Privacy policy
Application: rclone-colab. Developer: Alex Gromer. Effective date: 30 October 2026.
1. What the application is
rclone-colab is a personal OAuth client used by the developer's own instance of rclone to access the developer's own Google Drive from compute sessions the developer starts (for example Google Colab runtimes). It is a single-user tool: the only Google account that authorises it is the developer's account. It is not distributed to, and must not be used by, other people.
2. Data the application accesses
- Google Drive files. With the
https://www.googleapis.com/auth/drivescope the application can list, read, create, update and delete files in the authorising account's Google Drive. In practice it works inside one folder chosen by the developer (model evaluation runs, checkpoints, logs, result summaries). - OAuth tokens. The access and refresh tokens issued by Google are stored only in places controlled by the developer: a password manager on the developer's workstation and the Secrets store of the developer's Google Colab account. They are never written into notebooks, repositories, logs or shared files.
- Basic account information that Google returns as part of the OAuth flow (account identifier). Nothing else is requested.
3. How the data is used
Drive data is used exclusively to synchronise files between the developer's Drive folder and the developer's compute sessions. No data is analysed for advertising, profiling or any purpose other than the file transfer the developer requests.
4. Sharing and third parties
No Google user data is sold, shared, transferred or disclosed to any third party. No third-party services receive the data. The application does not use Google user data to develop, improve or train machine-learning models, and does not transfer Google user data to any AI model.
5. Storage and retention
The application itself stores nothing except the OAuth tokens described above. Files remain in the developer's Google Drive and on the compute sessions for as long as the developer keeps them; the developer can delete them at any time through Google Drive. Tokens can be revoked at any time at myaccount.google.com/permissions, which immediately ends all access.
6. Security
Tokens are kept in encrypted stores (a password manager and Colab Secrets) with access limited to the developer's accounts. Transfers use HTTPS to Google's APIs only.
7. Google API Services User Data Policy
The application's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
8. Changes and contact
Changes to this policy are published on this page with a new effective date. Questions: through GitHub. See also the terms of service and the application page.