Vaultwarden Backups privacy policy
Last updated: October 11, 2026.
Purpose and operator
Vaultwarden Backups is a private, single-user utility operated by Mykhaylo Tymofyeyev. It stores encrypted backups of his self-hosted Vaultwarden instance in his own Google Drive. It is not offered to the public. This policy describes the backup utility, not the privacy practices of Bitwarden, Vaultwarden, or Google.
Google data accessed
The utility uses Google OAuth authorization with the drive.filescope. It creates backup files and folders and accesses their contents and metadata, such as names, sizes, and identifiers, for upload verification and recovery. It does not request Gmail access or unrestricted access to existing Google Drive files.
Use and storage
Backup archives contain the Vaultwarden database, associated server files, and recovery configuration. Archives are encrypted on the operator’s server before upload. The backup encryption passphrase is not included in uploaded archives. Encrypted copies are stored locally and in the operator’s Google Drive.
OAuth credentials are stored locally on the operator’s server to authorize Drive access. Recovery tests may temporarily create decrypted files in a restricted local directory. These files are not uploaded by the backup workflow. Encryption does not protect against compromise of the source server or exposure of the recovery passphrase.
Sharing and Google API data
The operator does not sell backup data or Google user data, share it with advertisers, or use it for advertising, profiling, or training AI models. Google processes the encrypted archives as the selected storage provider. Data accessed through Google APIs is used only for the backup, verification, and recovery functions described here.
The utility’s use of information received from Google APIs adheres to theGoogle API Services User Data Policy, including its Limited Use requirements.
Retention, deletion, and revocation
The operator retains backups until he deletes them; there is no fixed automatic retention period. Backups can be deleted from Google Drive and local storage. Files placed in Drive’s trash remain subject to Google’s trash retention and deletion behavior. Local recovery-test files are managed separately.
Google authorization can be revoked through theGoogle Account connections page. Revocation prevents future authorized access but does not automatically delete existing backups. Local OAuth credentials can also be removed from the server.
This public website
Visiting this documentation does not grant Google access or expose a vault. The website’s hosting provider, Vercel, may process technical request information and site analytics under its own privacy practices. This is separate from the private Google Drive backup workflow.
Contact and changes
Contact mykhaylo.tymofyeyev@gmail.comwith questions. Material changes to this utility’s data handling will be reflected on this page with an updated date.