You're viewing the mastodonapp.uk public feed.

GrapheneOSGrapheneOS@grapheneos.social
Apr 6, 2026, 1:08 PM
@codebam /e/ doesn't have similar privacy protections as GrapheneOS. Unlike GrapheneOS, /e/ connects to a bunch of Google services by default and also unlike GrapheneOS gives extensions privileged access to Google apps and services. We don't use the term degoogled and it's not the purpose of GrapheneOS but GrapheneOS does only connect to our own servers by default and does not give any privileged access to installed Google apps without the user explicitly enabling narrow forms via a few toggles.
💬 1🔄 0⭐ 0

Replies

GrapheneOSGrapheneOS@grapheneos.social
Apr 6, 2026, 1:09 PM
@codebam /e/ fails to keep up with standard privacy patches and fails to provide standard privacy protections. /e/ has privacy invasive apps and services included. They have user tracking via a unique random identifier in their update client and multiple invasive services which are marketed as private when they aren't. They've had issues including leaking files stored in their cloud server to other users which turned out to clearly not actually be E2EE. Privacy also heavily depends on security.
💬 0🔄 0⭐ 0