HuIk I looked into this a bit more and it turns out it’s basically a misunderstanding (luckily): GrapheneOS already isn’t Play Protect Certified, so a new OEM partnership (which is Motorola, by the way: here’s the link - https://motorolanews.com/motorola-three-new-b2b-solutions-at-mwc-2026/ | https://www.androidauthority.com/grapheneos-motorola-partnership-announced-3645710/) doesn’t change that. Play Protect Certification (the thing apps check via the Play Integrity API) needs Google Play Services to have deep, high-level root access to the OS. GrapheneOS purposely strips away those privileges, making Google Play Services run as a normal, unprivileged app in a secure sandbox. Since GrapheneOS won’t give Google that root access, Google won’t officially certify the OS.
That said, it doesn’t mean your banking apps (or others you can’t really do without) will stop working. Most standard banking apps don’t require this super-high level of hardware attestation and run just fine on GrapheneOS’s Sandboxed Google Play. Only a few apps that need absolute hardware-backed proof (like Google Pay) will still be incompatible.
The main risk is with certain institutions—like UBS—that actively try to block secure custom operating systems by enforcing Google’s strictest telemetry checks. This seems to be a growing trend that might become more common though.