Back to updates
New releaseSep 18, 2026

privacyguides.org v2026.09.17

Protect your data against global mass surveillance programs.

Share
Privacy Guides

Your central privacy and security resource to protect yourself online.

About

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 on the executive committee page. Additionally, many people have made contributions to the project, and you can too!

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

Contributing

Open in GitHub Codespaces

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.

Git Mirrors

GitHub GitLab Codeberg Gitea Forgejo

Developing

The easiest way to develop this website in your browser without installing any software is to use GitHub Codespaces. To build the website locally, you will need the following software:

You can technically use any IDE which supports development containers, but YMMV. 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.

Local builds

Run these commands from the repository root inside the development container. (These commands run automatically if you are using a devcontainer/codespace)

./run.sh serve
./run.sh --blog serve --dev-addr=localhost:8001

To build the production version locally, you use the same context as the release workflows:

Categories