privacyguides.org

Privacy Guides is a socially motivated website that provides information for protecting your data security and privacy. Our mission is to inform the public about the value of digital privacy, and global government initiatives which aim to monitor your online activity. We are a non-profit collective operated entirely by volunteer team members and contributors. Our website is free of advertisements and not affiliated with any of the listed providers.

The current list of team members can be found here. Additionally, many people have made contributions to the project, and you can too!

Featured on: Tweakers, The New York Times, Wired, and Fast Company.

• Start a discussion or suggest an idea
• ? Sponsor the project
• ? Help translate the site [Matrix chat]
• Edit the site, everything's accessible in this repo
  • Browse our open issues to see what needs to be updated
  • View the list of approved topics waiting for a PR
  • Read some writing tips in our style guide

All contributors to the site are listed here. If you have contributed to the website or project, please add yourself to the list or ask @jonaharagon to make the change.

• GitHub Pages: privacyguides.github.io/privacyguides.org
• Netlify (AWS): illustrious-bavarois-56cf30.netlify.app
• BunnyCDN: privacyguides-org-production.b-cdn.net
• Hetzner: direct.privacyguides.org (discouraged!)

• Tor/onion: xoe4vn5uwdztif6goazfbmogh6wh5jc4up35bqdflu6bkdc5cas5vjqd.onion

Copyright © 2019 - 2024 Privacy Guides contributors.

Privacy Guides content is licensed under the Creative Commons Attribution-ShareAlike 4.0 International Public License, and the underlying source code used to format and display that content on www.privacyguides.org is licensed under the MIT License.

Generally speaking, content can be found in the /docs, /theme/assets/img and /includes folders; and source code and configuration files can be found in the /config and /theme folders, and in the root of this repository. Any source code snippets contained within documentation files are MIT Licensed. Please contact us if you require clarification on any of these terms.

These licenses do not apply to any work where another license is otherwise noted.

Logos in the /theme/assets/img folder may not be original works of Privacy Guides and therefore cannot be (re)licensed by us. We believe that these logos obtained from third-party providers are either in the public domain or fair use. In a nutshell, legal fair use doctrine allows the use of copyrighted images in order to identify the subject for purposes of public comment. However, these logos and other images may still be subject to trademark laws in one or more jurisdictions. Before using this content, please ensure that it is used to identify the entity or organization that owns the trademark and that you have the right to use it under the laws which apply in the circumstances of your intended use. When copying content from this website, you are solely responsible for ensuring that you do not infringe someone else's trademark or copyright.

You may comply with our license terms in any reasonable manner, but not in any way that suggests Privacy Guides endorses you or your use. You may not use the Privacy Guides branding in your own project without express approval from this project. Privacy Guides's brand trademarks include the "Privacy Guides" wordmark and shield logo.

When you contribute to this repository you are doing so under the above licenses, and you are granting Privacy Guides a perpetual, worldwide, non-exclusive, transferable, royalty-free, irrevocable license with the right to sublicense such rights through multiple tiers of sublicensees, to reproduce, modify, display, perform and distribute your contribution as part of our project.

The only supported method of building and previewing this website locally is by running the automatic dev container. The easiest way to do this in your web browser without installing any software is to use GitHub Codespaces. To build the website locally, you will need the following software:

• macOS/Windows: Docker Desktop
• Linux: Docker CE
• VS Code
• Dev Containers for VS Code extension
• GitHub Desktop (optional)

You can technically use any IDE which supports development containers, but YMMV. Docker Desktop has an experimental Dev Environments option which allows you to use any text editor under Settings > Features in development. We are only testing with the combination of software above.

Committing to this repository requires signing your commits (git config commit.gpgsign true) unless you are making edits via the GitHub.com text editor interface. As of August 2022 the preferred signing method is SSH commit signatures, but GPG signing is also acceptable. You should add your signing key to your GitHub profile.

It is required to create a GitHub release to publish the current site to privacyguides.org. The current main branch can be previewed at https://main.s*ta*gin*g.privacyguides.dev prior to release.

1. Create a new tag: git tag -s YYYY.MM.DD -m 'Some message'
   • Tag numbering: YYYY.MM.DD - if two+ releases are published on the same day, append short commit sha to next release, e.g. YYYY.MM.DD-6aa14e8
   • Enable GPG tag signing by default (git config tag.gpgSign true) to avoid missing signatures
2. Push the tag to GitHub: git push --tags
3. A GitHub Release will be automatically created and deployed to the live site.
   • You may wish to manually check or edit the release changelog/title after it is published for accuracy.

Privacy Guides wouldn't be possible without these wonderful people (emoji key):

This project follows the all-contributors specification. Contributions of any kind welcome, including contributions to Privacy Guides outside of this repo, and contributions that aren't content related (like sharing ideas for Privacy Guides, promoting the project, answering questions on the forum, etc.).

CLI to generate this table:

npx --package all-contributors-cli -- npx all-contributors generate

CLI to add a contributor:

npx --package all-contributors-cli -- npx all-contributors add <username> <contribution>

See this table for valid contribution reasons, comma-separated. Do not use the content code for contributors to the website, use docs instead (this way it will automatically link to their commits). Example:

npx --package all-contributors-cli -- npx all-contributors add jonaharagon docs,research,question