diff --git a/htdocs/_i18n/en/pages/support_topics/calls_to_google_servers.md b/htdocs/_i18n/en/pages/support_topics/calls_to_google_servers.md new file mode 100644 index 0000000000000000000000000000000000000000..50c80abb0301af88a1a4aff002268bf77f11a685 --- /dev/null +++ b/htdocs/_i18n/en/pages/support_topics/calls_to_google_servers.md @@ -0,0 +1,193 @@ +/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. + +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. + +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. + +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. + +## 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. + + +- domain: `android.clients.google.com` +- when: once per day in background +- how to disable: **Settings** > **System** > **Advanced** > **microG** > **Google device registration** > disable +- known side effect: applications using any Google Play service may not work +- data shared + - stripped device identifier (MAC addresses, IMEI): not fully anonymized to keep some brand and device model identifier + - IP address + - returns and Android ID + +Please note you can define another profile from **Settings** > **System** > **Advanced** > **microG** > **Google device registration** > **Select profile** + +## Push Notifications (microG) + +If users want to have push notifications from applications, there is no other way than connecting to Google servers to receive push notifications, because most applications that send notifications are using Google push notifications (so this is implemented and embedded in Android apps). However, since we have totally replaced the proprietary Google Play Services piece of software from /e/OS by microG, connections to Google servers for the purpose of push notifications feature are done anonymously (by default on /e/OS). This means that the only thing Google knows is that they got a connection from a specific IP that is related to push notifications, but no more. So even if that is not totally perfect (an IP address can be used to track users) it’s considered to be good enough in terms of personal data privacy. + +- domains: + - `android.clients.google.com`: register the application for push notifications + - `mtalk.google.com`: server used for push notifications +- when + - when you first start an application that uses push notifications (`android.clients.google.com`) + - then persistent connection to receive notification (`mtalk.google.com`) +- how to disable: **Settings** > **System** > **Advanced** > **microG** > **Cloud messaging** > disable +- known side effect: applications using Google Cloud Messaging (GCM) only for notifications may not receive notifications (at best) or not work at all (at worst) +- known side effects: + - for applications using any Google Play services, some features may not work (at best) or the application will not work at all (at worst) + - higher battery consumption +- data shared + - stripped device identifier (MAC addresses, IMEI): not fully anonymized to keep some brand and device model identifier + - IP address + - the Android ID + - the applications subscribing to notifications + +## Safetynet (microG) + +Safetynet is a security feature that Google suggests to app developers to ensure that their app is not running on a non-GoogleAndroid device (e.g. commercial Android you find on smartphones in stores, with the Google stamp on it). This check needs a connection to some Google servers. It’s an anonymous call (by default on /e/OS), so it doesn’t allow Google to track the user. + +Please note Safetynet also has a reCAPTCHA feature, different from the [Firebase reCAPTCHA](https://developer.android.com/training/safetynet/recaptcha). + +**Safetynet Parameters** + +- domain: `www.googleapis.com` +- when: whenever an application requests a Safetynet attestation +- how to disable: **Settings** > **System** > **Advanced** > **microG** > **Google Safetynet** > disable +- known side effect: for applications requesting Satetynet attestation, some features may not work (at best) or the application will not work at all (at worst) +- data shared + - stripped device identifier (MAC addresses, IMEI): not fully anonymized to keep some brand and device model identifier + - IP address + - the Android ID + - the applications requesting Safetynet attestations + - some others info from the build.prop, such as at least he following ones. + - ro.boot.verifiedbootstate + - ro.boot.veritymode + - ro.build.version.security_patch + - ro.oem_unlock_supported + - ro.boot.flash.locked + - ro.build.version.security_patch + - ro.build.fingerprint + - ro.product.model + - ro.product.brand + +{% include alerts/warning.html content="Please note this list may be updated in the future, according to what we will discover."%} + + + +## Firebase Authentication (microG) + +Firebase is a Google backend providing features like realtime database, authentication and cloud messaging. + +- domains: + - `www.gstatic.com` + - `securetoken.googleapis.com` +- when: when an application requests a Firebase Authentication +- how to disable: **Settings** > **System** > **Advanced** > **microG** > **Google device registration** > disable +- known side effect: for applications requesting Firebase Authentication, some features may not work (at best) or the application will not work at all (at worst) +- data shared + - stripped device identifier (MAC addresses, IMEI): not fully anonymized to keep some brand and device model identifier + - IP address + - the Android ID + - the applications requesting Firebase Authentication + +## Firebase Authentication reCaptcha (microG) + +- domains: + - `www.gstatic.com` + - `www.google.com` +- when: when an application requests a Firebase Authentication reCaptcha +- how to disable: **Settings** > **System** > **Advanced** > **microG** > **Google device registration** > disable +- known side effect: for applications requesting Firebase Authentication reCaptcha, some features may not work (at best) or the application will not work at all (at worst) +- data shared + - stripped device identifier (MAC addresses, IMEI): not fully anonymized to keep some brand and device model identifier + - IP address + - the Android ID + - the applications requesting Firebase Authentication reCaptcha + +## Google Account management (not by default on /e/OS installation) (microG) + +The following calls happen only when a user decides to sign in within microG + +- domains: + - `www.googleapis.com` + - `android.googleapis.com` + - `waccounts.google.com` +- when: when a user decides to sign in within microG +- how to disable: **Settings** > **System** > **Advanced** > **microG** > **Account** > logout +- known side effect: user will be authenticated anonymously when using microG +- data shared + - stripped device identifier (MAC addresses, IMEI): not fully anonymized to keep some brand and device model identifier + - IP address + - the Android ID + - the user Google account + +## Google Account sign in (not by default on /e/OS installation) (microG) + +microG gives you the possibility to log in with your Google account. It's required for some third party applications in order to work properly. + +- domain: `android.googleapis.com` +- when: when an application requests a Google Account sign in +- how to disable: **Settings** > **System** > **Advanced** > **microG** > **Account** > logout +- known side effect: for applications requesting Google Account sign in, some features may not work (at best) or the application will not work at all (at worst) +- data shared + - stripped device identifier (MAC addresses, IMEI): not fully anonymized to keep some brand and device model identifier + - IP address + - the Android ID + - the user Google account + +## App Lounge + +App Lounge is fetching data from Google Play Store directly to get access to the whole catalog of Android applications. We offer two options for this: anonymous access and real Google account. It’s the user’s choice, but in any case there is an option to avoid being tracked by Google. The only issue here remains the IP address, but it’s a smaller issue. + +- domain: `android.clients.google.com` +- how to disable: Reset `App Lounge` app data, and don't open it after +- Known side effect: You will not be able to access applications from the Google Play Store within App Lounge nor will you be able to get updates from App Lounge for your installed apps. +- data shared + - The Google account if setup, otherwise the anonymous one + - The list of install application (for updates) + - Device properties + - Build.RADIO + - Build.BOOTLOADER + - Screen.Density + - GL.Extensions + - HasFiveWayNavigation + - Build.BRAND + - Build.ID + - Platforms + - TouchScreen + - Build.FINGERPRINT + - Vending.version + - Screen.Width + - Build.HARDWARE + - Build.VERSION.RELEASE + - Build.VERSION.SDK_INT + - Build.MODEL + - Locales + - SharedLibraries + - GL.Version + - GSF.version + - Screen.Height + - Vending.versionString + - HasHardKeyboard + - Features + - Navigation + - UserReadableName + - Build.MANUFACTURER + - Keyboard + - Build.DEVICE + - ScreenLayout + - Build.PRODUCT + +## A-GPS and SUPL servers + + +⚙️ Under investigation with the /e/OS development team. + +--- + +Sources: +- [https://github.com/microg/GmsCore/issues/1508#issuecomment-876269198](https://github.com/microg/GmsCore/issues/1508#issuecomment-876269198) +- [https://community.e.foundation/t/e-page-says-e-is-ungoogled-degoogled-why-is-e-then-connecting-to-google/40707/59](https://community.e.foundation/t/e-page-says-e-is-ungoogled-degoogled-why-is-e-then-connecting-to-google/40707/59) +- [https://calyxos.org/docs/guide/security/identifiers/](https://calyxos.org/docs/guide/security/identifiers/) diff --git a/htdocs/_i18n/en/pages/support_topics/de_googlisation.md b/htdocs/_i18n/en/pages/support_topics/de_googlisation.md index 0e3ca772edcf248feddb01949df1400cf08c3e72..4d2e513f6052a66ab784729375f12dee11622aa6 100644 --- a/htdocs/_i18n/en/pages/support_topics/de_googlisation.md +++ b/htdocs/_i18n/en/pages/support_topics/de_googlisation.md @@ -51,5 +51,8 @@ To understand how /e/ is different please read these documents: - This Apple - Google deal is a [$12 billion](https://www.businessinsider.fr/us/google-apple-search-deal-doj-antitrust-suit-2020-10) per year deal. This does not work in the advantage -- Last but not the least, Apple claims that they are acting in favor of privacy. That is claimed privacy. /e/ supports auditable privacy +- Last but not least, Apple claims that they are acting in favor of privacy. That is claimed privacy. /e/ supports auditable privacy by being open source. + +### Can you explain the pings from /e/OS when a user sets up the device? +For details please check the detailed response [here](/calls_to_google_servers) diff --git a/htdocs/_i18n/en/pages/support_topics/micro_g.md b/htdocs/_i18n/en/pages/support_topics/micro_g.md index 3438581edc167d18bd18c1c85104ca62e8424bfa..736900e0a148e7789b2f02486314bd04edadef4a 100644 --- a/htdocs/_i18n/en/pages/support_topics/micro_g.md +++ b/htdocs/_i18n/en/pages/support_topics/micro_g.md @@ -1,19 +1,19 @@ ## Development status of microG -The development on microG is an ongoing project. We discuss with its maintainer regularly and also support the microG project financially. +The development on microG is an ongoing project. We discuss with its maintainer regularly and also support the microG project financially. Improvements and updates are planned and implemented. Some time back we added FCM support and optimized the code. The contact-tracing API has been added too (it is not enabled by default on /e/OS though, see below). -There are more updates in the pipeline. +There are more updates in the pipeline. The project is complex and it would be great if more users contribute to it. ## microG and microG EN - microG is an open source re-implementation of Google’s proprietary Android user apps and libraries -- microG EN is a build of microG and only required by users who need to use COVID-19 contact tracking applications. +- microG EN is a build of microG and only required by users who need to use COVID-19 contact tracking applications. ## All about Contact tracing @@ -48,7 +48,7 @@ The COVID-19 contact tracing is done through the Exposure Notifications API. The ### Steps to install Exposure Notifications API on /e/OS -1. Download the latest [microG EN](https://gitlab.e.foundation/e/apps/GmsCore/-/releases) +1. Download the latest [microG EN](https://gitlab.e.foundation/e/apps/GmsCore/-/releases) - The downloads for both (`/dev` and `/stable`) builds are available at this location. Check your version and download the corresponding apk @@ -74,7 +74,7 @@ Here we will use the example of the Covid Radar app (from Spain) ### How to update the microG Exposure Notification Framework -The new **microG EN version** has some improvements in the Exposure Notification Framework API. +The new **microG EN version** has some improvements in the Exposure Notification Framework API. The Exposure Notification Framework has been developed by Apple and Google to enable contact tracing on iOS and Android. This Exposure Notification Framework API is necessary to use most COVID-19 contact tracing apps. @@ -94,7 +94,7 @@ The downloads for both (`/dev` and `/stable`) builds are available at [this loca If microG EN becomes unavailable on your device after an /e/OS update, do not worry, you can simply reinstall it on your device following the steps given in this guide. -### How to disable the app or the framework? +## How to disable the app or the framework? You can easily disable the COVID-19 contact tracing from your /e/ OS. All that you need to do is.. - Uninstall the contact tracing application you downloaded @@ -106,4 +106,4 @@ In addition, it's also possible to uninstall the microG Exposure Notifications v - [microG project](https://microg.org/) - [microG on Github](https://github.com/microg) -- [microG projects on /e/OS Gitlab](https://gitlab.e.foundation/e?filter=microg) \ No newline at end of file +- [microG projects on /e/OS Gitlab](https://gitlab.e.foundation/e?filter=microg) diff --git a/htdocs/pages/support_topics/calls_to_google_servers.md b/htdocs/pages/support_topics/calls_to_google_servers.md new file mode 100644 index 0000000000000000000000000000000000000000..efc91c163fd8ec3c466a61339a173051d1741b89 --- /dev/null +++ b/htdocs/pages/support_topics/calls_to_google_servers.md @@ -0,0 +1,9 @@ +--- +layout: page +title: Calls to Google servers +namespace: support-topics/calls_to_google_servers +permalink: /calls_to_google_servers +toc: true +--- + +{% tf pages/support_topics/calls_to_google_servers.md %}