Last updated: August 13, 2026
Safety Vault is a local-first password manager. This Privacy Policy explains what information the application handles and how it is protected.
Safety Vault does not collect, sell, or share personal information with the developer or with third parties.
The application is designed to operate without a user account, cloud account, or backend server. Information that users enter into the vault may include:
This information is stored locally on the user's device and is not transmitted to Safety Vault servers.
The vault is encrypted locally. Safety Vault uses cryptographic protections including PGP encryption, Argon2id key derivation, and HMAC-SHA256 integrity protection.
The application does not maintain a cloud copy of the vault and does not provide automatic cloud synchronization.
Safety Vault allows users to explicitly export or back up their data. Exported data is created as a result of an action initiated by the user.
Encrypted exports use PGP protection by default. The application may also allow a user to intentionally export data in an unencrypted format, with a warning that the resulting file contains sensitive information.
Once a user exports or backs up information, the resulting file is under the user's control. Safety Vault does not upload or store those files on the developer's servers.
Safety Vault does not use advertising SDKs, analytics services, or third-party tracking services to profile users or track their activity.
Safety Vault does not require a cloud service, user account, or third-party data-processing service to store or synchronize the user's vault.
The application may contain platform-required permissions or components needed for normal functionality. These permissions do not mean that the contents of the user's vault are collected by the developer.
Safety Vault does not knowingly collect personal information from children or from any other users because the application is designed not to collect personal information.
Because vault data is stored locally, users can delete their stored data by deleting the corresponding vault data from the device or by using the application's data-deletion functionality where available.
Deleting the application may not necessarily delete every file that a user intentionally exported outside the application. Users should delete exported or backup files separately if they no longer want to keep them.
This Privacy Policy may be updated when the application's data practices change. The latest version will be published at the public URL where this policy is hosted.
For questions about this Privacy Policy or Safety Vault's privacy practices, please contact the developer through the project's public GitHub repository: