Privacy policy

Effective date: 15 November 2026

This policy describes the owner's private, locally operated Personal Backup Utilities and this informational website.

Google Drive data and purpose

The utilities access Google Drive file contents and metadata only as permitted by the user's Google authorization and selected operation. Operations include downloading selected archives, uploading encrypted Veeam computer backups, downloading backups for recovery, verifying transfers, and managing retention of the utilities' backup copies.

The backup connection requests access to files created or opened with that application through the Google Drive drive.file permission. Other separately configured download tools may use permissions granted for their specific download task. The utilities do not automatically grant themselves additional permissions.

Storage and security

OAuth client credentials and authorization tokens remain in protected configuration files on the user's device and are sent to Google when required for authorization and API requests. They are not embedded in this website or published in its repository.

Computer backups are encrypted locally by Veeam before upload. The user retains the backup encryption password separately. The utilities store backup files in the user's Google Drive and local locations chosen by the user; they do not publish those files or provide a public file-sharing service.

Local operational logs may contain backup filenames, transfer statistics, and status information. They are not intentionally used to record passwords, authorization codes, or access and refresh tokens.

Use and disclosure

The utilities do not sell Google user data, use it for advertising, or use it to train machine-learning models. Data transfers are between the user's selected local storage and Google Drive as needed for the requested backup or download operation. No separate operator-hosted backend receives the files or tokens.

Retention, deletion, and control

Local files remain until the user or their configured retention policy removes them. Cloud backup retention applies only to copies managed by the utilities. Depending on the configured policy, expired managed copies may be moved to Google Drive Trash or permanently deleted. Removing local files or revoking Google authorization does not automatically delete existing cloud backups.

The user can stop the utilities, remove their local configuration, delete their backup copies in Google Drive, and revoke the application's access through Google Account connections.

This website

These static pages have no forms, application login, analytics, advertising, or Google authorization flow. They do not intentionally set application cookies or use browser storage. Visiting them does not give the website access to Google Drive.

If published with GitHub Pages, the hosting provider may process technical request information under its own policies. See the GitHub General Privacy Statement. Google processes Google Account and Drive data under the Google Privacy Policy.

Contact and changes

For questions about these utilities or this policy, contact the repository owner via their GitHub profile. Do not post credentials, private file contents, authorization codes, or tokens in public GitHub content.

This policy may be updated if the utilities' data handling changes. The effective date above identifies the current version.