Privacy Policy
Scope
This policy describes data handling for KEYVA’s vault, password generator and authenticator. There is no online account registration or cloud sync. Core vault features work offline; third-party components may make the diagnostic network requests described below.
Passwords & local storage
Accounts, passwords, websites, notes and authenticator secrets are encrypted on your device to provide vault and code features. Your master password derives an encryption key and is not saved as a password. Preferences are stored separately. The developer operates no vault upload or sync server.
Face ID & fingerprints
The operating system handles biometrics; KEYVA does not read or store face or fingerprint templates. Enabling it protects the derived vault key using device security storage. You may disable it and use your master password, which is also required when biometrics are unavailable.
Camera, photos & clipboard
Camera access is requested when you scan an authenticator QR; selected photos serve the same purpose. Manual entry remains available if access is denied. Copying writes to the system clipboard, which other apps may access. Sensitive copies are cleared after about 30 seconds when possible; OS limits may prevent this.
Third-party components & diagnostics
KEYVA uses the DCloud uni-app x runtime. iOS scanning uses Google ML Kit, which may send device/app details, installation identifiers and performance/usage diagnostics to Google. QR recognition runs on-device. The developer enables no advertising or cross-app tracking. Automatic DCloud crash reporting is disabled in the current native iOS build.
Backups & sharing
Encrypted backups are copied only at your request. You choose where to keep them; external storage, email and other apps follow their own policies. If you email support, your email provider processes that correspondence and the developer uses it to respond. Never attach passwords, secrets or backups.
Retention, deletion & recovery
Entries remain until you delete them or clear app data. Deleting an entry rewrites the current encrypted vault; it does not remove old backups or guarantee physical flash erasure. OS backups or security storage may persist after uninstalling. Disable biometrics and manage your backups when leaving. The developer cannot decrypt, recover your master password or remotely erase your device.
Updates & privacy requests
We will update this policy and its date when practices change. Contact the developer below with privacy questions or requests to delete support correspondence. Records legally required to be retained are limited to what is necessary. KEYVA is not directed at children and does not request birth dates or ages.
Google ML Kit data disclosure · Google Privacy Policy · DCloud Privacy Policy