privacyguides.org
2024.12.14
Your central privacy and security resource to protect yourself online.
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.
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.
Note
Most hidden service providers are not very extensively used or tested, which is why we strongly recommend Tor. Using other networks could be more likely to endanger your anonymity, so make sure you know what you're doing.
Tor/onion: xoe4vn5uwdztif6goazfbmogh6wh5jc4up35bqdflu6bkdc5cas5vjqd.onion
IPFS: /ipns/ipfs.privacyguides.org (not anonymous)
/dnsaddr/node-1.ipfs.jonaharagon.net/p2p/12D3KooWMwqzuApCKxYfo66zq5BrTjCoz9naJ1rrMEBCnwuGGqWBI2P: privacyguides.i2p
Yggdrasil: http://[200:f3a6:4922:e067:770d:ac57:fcb1:8dbf] (not anonymous)
tcp://5.161.245.8:45454
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.
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.
mkdocs-materialpip install mkdocs-material./run.sh --cmd=mkdocsmkdocs-material-insidersThis website uses mkdocs-material-insiders which offers additional functionality over the open-source mkdocs-material project. For obvious reasons we cannot distribute access to the insiders repository.
Team members should clone the repository with mkdocs-material-insiders directly. This method is identical to production:
git clone --recurse-submodules https://github.com/privacyguides/privacyguides.org.git.allowed_signers file: git config gpg.ssh.allowedSignersFile .allowed_signerspip install pipenvpipenv install --dev (install Pillow and CairoSVG as well to generate social cards)./run.sh --insiders (set CARDS=true to generate social cards)
http://localhost:8000./run.sh --insiders --buildIf you commit to main with commits signed with your SSH key, you should add your SSH key to .allowed_signers in this repo.
brew install crowdin)CROWDIN_PERSONAL_TOKEN environment variable to your Crowdin personal access tokencrowdin download in the root of this repo./run.sh --insiders --lang=fr (replacing fr with the appropriate language in /config)Translations downloaded from Crowdin are .gitignore'd, so any local changes to the translated site cannot be committed to this repo. Actual modifications need to be made on Crowdin. As an alternative to steps 1-3, you can copy the folders from privacyguides/i18n to the root of this repo to obtain the translated files.
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.staging.privacyguides.dev prior to release.
git tag -s YYYY.MM.DD -m 'Some message'
YYYY.MM.DD - if two+ releases are published on the same day, append short commit sha to next release, e.g. YYYY.MM.DD-6aa14e8git config tag.gpgSign true) to avoid missing signaturesgit push --tagsPrivacy Guides wouldn't be possible without these wonderful people (emoji key):
| Add your contributions |
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 generateCLI 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
