Personal Rclone Backup

Privacy Policy

Last updated: November 9, 2026

This notice describes a personal backup setup operated by umutcagand. Rclone is used to access my own Google Drive account, and Restic is used to create encrypted backups. This is not a public backup service: visitors to this portfolio are not asked to connect their Google accounts.

Google data accessed

After I explicitly authorize the application, Rclone can list, read, create, update, and delete files in the Google Drive account I select. Full Drive access is requested so Restic can maintain its backup repository, including snapshots, retention, and pruning. This access is used only for operating and restoring personal backups.

How information is used and stored

Restic encrypts backup contents locally before uploading them through Rclone to Google Drive. Backup repository files are stored in Google Drive; Rclone OAuth authorization tokens are stored in the local Rclone configuration on my computer, not on this portfolio website. The website does not receive Google Drive files, OAuth tokens, or Google account data from its visitors.

Sharing and disclosure

Google Drive provides the cloud storage for the encrypted backup repository. I do not sell Google user data, use it for advertising, or share it with unrelated third parties. Access is limited to the functionality needed for personal backups.

Retention and deletion

When scheduled backups are enabled, Restic is configured to retain up to seven daily, four weekly, and six monthly snapshots, with repository pruning. Backup data can also be removed directly from Google Drive. Google account access can be revoked at any time from Google Account connections. Revoking access stops future access but does not automatically delete previously uploaded backup files.

Contact

Questions about this personal application or privacy notice can be directed to the operator via GitHub.