Passfold on GrapheneOS: a hardened phone, a local wallet
GrapheneOS hardens the operating system. Passfold keeps the wallet on that phone. Together they are a strong pairing — if we stay honest about what each layer does.
Why GrapheneOS users look for a different wallet
People install GrapheneOS because they want a modern Android device with a smaller attack surface, tighter sandboxing, and no assumption that Google services must be present. A wallet that quietly syncs boarding passes and IDs to a vendor cloud fights that choice. You locked down the OS, then invited a second copy of your life onto someone else’s infrastructure.
A local wallet is the matching application. Passfold stores encrypted passes, cards, documents, and vault credentials on the device. There is no Passfold account. There is no cloud sync of wallet data. Android auto-backup of the app is off.
What works well on a hardened phone
- No internet permission. The app is not designed to phone home with your cards. Your tickets do not need a Passfold session to exist.
- On-device encryption. SQLCipher, Android Keystore, and AES-GCM protect data at rest on the same hardware GrapheneOS already treats as the trust boundary.
- Backups you control. Export an encrypted file when you want a copy. Store it offline. GrapheneOS users already think this way about device backups they keep themselves.
- Install without a Google identity. You can buy the APK from passfold.app and sideload it. Play Store is optional, not required to own the wallet.
What we will not claim
Passfold is not “Google-free software.” Barcode scanning uses Google ML Kit. In-app review uses Play libraries. Those dependencies exist. On GrapheneOS, the core wallet — encrypted storage, app lock, vault, widgets, exported backups — does not need a Google account. Camera barcode import may need the bundled ML Kit model, or sandboxed Play services if you have chosen to install them. We will not pretend otherwise.
We also do not claim a formal GrapheneOS audit, compatibility badge, or that every feature has been certified on every Pixel generation. The product design is local-first. That is the fit. Users should test the flows they care about on their own device.
A clean split of responsibility
GrapheneOS reduces what the operating system and default apps exfiltrate. Passfold reduces what a wallet app itself uploads — which, for wallet contents, is nothing. Hardware-backed keys stay on the phone. You decide whether a backup file ever leaves it.
That split is why the pairing works. The OS is the floor. The wallet should not punch a hole in it with a mandatory account.
Practical setup
- Install Passfold from the APK you purchased, or from Play if you use sandboxed Play.
- Turn on the phone’s screen lock. Add an app PIN if you want a second gate.
- Put high-sensitivity logins and 2FA in the vault, not in an unlocked note.
- Export an encrypted backup after you have real data in the wallet. Keep the password offline.
For the architectural contrast, read cloud vs local wallets. The same promises are in the privacy policy.