Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 1a022d5b authored by Florian Bausch's avatar Florian Bausch Committed by Weblate
Browse files

Translated using Weblate (Portuguese (Brazil)) 

Currently translated at 40.0% (16 of 40 strings)

Translation: /e/ support center/Pages/Support_Topics/Calls_To_Google_Servers
Translate-URL: https://i18n.e.foundation/projects/e-support-center/pagessupport_topicscalls_to_google_servers/pt_BR/
parent 4c3e5d7d

htdocs/_i18n/pt_BR/pages/support_topics/calls_to_google_servers.md

+1 −1
Original line number Diff line number Diff line
@@ -30,7 +30,7 @@ In order to get access to the Google API (mainly to get access to notifications) 


Please note you can define another profile from **Settings** > **System** > **Advanced** > **microG** > **Google device registration** > **Select profile**



## Push Notifications (microG)

## Notificações Push (microG)



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.