Privacy Policy
Last updated: October 9, 2026
This policy describes a personal Google Drive integration using the open-source rclone command-line application and a Google OAuth client controlled by the account owner.
Information accessed
When authorized, rclone can request the Google Drive access granted through the Google OAuth consent process. Depending on the scope approved, this may include listing, reading, uploading, editing, or deleting Drive files. The account owner controls commands issued to rclone.
Use and storage
Rclone uses Google account authorization tokens to make requests to Google Drive. Its configuration, including OAuth tokens, is stored on the device or other storage location configured by the operator. Files may be transferred to local or remote destinations selected by the operator. The Google Drive service processes API requests as described in Google's own privacy terms.
Sharing and hosting
This informational GitHub Pages website does not request Google sign-in or receive Google Drive files or OAuth tokens. No separate hosted application backend is provided by this site. GitHub may process ordinary website visitor data under its own policies.
Retention and control
Any copies or logs created by rclone are controlled through the operator's local configuration and chosen storage destinations. Google account access can be revoked in Google Account connections. Local rclone credentials and transferred files must be managed separately.
Security
OAuth client secrets and authorization tokens are not intentionally published through this website. Access and protection of local rclone configuration files are the responsibility of the operator.
Contact
This is a personal-use integration, not a public service. For concerns about authorization, use Google Account settings to review or revoke access.