Privacy

4610 readers

2 users here now

Icon base by Lorc under CC BY 3.0 with modifications to add a gradient

founded 3 years ago

MODERATORS

Ategon@programming.dev

danielintempesta@programming.dev

"Cookies, identifiers and other data that google silently stores on android handsets", 2026, D.J. Leith (www.sciencedirect.com)

submitted 3 weeks ago by cm0002@mander.xyz to c/privacy@programming.dev

3 comments fedilink hide all child comments

I lot of the hostnames or IP addresses that your android devices connect to without your direct knowledge or consent(1) are hard to find anything relevant about, except for the fact that Google owns a lot of the domains and IP ranges. This article helped me a lot when deciding which end points to block(2).

(1) You have given your consent, albeit unknowingly, since the EULAs are purposefully written so that the end user has a hard time understanding it.\
(2) In my case, with a systemless hosts file using Magisk and AdAway

top 3 comments

sorted by: hot top controversial new old

[–] crimson_iris@piefed.social 2 points 3 weeks ago (1 children)

Inb4 "just get a GrapheneOS phone."

[–] IceFoxX@lemmy.world 1 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

HoneypotOS Fresh on hardware with undocumented instruction sets, etc. It continues to use the mobile network with SS7, etc. Securephones (cryptophones) are banned for reason Copyfail and well... honeypotOS

[–] akunohana@piefed.blahaj.zone 4 points 3 weeks ago

I remember hearing that the Copy Fail exploit doesn't work on Android because of SELinux restrictions.