parent
b4dbbeb1ae
commit
b0f5fc0aa0
|
|
@ -70,3 +70,7 @@ See https://www.privacytools.io/providers/vpn/#criteria for more details.
|
|||
|
||||
- Provider logos are 200px x 70px ([example](https://www.privacytools.io/assets/img/provider/AirVPN.png))
|
||||
- Tool logos are 120px x 120px ([example](https://www.privacytools.io/assets/img/tools/ChatSecure.png))
|
||||
|
||||
## Licensing
|
||||
|
||||
The content and original technology of this website is made available under the Creative Commons Zero v1.0 Universal license text. Some files or folders may include works from other projects with separate licenses, and will be marked as such. **By contributing to this repository, contributors do not necessarily agree to sign a CLA or legally transfer their copyright to the project, but they do at a minimum agree to license their work under the current license of this repository: In this case, the Creative Commons Zero v1.0 Universal.**
|
||||
|
|
|
|||
|
|
@ -1,4 +0,0 @@
|
|||
github: JonahAragon
|
||||
liberapay: privacytools.io
|
||||
patreon: privacytools
|
||||
custom: https://www.privacytools.io/donate/
|
||||
|
|
@ -1,88 +0,0 @@
|
|||
# privacytools.io Code of Conduct
|
||||
|
||||
## Our Pledge
|
||||
|
||||
In the interest of fostering an open and welcoming environment, we as
|
||||
contributors and maintainers pledge to make participation in our project and
|
||||
our community a harassment-free experience for everyone, regardless of a
|
||||
distinction of any kind, such as age, body size, disability, ethnicity, sex
|
||||
characteristics, gender identity and expression, level of experience,
|
||||
education, socio-economic status, nationality, personal appearance, race,
|
||||
religion, or sexual identity and orientation.
|
||||
|
||||
## Our Standards
|
||||
|
||||
Examples of behavior that contributes to creating a positive environment
|
||||
include:
|
||||
|
||||
* Using welcoming and inclusive language
|
||||
* Being respectful of differing viewpoints and experiences
|
||||
* Gracefully accepting constructive criticism
|
||||
* Focusing on what is best for the community
|
||||
* Showing empathy towards other community members
|
||||
|
||||
Examples of unacceptable behavior by participants include:
|
||||
|
||||
* The use of sexualized language or imagery and unwelcome sexual attention
|
||||
or advances
|
||||
* Trolling, insulting/derogatory, antagonistic comments and personal or
|
||||
political attacks
|
||||
* Promoting intolerance
|
||||
* Public or private harassment
|
||||
* Publishing others' private information, such as a physical or electronic
|
||||
address, without explicit permission
|
||||
* Other conduct which could reasonably be considered inappropriate in a
|
||||
professional setting
|
||||
|
||||
## Our Responsibilities
|
||||
|
||||
Project maintainers are responsible for clarifying the standards of
|
||||
acceptable behavior and are expected to take appropriate and fair
|
||||
corrective action in response to any instances of unacceptable behavior.
|
||||
|
||||
Project maintainers have the right and responsibility to remove, edit, or
|
||||
reject comments, commits, code, wiki edits, issues, and other contributions
|
||||
that are not aligned to this Code of Conduct, or to ban temporarily or
|
||||
permanently any contributor for other behaviors that they deem
|
||||
inappropriate, threatening, offensive, or harmful.
|
||||
|
||||
## Scope
|
||||
|
||||
This Code of Conduct applies within all project spaces, and it also applies
|
||||
when an individual is representing as a part of the project or its
|
||||
community in public spaces.
|
||||
|
||||
Examples of representing a project or community include using an official
|
||||
project e-mail address, posting via an official social media account, or
|
||||
acting as an appointed representative at an online or offline event.
|
||||
Representation of a project may be further defined and clarified by
|
||||
project maintainers.
|
||||
|
||||
## Enforcement
|
||||
|
||||
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
||||
reported by contacting blacklight447 via email on
|
||||
blacklight447@privacytools.io or [any team member on our forum].
|
||||
The reports should include information on whether they can be shared to
|
||||
other team members and how much may be told.
|
||||
|
||||
[any team member on our forum]:https://forum.privacytools.io/g/team
|
||||
|
||||
All complaints will be reviewed and investigated and will result in a
|
||||
response that is deemed necessary and appropriate to the circumstances.
|
||||
The project team is obligated to maintain confidentiality with regard to the
|
||||
reporter of an incident. Further details of specific enforcement policies
|
||||
may be posted separately.
|
||||
|
||||
Project maintainers who do not follow or enforce the Code of Conduct in good
|
||||
faith may face temporary or permanent repercussions as determined by other
|
||||
members of the project's leadership.
|
||||
|
||||
## Attribution
|
||||
|
||||
This Code of Conduct is forked from and licensed under Creative Commons
|
||||
BY-4.0, [Contributor Covenant version 1.4] by privacytools.io, which you can
|
||||
[find on our GitHub repository].
|
||||
|
||||
[find on our GitHub repository]:https://github.com/privacytoolsIO/privacytools.io/blob/master/CODE_OF_CONDUCT.md
|
||||
[Contributor Covenant version 1.4]:https://contributor-covenant.org/version/1/4
|
||||
35
SECURITY.md
35
SECURITY.md
|
|
@ -1,35 +0,0 @@
|
|||
# Security Policies and Procedures
|
||||
|
||||
This document outlines security procedures and policies for the `privacytools.io` repository/code and all services hosted by privacytools.io, such as Mastodon, Matrix, Riot, et cetera.
|
||||
|
||||
## Reporting a Bug
|
||||
|
||||
We take all security bugs related to our code and our infrastructure very seriously. Thank you for improving the security of our projects and services. We appreciate your efforts and responsible disclosure, and will make every effort to acknowledge your contributions.
|
||||
|
||||
Report any security bugs by emailing the services administrator at [admin@privacytools.io](mailto:admin@privacytools.io).
|
||||
|
||||
The administrative team will acknowledge your message within 48 hours, and will provide a detailed response within 72 hours detailing the next steps for handling your report. After our initial reply we will make every effort to keep you informed of the progress towards a fix and announcement, and we may ask for additional information or guidance.
|
||||
|
||||
Please report any security bugs in third-party projects to the person or team maintaining that project.
|
||||
|
||||
The following are out of scope and should **not** be attacked/performed:
|
||||
|
||||
* Excessive Automated Scans
|
||||
* Denial of Service Attacks
|
||||
* Social Engineering Attacks
|
||||
* Reports against infrastructure outside our control
|
||||
* User or admin accounts not owned by the tester
|
||||
|
||||
## Disclosure Policy
|
||||
|
||||
When we receive a security report, that report will be assigned to an administrative team member. That person will coordinate the fix, release, and announcement process, involving the following steps:
|
||||
|
||||
1. Confirm the problem and determine affected services.
|
||||
2. Audit infrastructure and/or code to find any potential similar problems.
|
||||
3. Prepare fixes for all releases currently in production, which will be implemented as quickly as possible.
|
||||
|
||||
Additionally, if user data was directly affected or compromised, we will inform affected users to the best of our ability via email and/or a website notification with more information about the incident.
|
||||
|
||||
## Comments on this Policy
|
||||
|
||||
Please open a Pull Request or Issue if you would like to discuss any changes to this policy.
|
||||
Reference in New Issue