Security, explained plainly

Trust facts,
not adjectives.

OwnVault reduces exposure by keeping vault data on your device. Here is what it protects, how it works, and where your responsibility begins.

No vault serverLocal-only architecture

Data protection

Two encryption boundaries.

01Individual secretsAES-256-GCM encrypts each password and hint.
02Whole databaseSQLCipher encrypts the complete vault database.
03Device protectionThe generated master key is held by iOS Keychain or Android Keystore.

What leaves your phone?

Your vault data does not. The app requests no network permission and has no server for password storage, sync, analytics, ads, or crash reporting.

How are backups protected?

Backups are user-initiated exports. A key is derived from your backup password with Argon2id, and the file is encrypted with AES-256-GCM. We cannot recover a forgotten backup password.

What about unlock secrets?

Your pattern and master PIN are not stored directly. Salted Argon2id hashes are used for verification. Biometric templates remain under operating-system control.

What happens on uninstall?

Uninstalling removes the local app data. OwnVault has no server copy to restore. Export and safely retain an encrypted backup before changing or erasing a device.

Important limitations

Local-only changes the trade-off.

No remote recovery

We cannot reset your vault or restore data from a server.

Backups are your responsibility

A lost phone without a valid encrypted backup may mean permanent data loss.

Device security still matters

Keep your operating system updated and protect your device passcode.

Local by design

Security you can understand before you install.

No account. No vault server. No subscription.