GrapheneOS vs /e/OS: Privacy Comparison
Here we put GrapheneOS head-to-head with /e/OS across the six privacy factors that matter most: their data collection practices, encryption implementation, third-party data sharing, user privacy controls, transparency, and historical track record. While both products address similar requirements, the philosophies they bring to protecting users diverge sharply. Our assessment finds that GrapheneOS provides a noticeably better overall privacy experience, although neither service is without trade-offs that deserve a careful, detailed look.
Reading the Scorecard
The most useful starting point is the overall tally and the single dimension that decided it. Across the six privacy dimensions we score, GrapheneOS finishes ahead of /e/OS, 41/60 to 35/60. That total reflects a side-by-side review in which one service is consistently the more privacy-respecting choice, even though both cover the same functional ground.
The largest single-dimension gap is in Data Collection, where GrapheneOS leads by 1 point -- GrapheneOS 6/10 to /e/OS 5/10. On Data Collection the margin nearly vanishes: GrapheneOS 6/10 against /e/OS 5/10. Everything below justifies these totals dimension by dimension.
Data Collection Practices
Every privacy assessment starts with data collection. How much a service gathers, stores, and processes about its users is what ultimately drives the privacy risk of using it. GrapheneOS takes a leaner approach here, capturing only the data strictly required to make the service work. Its rival pulls in a wider net of information -- behavioral patterns, device identifiers, and usage analytics that go well past what the core features actually need. Our marks were GrapheneOS 6/10 and /e/OS 5/10 in this area. What separates them is not merely how much is gathered but why it is gathered and whether it is truly needed.
Encryption Standards
Whether data is moving or resting, encryption is what keeps it safe, and the quality of that work swings widely across services. GrapheneOS brings more capable encryption to the table, pairing more resilient protocols for data in transit with better protection for data at rest. Where the two differ is in coverage (exactly which data is encrypted), in strength (the algorithms and key lengths chosen), and in whether end-to-end encryption is used at all (which stops even the service operator from seeing user content). On encryption, GrapheneOS scored 7/10 and /e/OS scored 6/10.
Sharing Data With Outside Parties
A service's willingness to hand data to outside parties is a make-or-break privacy factor. That covers advertising networks, analytics providers, business partners, and what happens when governments come asking. GrapheneOS keeps a tighter lid on who can reach user data. These sharing habits shape security as much as privacy, since every extra party granted access becomes one more way a breach could happen. Scores: GrapheneOS 8/10, /e/OS 7/10.
User Privacy Controls
Individuals only hold real power over their data when a service's privacy controls are available and genuinely effective. The relevant tools include the option to opt out of data collection, ways to download and erase data, granular permission settings, and how readily users can exercise the rights afforded them by applicable privacy regulations. GrapheneOS offers more complete and approachable privacy controls. Scores: GrapheneOS 9/10, /e/OS 8/10.
Transparency
Transparency comes down to how plainly a service explains what it does with data. It shows up in how readable the privacy policy is, whether transparency reports are published, how quickly privacy questions get answered, and whether policy changes are communicated up front. GrapheneOS comes across as the more transparent of the two overall. Plain, easy-to-find privacy communication is the bedrock of informed consent and trust. Scores: GrapheneOS 5/10, /e/OS 4/10.
Historical Track Record
The record of privacy incidents, regulatory run-ins, and how a service answers vulnerabilities offers context you cannot ignore. GrapheneOS holds the stronger track record here, with a smaller count of incidents and a more responsible response to the problems that did surface. More often than not, what a service did in the past is the best guide to its future privacy conduct. Scores: GrapheneOS 6/10, /e/OS 5/10.
Our Bottom-Line Call
Adding everything up, our full analysis lands GrapheneOS at 41/60 and /e/OS at 35/60. For privacy, the overall winner is GrapheneOS. The two cover much the same functional ground, but the winner takes a more privacy-respecting stance across the dimensions that count for the most. Even so, no service is flawless, and whichever option you pick, you should always tune its privacy settings deliberately. We suggest pairing your choice with extra privacy tools, a VPN, DNS-level ad blocker, and privacy-focused browser, so you end up with a well-rounded privacy posture. And if your threat model demands the very highest level of privacy, it is worth asking whether an even more privacy-focused alternative exists in this category beyond the two compared here.