Privacy Policy

Purpose

This integration enables personal file synchronization, backup, and file management through rclone. It is not a public service and does not offer accounts or access to third parties. In this policy, “the user” means the owner using the integration on their own systems.

Google user data accessed

Using the Google Drive permissions granted to this OAuth client, rclone accesses:

• Google Drive file and folder metadata, such as names, identifiers, sizes, and modification times.
• File contents when requested for upload, download, synchronization, or backup.
• Other data necessary for normal Google Drive file-management operations performed by rclone.

Rclone communicates with Google from the devices or servers where it runs. Google user data does not pass through this static website.

How data is used

Google user data is used only to perform synchronization, backup, upload, download, listing, and file-management operations initiated through rclone, including any scheduled tasks the user configures.

Where data is stored

Google Drive files may be copied to the user's own devices or servers as part of synchronization or backup. OAuth credentials and refresh/access tokens are stored by rclone on the devices or servers where rclone is configured.

This website is informational only. It does not operate an application backend service or database that collects Google user data, and it does not receive or store Google Drive files or OAuth tokens. It uses no cookies, analytics, or tracking.

Sharing

Google user data is not sold, used for advertising, or shared with unrelated third parties by this application. Transfers take place between Google Drive and the user's own systems as directed through rclone.

Data retention

Locally synchronized files and backup copies remain on the user's own systems according to their backup and synchronization configuration. The user manages deletion of those copies.

Rclone's ability to access Google Drive remains until authorization is revoked or the credentials are removed from the systems where rclone runs, unless access expires or is otherwise invalidated. Removing local credentials does not itself revoke the permission recorded in the Google Account. Revoking access does not delete previously synchronized files or backups.

Revoking access

The user can revoke this application's access in their Google Account security or third-party access settings. Open Google Account third-party connections, select Personal Rclone Drive Integration (or the configured application name), and remove its access. Rclone will need new authorization to access Google Drive through this client afterward.

The user can also remove the corresponding rclone configuration and any saved credentials from their own devices or servers.

Security

The user should protect OAuth credentials, tokens, rclone configuration files, and the devices or servers where rclone runs. Appropriate steps include restricting access to those files and keeping local systems secure and up to date. No method of storage or transmission can be guaranteed completely secure.

Contact

For questions about this policy, contact s.keshav13142@gmail.com.