Privacy Policy

Last updated: 2026-10-10

This notice describes a personal, single-user setup using rclone to back up selected files to the user's own Google Drive account. Home | Terms of Service

Google data accessed and purpose

rclone runs on the user's own computer and uses Google Drive API access to list, read, transfer, and verify files for backup. Depending on the Google OAuth scope granted and the rclone command used, it may also create, update, or delete files. A broad Drive scope can permit access to files across the Google Drive account. The Google consent screen shows the permissions being requested.

Google user data is used only to provide this backup and verification function. It is not used for advertising, sold, or shared with unrelated parties. Use of Google user data follows the Google API Services User Data Policy , including its Limited Use requirements.

Storage and sharing

File transfers take place between the user's computer and the user's Google Drive. The source files and rclone configuration, including OAuth tokens, remain on the user's computer. Backup copies are stored in the user's Google Drive. This website does not receive or store Drive files, OAuth tokens, or client credentials.

Google processes the data sent to Drive under Google's applicable policies. This site is hosted by GitHub Pages. GitHub logs visitors' IP addresses for security purposes; see the GitHub General Privacy Statement . This site does not use advertising or analytics scripts.

Retention and revoking access

The user controls the source files, local rclone configuration, and backup copies in Google Drive. Revoking this application's access in Google Account settings stops future OAuth access, but does not automatically delete existing backup copies. Those copies must be deleted separately if desired.

Contact

For privacy questions, use the support email shown on the Google OAuth consent screen.