Privacy policy

Personal Backups is operated for the Google account owner’s private backup and recovery needs.

Data accessed and purpose

The application uses Google Drive file content and metadata for its backup objects, including file identifiers, names, sizes, and modification times. It uses this information to upload, locate, verify, restore, and remove backups. It also reads storage-quota information to assess available capacity.

Access is requested through the drive.file scope, which covers files created by the app or explicitly made available to it. The configured backup workflow uses the app’s backup folders. It does not request Gmail or Google Contacts access.

Storage and protection

Backup contents are encrypted on the operator’s computers using restic and rclone crypt before upload to Google Drive. Plaintext encryption keys are not sent to Google. Google still processes account, transfer, storage, and object metadata needed to provide Drive.

OAuth tokens and application credentials are stored in access-restricted configuration files on the operator’s computers so scheduled backups can run without repeated sign-in. Local backup software may keep operational logs, file paths, snapshot metadata, and caches needed for backup and recovery.

Sharing and other uses

Google processes the uploaded backup objects as the storage provider. The operator may also store independently encrypted copies of the same source files with another backup storage provider; Google OAuth tokens are not shared with that provider. Google user data is not sold or used for advertising, profiling, or training machine-learning models. There is no public service that distributes the backups to other users.

The application’s use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Retention and deletion

The operator controls backup retention and deletion. Older versions can remain until retention maintenance removes them; deleting a source file does not immediately delete its backup copies. The operator can remove stored backups and local credentials independently.

Access can be revoked through Google Account connections. Revocation stops further authorized API access but does not itself erase existing backups, local logs, or credentials. Those require separate deletion.

This website and contact

These static pages contain no sign-in form, analytics scripts, or tracking cookies. The website’s hosting provider may process ordinary request information to serve the pages. For questions or deletion requests, use the developer support email shown on the application’s Google authorization screen.