/e/OS is designed for the non technical users. The default configuration intends to offer the best user experience to its users, especially with third party applications. In order to work properly, those applications require some calls to Google servers. As much as possible, the data shared with Google are anonymized in order to protect your privacy.
/e/OS is a deGoogled mobile OS designed for the non technical users.
You may be able to detect some calls to Google servers on your device running on /e/OS. This page intends to explain where they are coming from, what they are used for and what information may be shared with Google.
## What does "deGoogling" means?
Sadly, if you want to use popular Android apps, there is no way to avoid sending some data to Google servers. We would love to tell you that we stop all calls to Google servers, but this is not possible today.
Some people might be confused by this word since deGoogling doesn't mean that nothing from Google is going to be used. The core Android project itself is maintained by Google, and mobile applications for Android often rely on Google Play Services.
But /e/OS has been historically (since 2018) the first mobile OS to solve this complicated equation by integrating by default by replacing all the proprietary Android components that communicate with the Google Play services by an open source layer called "microG", that replaces some Google Play Services, and anonymizes remaining call to the Google Play Services (e.g. Push Notifications...). Read more about deGoogling in /e/OS, Advanced Privacy features in /e/OS (mobile apps trackers killer, fake gelolocation, fake IP address...) and online services we provide (personal workspace, search engine...): https://doc.e.foundation/what-s-e#degoogling--ungoogling-in-eos
The default /e/OS configuration intends to offer the best user experience to its users, especially with third party applications. In order to work properly, some applications require some calls to Google servers. By default in /e/OS, all the data shared with Google are anonymized in order to protect your privacy.
We have created this page for transparency: like on any other Android-based mobile OS, you can detect some network calls to Google servers on your device running on /e/OS. This page explains where they are coming from, what they are used for and what information may be shared with Google.
Our goal is to focus on personal data protection while allowing you to enjoy a normal life with your phone. Our approach is to avoid sending identifiable information when we have to send data, while not degrading the user experience.
Instead, our goal is to focus on personal data protection while allowing you to enjoy a normal life with your phone. Our approach is to avoid sending identifiable information when we have to send data.
The other thing that is key to note is that /e/OS doesn't capture any logs, any location or app activity. With /e/OS, Google is not able to profile users and leverage data from the OS for its own purpose, nor to sell this data to third parties.
To sum up: with the default /e/OS setup, Google is not able to capture any personal information from the user.
## Device registration (microG)
In order to get access to the Google API (mainly to get access to notifications), microG has to register the device at Google.
@@ -185,6 +194,9 @@ App Lounge is fetching data from Google Play Store directly to get access to the
⚙️ Under investigation with the /e/OS development team.
