Sandboxed Google Play on GrapheneOS: how does it work?
The most common question about GrapheneOS: “Can I still use my apps?” The answer is nuanced — which is exactly why this article exists.

Sandboxed Google Play on GrapheneOS: how does it work?
The most common question about GrapheneOS: “Can I still use my apps?” The answer is nuanced — which is exactly why this article exists.
Who this guide is for
This guide is mainly for GrapheneOS users who are deciding whether app compatibility is a good reason to install sandboxed Google Play.
It fits especially:
- readers who want GrapheneOS but still need some banking, work, transport, or mainstream apps
- users comparing a lighter transition path against a stricter no-Google setup
- people who want to understand the compromise before installing anything
If you already know you want a no-Google setup and are willing to live within open-source alternatives, you probably do not need this page in detail.
What you gain, and what it costs
If you install sandboxed Google Play, you usually gain:
- access to a much wider set of mainstream apps
- fewer compatibility surprises in daily use
- a more realistic transition path from stock Android to GrapheneOS
But it also costs something:
- some continued data sharing with Google
- more trust in an ecosystem you may be trying to reduce dependence on
- more temptation to keep every mainstream default rather than deciding deliberately
For many readers this is still a reasonable trade. It becomes overkill only when “maximum de-Google” is your actual goal and you are installing Play mainly out of habit rather than need.
Regular Google Play vs. sandboxed Google Play
On a standard Android phone, Google Play is built into the system: GrapheneOS describes it as bypassing the app sandbox with a massive amount of highly privileged access. This is not a bug, it is by design.
Sandboxed Google Play is the official Google Play apps, installed as regular apps in the standard app sandbox, with no special access. Like any other app, they need your consent for standard permissions and profile data. They exist only in the user or work profile where you install them, and only apps in that profile that choose to use them can talk to them.
What it can do: install and update apps (you approve it as an app source), relay push notifications. What it cannot do: read other apps’ data, or get your location without permission. Apps that use Google Play location keep working without that permission, because GrapheneOS reroutes those requests to its own location service by default.
A Google account is optional for Play services, but the Play Store needs one to install apps.
Banking apps: do they work?
Mostly yes, but the picture is shifting. GrapheneOS says about 90% of European banking apps can be used on it (March 2026). Most need Play services, and for many it is enough to have sandboxed Google Play in the same profile.
The status of Dutch apps below comes from user reports, read on 7 November 2026: the community-run PrivSec list (GrapheneOS gives no guarantee for it) with its report threads, and the GrapheneOS forum. It can change with any app update.
- ABN AMRO, ING, bunq: reported working, the latest reports dating from March and April 2026; bunq’s report excludes NFC payments. ING told one user in March that people “will have” issues on GrapheneOS, and another user replied that it works for them.
- ASN, SNS: the apps open, but Wero payments have been blocked since October 2026; users trace it to a Play Integrity check. ASN support told users GrapheneOS is not supported for Wero. iDEAL | Wero payments get mixed reports.
- Knab: the selfie needed to link your account has failed since at least July 2026, and Knab told a user it does not support GrapheneOS.
- Rabobank: a user quoted Rabobank in April 2026 saying its app does not work on GrapheneOS because it does not meet the bank’s security requirements. It disappeared from the Play Store there, and installing via Aurora Store worked instead. Reports since say the face check fails and that versions 8.1.2 and 8.1.3 crash on memory tagging; one user got it running by turning memory tagging off for that app, which weakens a protection. One report says 8.1.3 is back in the Play Store, not yet tested. Don’t count on this app, and keep the web version in reach.
- DigiD app: users report it working (October 2026). If the DigiD website can’t find the app, add its link: Settings → Apps → DigiD → Open by default → Add link. GrapheneOS keeps such links off by default.
Why this happens: some apps use the Google Play Integrity API, and GrapheneOS isn’t certified by Google. Apps can support GrapheneOS through the standard Android hardware attestation API instead, which GrapheneOS fully supports. GrapheneOS says a growing number of apps that check for a certified OS now explicitly permit it.
Contactless payment: Google Pay does not work on GrapheneOS, because Google bans operating systems it hasn’t certified. GrapheneOS names Curve Pay and some European banks’ own tap-to-pay as working options.
If a banking app refuses to start: check whether the app is up to date. If you turned off Native code debugging (Settings → Security & privacy → Exploit protection), GrapheneOS suggests turning it back on. Then check the PrivSec list and the GrapheneOS forum for the current status of your app.
Alternatives to Google Play
F-Droid
Open-source apps, no account required; F-Droid says it doesn’t track what you install. The selection is more limited than Google Play but still covers many privacy-friendly alternatives.
Note: Google began rolling out mandatory developer verification for apps on certified Android devices on September 30, 2026. That first phase only covers installs from Google Play and six phone makers’ app stores (Samsung, Xiaomi, OPPO, vivo, HONOR, Transsion), for users in Brazil, Indonesia, Singapore, and Thailand; extending it to all apps, sideloaded and alternative stores included, is planned for 2027, worldwide (including NL/EU). Google says sideloading itself isn’t going away: an “advanced flow” will remain to install apps from unverified developers, plus a free limited-distribution account for hobbyists (up to 20 devices, no ID required). F-Droid is opposing the requirement, and how it will apply to alternative stores is still uncertain.
Google applies these checks to certified Android devices, and GrapheneOS isn’t certified. Our reading, not a statement from Google or GrapheneOS: the checks don’t bind a GrapheneOS phone directly, but F-Droid and its developers would still feel the effect elsewhere. Follow f-droid.org for updates.
Aurora Store
An open-source client that downloads apps from Google Play without your own Google account: by default it uses shared anonymous account credentials. GrapheneOS calls the Play Store app the most secure way to install and update Play apps. Useful, but not a full substitute for sandboxed Google Play when apps depend on Play Services, DRM, or stricter integrity checks.
Direct APK installation
For apps that offer an official APK (Signal, Proton Mail), you can install directly from the developer. This bypasses the Play Store entirely, but only works for apps that support direct distribution well.
When should you install sandboxed Google Play?
- You need apps that are genuinely not available any other way
- Your banking app needs Play services
- You want a normal Android experience with better security than stock
It doesn’t have to be everywhere: install it in a separate profile to choose which apps can use it.
When should you not install it?
- You want maximum isolation from Google services
- You are willing to use open-source alternatives for all functionality
- You accept that some apps will not work
The trade-off, stated plainly
Sandboxed Google Play is a compromise. It runs with far less access than regular Google Play, but whatever you and your apps send through it still reaches Google. If Google is part of your threat model, do not install it.
If your threat model is about advertisers, data breaches and general tracking — sandboxed Google Play is fine. It is a realistic middle ground between fully open and fully closed.
You can always install it, test it, and remove it again: open the GrapheneOS App Store and select Google Play services (first setup has the details), and uninstall it like any other app.
Next step
Go further
- Profiles on GrapheneOS — decide where to isolate Google-dependent apps
- GrapheneOS first setup — settings before this step
- F-Droid: apps without Google — open-source apps without Play