Updated October 5, 2026.
rclone-google-drive is a personal desktop OAuth client used with locally installed rclone. It accesses Google Drive only after its owner authorizes it.
The Google Drive authorization permits viewing, editing, creating, and deleting files. The configured backup workflow copies selected local files to the owner's existing Drive destination and reads file metadata and content as needed to list, compare, and verify transfers. The backup commands use copy and verification operations and retain local files.
OAuth tokens and configuration are stored on the owner's computer in a private local configuration file. Transfer and error logs are also stored locally and may include file names, paths, sizes, and transfer status. With an encrypted rclone remote, file contents and configured file names are encrypted locally before transfer; the encryption keys remain on the owner's computer. Google receives the uploaded files in their configured form and the API requests needed to transfer and verify them.
This personal workflow does not sell user data, use it for advertising, or send it to an additional application developer's server. Google handles data received by its services under its own policies. Anyone who receives the client's configuration or local computer access may be able to access its authorization; keep those credentials private.
These informational pages are hosted by GitLab Pages. They contain no application login, forms, analytics scripts, or uploaded user files. The hosting provider may process ordinary request information, such as IP addresses, under its own policies.
The owner can stop the local client, remove its local credentials, or revoke its authorization in Google Account connections. Revoking authorization does not automatically delete files previously uploaded to Google Drive. Those files remain under the owner's control in Google Drive.