Rclone · Personal Google Drive connection
Privacy policy
This policy explains how Yamen Fahham’s personal Rclone configuration handles Google Drive information.
Scope and purpose
This is a personal configuration of the open-source Rclone program, maintained by Yamen Fahham for his own Google Drive. It is used to list, check, transfer, synchronise and organise files on the owner’s instructions. It is not a public file-management service.
Google API data is used for those file-management tasks in accordance with the Google API Services User Data Policy, including its Limited Use requirements.
Data accessed
Depending on the command and permission granted, Rclone can access:
- File and folder names, identifiers, sizes, timestamps and other Drive metadata.
- File contents needed for a requested transfer, comparison or other file operation.
- Google account information and authorisation tokens needed to identify the connection and authenticate requests.
The connection requests access to view and manage existing Drive files, including creating, changing, moving and deleting them. Google handles sign-in; the owner’s Google password is not given to Rclone.
Processing, storage and protection
Rclone communicates with Google from the owner’s computer over HTTPS. Connection tokens are stored in Rclone’s local configuration. Requested downloads, local copies, caches and any enabled logs may also remain on the computer.
The owner controls access to these local files through Windows permissions and any Rclone configuration encryption he enables. Credentials and Drive files are not included in these information pages. Running Rclone does not send this configuration’s tokens or file data to the Rclone project’s developers.
Sharing and AI assistance
Google processes requests under its own privacy policy. If the owner directs a transfer to another storage service or recipient, that destination receives the selected data.
The owner may use OpenAI Codex to issue commands and review results. Relevant filenames, metadata, command output and specifically requested file content may then be processed by OpenAI to carry out those instructions, under its applicable terms, privacy policy and the owner’s account controls.
Google Drive data must not be used to develop, improve or train general-purpose AI or machine-learning models. AI-assisted use is permitted only with terms and data controls consistent with that restriction. This personal configuration does not sell Drive data or use it for advertising, profiling or credit decisions.
Retention, deletion and access
Local connection details remain until the owner removes them. Downloaded files, logs, caches and backups remain subject to the owner’s storage and cleanup choices. Information shared with Google or OpenAI is subject to the relevant service’s retention rules and account controls.
The owner can disconnect this setup through Google Account connections and remove the remote configuration in Rclone. Revoking access prevents further authorised access through the connection; it does not erase existing local copies or chat records. Those must be removed separately. Removing connection details does not delete the original Drive files.
These information pages
These pages do not provide Drive sign-in, file uploads, forms, advertising or analytics. They do not set cookies or load tracking scripts. The website’s hosting service may process routine request details, such as IP addresses and browser information, to deliver and protect the pages.
Contact and changes
Questions or requests about this personal setup can be sent to Yamen Fahham at Mail@YamenFahham.com.
This policy will be updated if the setup’s data handling changes. Material changes will be explained before additional data use, with renewed consent where required.