Just to nitpick, it’s the same privacy as your card. It’s more secure than your card. Different things.
It is indeed both more private and more secure than Google Pay though.
1 Like
Thank you a lot !
From a pragmatic perspective (not ideological about FOSS), doesn’t enabling Google Play Services - even if sandboxed and via microG compromise any privacy advantage GrapheneOS has over iOS.
Your phone is still making outgoing requests that end up on Google’s servers.
I know that iOS is dependent on Apple’s cloud infrastructure for many things - Push Notifications, Application Signing, the App Store. I’m not trying to imply that iOS is anywhere close to zero telemetry.
Apple’s implementation of E2EE in their services, regular pushbacks on government backdoors, and overall privacy policy proves to me that it is the lesser of two evils.
If you use apps that require Google Play Services, then in my opinion you’re better off using iOS.
1 Like
Google’s tracking can be significantly reduced in your account settings. Moreover, Google would see which apps you installed, but not the notification content. IIRC, Android encrypts most notifications.
That doesn’t change anything I’ve said.
You can take steps to limit Apple’s telemetry as well.
Your second statement about notification content is false.
By default Android’s notifications are only encrypted in transit. Individual developers have to do the extra legwork to encrypt their payloads themselves.
However, messages are not encrypted end-to-end (E2E) between the developer server and the user device unless developers take special measures.
A direct quote from Google’s Security Blog.
The same is true for iOS. Developers can choose to encrypt their payloads if they wish.
2 Likes