@@ -25,7 +25,7 @@ Please note you can define another profile from **Settings** > **System** > **Ad
## 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.
A large number of Android applications are using and embedding the Google Push notifications framework to have notification messages received by users. As this framework is relying on the Google servers infrastructure, connecting to Google servers is needed to have Google Push notifications work. 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