rclone

rclone · Tyler Albee

Privacy policy

Effective September 16, 2026

This policy covers the Google OAuth application named rclone, configured and operated by Tyler Albee for personal file management on his desktop.

This is a personal configuration of the open-source rclone software for use with Tyler’s own Google account. This website and OAuth client are operated independently of the rclone project and Google.

1. Information accessed

Within the Google permissions granted, the app accesses Drive file and folder metadata, such as names, identifiers, sizes, and modification times, and file contents needed for requested operations. It uses OAuth access and refresh tokens to authorize requests. Account details, such as an email address, may be returned by Google to identify the connected account.

2. How information is used

Information is used only to carry out Tyler’s file management commands: listing, copying, downloading, uploading, backing up, synchronizing, moving, or deleting files, as permitted by the selected authorization scope. Tokens are used to maintain that authorized connection. Access is limited to the permissions needed for the configured file operations.

Google user data is not sold, used for advertising or profiling, or used to train AI models.

3. Storage and protection

Rclone runs on Tyler’s desktop and communicates with Google over HTTPS. Its local configuration stores authorization tokens. Downloads, caches, logs, and backups may retain file contents, metadata, or configuration according to the local settings and commands used.

Tyler controls access to the desktop and its stored data. Configuration encryption is an optional rclone setting; this policy does not imply that it is enabled. This information website does not receive or store Drive files or the desktop app’s OAuth tokens.

4. Sharing and transfers

Google processes API requests and stores files in Google Drive under its own privacy policy. The desktop receives files that Tyler chooses to download. If Tyler directs rclone to copy files to another configured location or provider, that destination receives those files under its applicable terms.

No access to Google user data is provided to advertisers, data brokers, or the rclone project’s developers through this personal setup. Any disclosure for security or legal reasons must comply with Google’s Limited Use requirements.

5. Retention, deletion, and revoking access

Tokens remain in the local configuration until removed or replaced. Files, logs, caches, and backups remain in their configured locations until Tyler deletes them or the applicable retention settings remove them.

  1. Revoke the app’s authorization in Google Account connections to stop future authorized access.
  2. Remove the Google Drive remote from the local rclone configuration and remove any configuration backups containing its tokens.
  3. Delete any downloaded files, caches, logs, or other copies that are no longer needed, including copies at other configured destinations.

Revoking access does not delete existing files in Google Drive or copies already transferred elsewhere.

6. Google API Limited Use

This app’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

7. Visiting this website

These pages contain no analytics scripts, advertising, sign-in forms, or app-managed cookies. The hosting infrastructure may process technical request data, such as IP address, browser information, requested URL, and access time, to deliver and secure the website. This technical website traffic is separate from the desktop app’s Google Drive data.

8. Contact and policy changes

The operator is Tyler Albee. For questions about this personal OAuth app or its data practices, use the user support email associated with the app on Google’s authorization screen.

Updates will appear on this page with a revised effective date. Any new use of Google user data will be disclosed and authorized before it begins.