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
I made the switch when I got a new phone. So I kept both the old phone with android and the new phone with GrapheneOS. There was a transition period when I would bring both phones with me, just in case. Now my old phone is my "whatsapp" phone which I keep at home and turn on rarely. During the transition period I used my old phone number whenever I needed to provide my phone to use a service, but eventually I transitioned that to a VoIP. But, even then, many services will reject VoIP phone numbers, so I still make use of the old one.
I had to request a special scanner from my bank because the banking apps do not work with GrapheneOS. And I had to make sure that nothing important goes into my gmail anymore because google would request that I used my old phone 2FA in the most inconvenient moments, and also I don't want to access google from my GrapheneOS phone.
I think that there are many annoyances that can and probably will happen if you try to jump right into GrapheneOS after having previously relied in the google/meta ecosystem. If you attempt to switch too quickly you might inadvertently lose access to your bank, and you might become suddenly unable to communicate with family and friends. My government's online identification system requires that I use their app, which runs on google services, so I still have to use my old phone for that. And I have encountered situations in which the only reasonably convenient way to proceed is to download an app. For example, recently I registered for a gym that would then require me to use their google-store app so that I could identify myself when purchasing a physical card.
Does WhatsApp not work at all on Graphene OS or do you just need to enable Google Play services for it to work? (I do understand why you personally may not want to enable the Play services, but I'm just curious about the potential capabilities).
It works fine if you have Google Play Services
I think that it works, but for it to work you need to enable Google Play services. From what I understand, this is done in a sandboxed manner simulating a fake identity, so it is possible to do this while isolating Google from your phone to an extent. But I think that WhatsApp is in itself problematic and one of the direct offenders that I want to avoid, regardless of its reliance on Google Play services, and so I have not gone through this effort myself.
@Antiochus @Sal Graphene or any clean Custom-ROM is a waste of time if you intend to use Whatsapp or any of META, TikTok and the like. https://medium.com/@TalBeerySec/hi-meta-whatsapp-with-privacy-6d646c5aa3bc
The official GrapheneOS Twitter account states the complete opposite on several occasions:
https://nitter.net/GrapheneOS/status/1692002070650335259#m
https://nitter.net/GrapheneOS/status/1728630943886270827#m
https://nitter.net/GrapheneOS/status/1745532453215781151#m
What do they do if you say "oh, I don't have a smart phone"?
I am not sure as I did not test this one. Maybe you can go in person and get a worker to get you access to the kiosk through your account to print the card. It is one of those massive chains with gyms in every corner. I think that by now they rely on their digital infrastructure and many of their workers are not trained to handle uncommon situations. At least I get that from some of my experiences, but I could be wrong, maybe if I would have called them could have helped me with this. It was just easier to get the app into my old phone, print a card, delete the app.