Privacy Policy

Scope of this policy

This policy applies to Rclone Drive Connector, a privately operated Google OAuth client used by its owner to connect the open-source rclone software to the owner's own Google Drive account. It is not offered as a public service and does not support third-party user accounts.

This informational website is static. It does not itself sign users in, process OAuth callbacks, receive Drive files, or operate an application database.

Google data the app accesses

When the owner grants permission, rclone may use the OAuth client to access Google Drive file and folder information, including file names, identifiers, metadata, folder structure, and file contents. Depending on the rclone operation the owner chooses, it may also create, upload, download, copy, move, rename, or delete Drive files and folders.

The app does not request access to Gmail, Google Contacts, Google Calendar, or unrelated Google Account profile data.

How Google data is used

Google Drive data is used only to perform file-management and synchronization actions initiated by the owner through rclone, including backups, transfers, listings, and integrity checks. The data is not used for advertising, profiling, surveillance, credit decisions, or training generalized artificial-intelligence or machine-learning models.

Use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Storage and retention

OAuth access and refresh tokens are stored by rclone in the owner's local rclone configuration file on devices controlled by the owner. Google Drive data may be stored locally only when the owner downloads or synchronizes it. This website does not receive or store those tokens or files.

Local files and tokens remain until the owner removes them, deletes the rclone configuration, or revokes the app's Google Account access. Google retains Drive data according to the owner's Google Account settings and Google's policies.

Sharing and disclosure

Google user data is not sold, rented, licensed, or shared with advertisers, data brokers, or unrelated third parties. Data moves only between Google Drive, rclone, and storage destinations deliberately configured and controlled by the owner.

Information may be disclosed only if required by applicable law or necessary to protect against fraud, abuse, or a security threat. Because this is a personal local setup, no employees or contractors are given access to Google user data.

Security

The owner is responsible for securing devices, rclone configuration files, encryption keys, and any configured storage destination. Reasonable safeguards include device access controls, operating-system updates, restricted file permissions, and encryption where appropriate.

No method of electronic storage is completely secure. If a token may have been exposed, access should be revoked immediately and the local rclone configuration replaced.

Your controls and deletion

The connected Google Account owner can review or revoke access at any time from the Google Account third-party connections page. The owner can also delete the relevant rclone remote or configuration file from their devices and remove any locally synchronized copies.

Revoking access prevents new API access. It does not automatically delete files already copied to a destination chosen by the owner; those copies must be deleted at that destination.

Website data

This site does not use account registration, analytics, advertising pixels, or marketing cookies. The hosting provider may process standard technical request data—such as IP address, browser information, requested URL, and timestamp—to deliver and protect the site, subject to the provider's own retention and security practices.

Changes and contact

This policy may be updated if the app's operation or legal obligations change. Material changes will be published on this page before the new practices take effect. The effective date below identifies the current version.

Questions or privacy concerns may be directed to the support contact shown on the app's Google OAuth consent screen. As this is a single-owner utility, that address reaches the app owner directly.