Top Related Projects
:books: Freely available programming books
A list of Free Software network services and web applications which can be hosted on your own servers
Awesome Privacy - A curated list of services and alternatives that respect your privacy because PRIVACY MATTERS.
A huge list of alternatives to Google products. Privacy tips, tricks, and links.
🔒 A compiled checklist of 300+ tips for protecting digital security and privacy in 2024
🛡🛠 You are being watched. Protect your privacy against global mass surveillance.
Quick Overview
PrivacyGuides.org is an open-source project that provides a comprehensive guide to privacy and security-focused tools, services, and best practices. The repository contains the source code for the Privacy Guides website, which aims to educate users about digital privacy and help them make informed decisions about their online presence.
Pros
- Comprehensive and well-organized information on privacy tools and practices
- Regularly updated content to reflect the latest developments in privacy and security
- Community-driven project with contributions from privacy experts and enthusiasts
- Transparent and open-source, allowing for public scrutiny and improvement
Cons
- May be overwhelming for beginners due to the extensive amount of information
- Some recommended tools or services may have a learning curve or require technical knowledge
- Occasional debates or disagreements within the community about specific recommendations
- Limited localization options for non-English speakers
Competitor Comparisons
:books: Freely available programming books
Pros of free-programming-books
- Extensive collection of free programming resources across various languages and topics
- Community-driven project with frequent updates and contributions
- Well-organized structure with categorization by programming language and subject
Cons of free-programming-books
- Limited focus on privacy-related topics compared to privacyguides.org
- Lacks in-depth explanations or reviews of the listed resources
- May include outdated or deprecated resources due to the vast collection
Code Comparison
While a direct code comparison is not particularly relevant for these repositories, we can compare their structure:
free-programming-books:
books/
language-specific-folders/
README.md (containing book lists)
privacyguides.org:
docs/
topics/
specific-topic-files.md
_includes/
sections/
specific-section-files.html
privacyguides.org uses a more complex structure with separate documentation and includes folders, while free-programming-books primarily relies on README files within language-specific folders.
A list of Free Software network services and web applications which can be hosted on your own servers
Pros of awesome-selfhosted
- Extensive list of self-hosted software options across various categories
- Active community contributions and regular updates
- Includes detailed information about each project, such as demo links and license types
Cons of awesome-selfhosted
- Less focus on privacy-specific tools and recommendations
- May overwhelm users with too many options without clear guidance
- Lacks in-depth explanations or tutorials for implementing self-hosted solutions
Code comparison
While both repositories are primarily content-based and don't contain significant code, here's a brief comparison of their structure:
awesome-selfhosted:
## Category Name
- [Project Name](https://project-url) - Brief description. (`License` `Language`)
privacyguides.org:
---
title: "Page Title"
icon: icon-name
description: "Page description"
---
{% include breadcrumbs.html %}
Content in Markdown format
The awesome-selfhosted repository uses a simple Markdown structure to list projects, while privacyguides.org employs a more complex Jekyll-based structure with front matter and custom includes for building a full website.
Awesome Privacy - A curated list of services and alternatives that respect your privacy because PRIVACY MATTERS.
Pros of awesome-privacy
- More extensive list of privacy-focused tools and services
- Includes a wider range of categories, such as cryptocurrencies and decentralized networks
- Community-driven with frequent updates and contributions
Cons of awesome-privacy
- Less structured and organized compared to PrivacyGuides
- Lacks in-depth explanations and recommendations for each tool
- May include some outdated or less vetted resources
Code comparison
PrivacyGuides (Jekyll-based website):
---
layout: page
title: "Browser Recommendations"
description: "Find a recommended, privacy-respecting web browser for your desktop or mobile device."
---
awesome-privacy (Markdown-based list):
## Browsers
- [Brave](https://brave.com/) - Privacy-focused browser with built-in ad and tracker blocking.
- [Firefox](https://www.mozilla.org/firefox/) - Open-source browser with strong privacy features.
- [Tor Browser](https://www.torproject.org/) - Anonymity-focused browser based on Firefox.
PrivacyGuides offers a more structured and detailed approach to presenting information, while awesome-privacy provides a concise list format with brief descriptions. Both repositories serve as valuable resources for privacy-conscious users, with PrivacyGuides offering more curated content and awesome-privacy providing a broader range of options.
A huge list of alternatives to Google products. Privacy tips, tricks, and links.
Pros of degoogle
- Focused specifically on Google alternatives and de-Googling strategies
- Community-driven with frequent updates and contributions
- Includes a comprehensive list of Google products and their alternatives
Cons of degoogle
- Less structured and organized compared to PrivacyGuides
- Limited information on general privacy practices beyond Google alternatives
- Lacks in-depth explanations and tutorials for implementing privacy measures
Code comparison
PrivacyGuides (Jekyll-based):
{% include sections.html %}
{% include breadcrumbs.html %}
<h1>{{ page.title }}</h1>
{{ content }}
degoogle (Markdown-based):
# degoogle
> A huge list of alternatives to Google products. Privacy tips, tricks, and links.
* [Search](#search)
* [Browser](#browser)
* [Android](#android)
PrivacyGuides uses a more structured approach with Jekyll templating, while degoogle relies on simple Markdown formatting. This reflects the overall organization and presentation differences between the two projects.
Both repositories serve as valuable resources for privacy-conscious individuals, with PrivacyGuides offering a broader scope of privacy information and degoogle focusing specifically on Google alternatives.
🔒 A compiled checklist of 300+ tips for protecting digital security and privacy in 2024
Pros of personal-security-checklist
- More comprehensive coverage of security topics, including physical security and OPSEC
- Regularly updated with community contributions
- Includes practical tips and actionable advice for various scenarios
Cons of personal-security-checklist
- Less structured organization compared to privacyguides.org
- Lacks in-depth explanations for some recommendations
- May overwhelm users with the sheer amount of information
Code Comparison
While both repositories are primarily focused on content rather than code, we can compare their structure:
personal-security-checklist:
# Personal Security Checklist
## Contents
- [Authentication](#authentication)
- [Networking](#networking)
...
privacyguides.org:
---
title: "VPNs"
icon: material/vpn
description: VPNs are the most widely recommended privacy tools...
---
# Choose a VPN Provider
...
privacyguides.org uses a more structured approach with YAML frontmatter for metadata, while personal-security-checklist relies on standard Markdown formatting. The privacyguides.org repository also includes more complex build processes and internationalization support, making it more suitable for a full-fledged website.
🛡🛠 You are being watched. Protect your privacy against global mass surveillance.
Pros of privacytools.io
- Longer history and established reputation in the privacy community
- More comprehensive coverage of privacy-related topics and tools
- Larger community and contributor base
Cons of privacytools.io
- Less frequent updates and maintenance
- Some outdated information and recommendations
- Occasional controversies surrounding project leadership
Code Comparison
privacytools.io:
<section class="mb-5" id="vpn">
<h1 id="vpn" class="anchor"><a href="#vpn"><i class="fas fa-link anchor-icon"></i></a> VPN Services</h1>
<div class="row mb-2">
<div class="col">
<p><strong>Get a VPN to hide your IP address and location!</strong></p>
privacyguides.org:
<h1 class="mb-4">VPN Services</h1>
<p class="lead mb-4">
A VPN, or Virtual Private Network, is an encrypted connection between your device and a server operated by the VPN provider.
</p>
<div class="row mb-4">
The code comparison shows that both projects use HTML for their website structure, but privacyguides.org appears to have a more modern and streamlined approach to content presentation.
Convert 
designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual CopilotREADME
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 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.
Contributing
- ð¬ 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.
Mirrors
- 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!)
Alternative Networks
[!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)- Please help us out by pinning a copy: Learn more
- via Cloudflare: cloudflare-ipfs.com/ipns/ipfs.privacyguides.org
- via 4everland: ipfs-privacyguides-org.ipns.4everland.io
- via @jonaharagon: ipfs.jonaharagon.net/ipns/ipfs.privacyguides.org
- via peer:
/dnsaddr/node-1.ipfs.jonaharagon.net/p2p/12D3KooWMwqzuApCKxYfo66zq5BrTjCoz9naJ1rrMEBCnwuGGqWB
-
I2P: privacyguides.i2p
-
Yggdrasil: http://[200:f3a6:4922:e067:770d:ac57:fcb1:8dbf] (not anonymous)
- via public peer:
tcp://5.161.245.8:45454
- via public peer:
Git Mirrors
License
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.
Developing
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.
With mkdocs-material
- Install required packages:
pip install mkdocs-material - Run a local preview of the English site:
./run.sh --cmd=mkdocs
With mkdocs-material-insiders
This 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:
- Clone this repository and submodules:
git clone --recurse-submodules https://github.com/privacyguides/privacyguides.org.git - Enable SSH commit verification with our local
.allowed_signersfile:git config gpg.ssh.allowedSignersFile .allowed_signers - Install Python 3.12.
- Install pipenv:
pip install pipenv - Install dependencies:
pipenv install --dev(install Pillow and CairoSVG as well to generate social cards) - Serve the site locally:
./run.sh --insiders(setCARDS=trueto generate social cards)- The site will be available at
http://localhost:8000 - You can build the site locally with
./run.sh --insiders --build - This version of the site should be identical to the live, production version
- The site will be available at
If you commit to main with commits signed with your SSH key, you should add your SSH key to .allowed_signers in this repo.
Local Translated Site Builds
- Install the Crowdin CLI Tool (
brew install crowdin) - Set the
CROWDIN_PERSONAL_TOKENenvironment variable to your Crowdin personal access token - Run
crowdin downloadin the root of this repo - Serve the site locally:
./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.
Releasing
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.
- 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
- Tag numbering:
- Push the tag to GitHub:
git push --tags - 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.
Contributors
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
Top Related Projects
:books: Freely available programming books
A list of Free Software network services and web applications which can be hosted on your own servers
Awesome Privacy - A curated list of services and alternatives that respect your privacy because PRIVACY MATTERS.
A huge list of alternatives to Google products. Privacy tips, tricks, and links.
🔒 A compiled checklist of 300+ tips for protecting digital security and privacy in 2024
🛡🛠 You are being watched. Protect your privacy against global mass surveillance.
Convert designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual Copilot