Personal Drive Backup

Privacy Policy

Last updated: October 27, 2026

Purpose and scope

This personal-use OAuth client authorizes rclone to use the Google Drive API for backing up and restoring the owner's files. The requested permission is the Google Drive per-file scope (drive.file), as configured in rclone.

Information accessed and used

Through the owner's authorization, the backup software can access the Google Drive files permitted by its OAuth scope. It uses this access only to create, upload, list, read, and restore backup repository files as required for backup operations.

Storage and security

Backup contents are encrypted on the owner's device by restic before upload to Google Drive. rclone stores its OAuth configuration and credentials locally on the owner's device. The owner is responsible for securing these files and the restic encryption password. Google Drive holds the encrypted repository and processes it according to Google's applicable terms and policies.

Disclosure and sharing

This workflow does not sell Google user data or use it for advertising. It does not transfer Google user data to an operator-run third-party analytics or advertising service. Google Drive is used as the storage provider for the encrypted backups.

Retention and deletion

Encrypted backups are retained according to the owner's restic retention configuration. The owner may delete repositories from Google Drive and revoke this OAuth client's access through their Google Account security settings.

Public website

This informational website does not require visitors to sign in and does not intentionally collect information through forms, analytics scripts, or cookies. The website host may process routine technical request data under its own policies.

Updates

This policy will be updated if the backup workflow's data-handling practices change.