Privacy Policy

devrclone — personal rclone Google Drive OAuth client

Effective date: September 20, 2026

Overview

devrclone is a personal OAuth client used with rclone for backup and recovery to Google Drive. The website at yarr.icu is informational only; it does not operate the rclone client or receive Google Drive file contents.

Google user data accessed

The OAuth client requests the Google Drive drive.file scope. This allows rclone to access files and folders that the user creates, opens, or authorizes through this OAuth client.

How Google user data is used

Google Drive access is used only to perform user-directed personal backup, restore, synchronization, and file-management operations through rclone.

Storage of data and credentials

rclone runs on the user's own device. OAuth tokens and rclone configuration are stored locally by rclone on that device unless the user independently backs them up. Backup files may be encrypted locally by rclone before upload.

Sharing and disclosure

Google user data is not sold, rented, transferred for advertising, or used for behavioral profiling. This informational website does not receive or store Google Drive file contents.

Tracking, analytics, and cookies

This website does not intentionally use analytics, advertising, tracking scripts, or application cookies.

Data retention and deletion

The OAuth client itself does not maintain a separate server-side database of Google user data. Files stored in Google Drive remain under the user's control and can be deleted by the user. Local OAuth tokens and rclone configuration can be removed by deleting or revoking the local rclone configuration and by revoking the application's Google account access.

Limited use

Use of information received from Google APIs is limited to providing the user-requested backup and file-management functionality described above and is intended to comply with applicable Google API Services User Data Policy requirements.

Changes

This policy may be updated if the OAuth client, requested scopes, or data handling practices change. The current version will be published at this URL.

Contact

Questions about this OAuth client may be directed to the developer contact address configured in the Google OAuth consent screen.