this post was submitted on 30 Oct 2024
41 points (95.6% liked)

Privacy

32159 readers
641 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Related communities

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago
MODERATORS
 

To me, it’s gotta be the microphone

you are viewing a single comment's thread
view the rest of the comments
[–] Charger8232@lemmy.ml 17 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

This depends on what you're trying to defend against. In my opinion (on GrapheneOS):

  • "Accessibility" permission (i.e. full control of the device)
  • "Network" permission
  • "Modify system settings" permission
  • "Install unknown apps" permission
  • Any permission that allows apps to communicate with one another (such as a reduced sandbox, file permission, or app communication scopes)

Those are the only permissions that I can think of off the top of my head that could potentially allow an app to phone home. Turning off Wi-Fi for the device does little if the app also has the "Wi-Fi control" permission.

[–] Quail4789@lemmy.ml 3 points 3 weeks ago

App communication scopes isn't the scary thing, it's the solution. Standard Android sandbox allows apps to communicate if they mutually agree to it. Scopes will allow you to limit that.