Privacy policy
What the app stores
Your vault lives in a single encrypted file on your phone. Its key derives from your master password and from a secret sealed in the phone's secure hardware. The file leaves the device only when you export it yourself.
What leaves the device
Nothing leaves on its own. Backups and exports exist only when you create them, and they go where you send them through the system share sheet. An exported backup is protected by your recovery passphrase alone, so treat the passphrase with the same care as the file.
What we receive
Nothing. No analytics, no crash reporting, no telemetry, no advertising identifiers, no third-party SDKs. There is no data to sell, share, or lose.
How to verify this
The Android build requests no INTERNET permission, which one command confirms. The iOS app and its autofill extension carry no network entitlements. The source is public, and releases are reproducible, so you can build the app yourself and compare binaries.
Permissions the app does use
Biometric unlock. Face ID, Touch ID, and fingerprint checks run inside the operating system's secure hardware. Stonevault receives a yes or a no, never the biometric itself.
Autofill. The credential provider on iOS and the autofill service on Android let Stonevault fill passwords in other apps when you ask it to. Both run locally.
The app stores
If you install through the App Store or Google Play, Apple and Google show us aggregate install counts. That measurement happens in the store, under their policies. The app itself contributes nothing beyond existing.
This website
Static files. No cookies, no analytics, no third-party requests.
Your rights
Data protection laws give you rights to access, correct, and delete personal data. Stonevault satisfies them by default: there is nothing to access, nothing to correct, and nothing to delete.
Changes
If this policy changes, the change ships with an app update and is recorded in the repository history, where you can diff it like anything else.