Privacy policy

Last updated: 27 July 2026

This policy covers once-backup, a personal backup utility published at olibano.dev by Ivan Vega.

What the application does

once-backup runs on hardware I own and operate. It copies my own backup archives to my own Google Drive account so that a second, offsite copy exists. It is a single-user tool: the only Google account it ever connects to is the account of the person who runs it.

Google user data accessed

The application requests a single OAuth scope, https://www.googleapis.com/auth/drive.file. This scope grants access only to files that the application itself creates in Google Drive. It does not permit reading, listing, or modifying any other file or folder in the account.

Within that scope the application only ever creates, reads back, and deletes the backup archive files it has written itself, inside a single folder it creates for that purpose.

How the data is used

Google Drive is used solely as file storage for backup archives. The application does not analyze, index, or otherwise process the contents of the Drive account, and it does not use Google user data to train any model.

Storage, encryption, and retention

• All archives are encrypted locally, before upload, using the restic backup format. The encryption key never leaves the local machine, so the uploaded contents are not readable by anyone who does not hold that key.
• OAuth credentials are stored only in a local configuration file on the machine that runs the tool, readable only by that user account.
• Old archives are removed on a retention schedule; the current schedule keeps daily, monthly, and yearly snapshots for a bounded period.

Sharing

No data is transmitted to, sold to, or shared with any third party. There is no server-side component that receives user data — the application runs entirely on the user's own machine and communicates only with Google's APIs.

Revoking access

Access can be revoked at any time from Google Account permissions. Revoking access immediately stops the application from reaching Drive. Files it has already written remain in the Drive account and can be deleted normally.

Contact

Questions about this policy: ivanvega@gmail.com.