Where protocol data lives
On your device, in the app’s SQLCipher-encrypted local database.
What stays on your device, what can leave it, and the choices you control—without dense legal language.
Protocol Vault’s core features run locally. The app does not need a Protocol Vault cloud account to organize your entries.
On your device, in the app’s SQLCipher-encrypted local database.
We do not receive your vault contents through normal app use.
When you deliberately export, enable a backup, or include information in a support request.
You do. Delete entries in the app or erase all app storage from device settings.
The app’s privacy boundary is your device. Optional actions can move data beyond that boundary only when you choose them.
The entry is written to the encrypted app database.
Viewing, editing, and completing protocols does not require our server.
A copy goes to the destination you select. That provider’s terms apply there.
Local deletion removes the selected data or app storage. Delete external copies separately.
This page helps explain the app’s data practices. The official store Data safety form will reflect the released build and any included platform services.
Core protocol details stay on-device and are not transmitted to Protocol Vault servers.
No advertising profiles, data brokerage, or cross-app behavioral targeting.
SQLCipher protects data stored by the app. Device security remains part of the protection model.
Local database encryption protects stored app data. It does not make screenshots, exported files, unlocked devices, or third-party backup destinations automatically private.
Read the legal details, including website hosting, support communications, retention, and policy updates.