Privacy Guides
In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.
This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.
You can subscribe to this community from any Kbin or Lemmy instance:
Check out our website at privacyguides.org before asking your questions here. We've tried answering the common questions and recommendations there!
Want to get involved? The website is open-source on GitHub, and your help would be appreciated!
This community is the "official" Privacy Guides community on Lemmy, which can be verified here. Other "Privacy Guides" communities on other Lemmy servers are not moderated by this team or associated with the website.
Moderation Rules:
- We prefer posting about open-source software whenever possible.
- This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
- No soliciting engagement: Don't ask for upvotes, follows, etc.
- Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
- Be civil, no violence, hate speech. Assume people here are posting in good faith.
- Don't repost topics which have already been covered here.
- News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
- Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
- No help vampires: This is not a tech support subreddit, don't abuse our community's willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
- No misinformation: Extraordinary claims must be matched with evidence.
- Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
- General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.
Additional Resources:
- EFF: Surveillance Self-Defense
- Consumer Reports Security Planner
- Jonah Aragon (YouTube)
- r/Privacy
- Big Ass Data Broker Opt-Out List
view the rest of the comments
Because the threat isn't getting your number stolen, it's about the content of your messages. While the goverment cóuld ask your phone number, they likely already have it unless you got a prepaid trow away that you keep replacing regularily. And even then it cóuld be traced when used anywhere. What they can't get, is your messages. At least not decrypted unless you give it to them yourself. And those are way more interesting. But it's not even about the goverment per se, it's for everything from data hungry companies to your old crazy ex.
Telegram sends everything plain text and stores that on their servers. One man-in-the-middle and we got everything you've said.
WhatsApp says they have E2EE but is propietary and non-checkable, and from Meta who has a rep for finding ways to secretly and unlawfully grab data. Even if you (foolishly) trust them, they do grab metadata from your messages.
Signal isn't about it being FOSS, but about privacy. FOSS just means it's checkable, which is good for security and privacy. They have E2EE not only on message content but also on metdata (unlike most alternatives who only do message contents), do external audits, and are part of a non-profit (which means showing how money is received and spend).