Privacy policy

1. Information accessed

After the account owner authorizes access, the utility processes file contents and metadata needed for synchronization. This can include file names, folder paths, identifiers, sizes, modification times, and checksums where available. Provider identifiers and OAuth access and refresh tokens are used to connect to the authorized accounts.

OneDrive serves as the source; Google Drive serves as the destination. Access may include listing and reading files or metadata and creating, updating, or deleting destination files according to the configured operation. The permissions shown on each provider’s consent screen determine the actual scope of access; those permissions may cover more files than the selected sync folders.

2. Purpose and use

Information is used only to authorize connections, transfer the owner’s selected files, compare source and destination state, and diagnose sync errors. Data is not sold, used for advertising, or used to develop, improve, or train generalized AI or machine learning models.

3. Where data is processed and shared

rclone runs on a machine controlled by the owner and communicates with Microsoft and Google APIs. Selected OneDrive file contents and metadata are transferred to Google Drive as requested by the owner. Files may pass through local memory or temporary storage during transfer. This static website does not receive cloud files or OAuth tokens.

No separate analytics, advertising, or data brokerage services are part of the utility. Microsoft, Google, and the website hosting provider process information under their own policies. Cloudflare may process visitor IP addresses, request details, and security logs to serve and protect this website.

4. Storage, security, and retention

OAuth tokens are stored in the owner-controlled rclone configuration or runtime environment until removed or replaced. They must be protected using access restrictions and appropriate configuration encryption. They are never included in this website’s published files.

Transferred files remain in the connected cloud accounts until the owner deletes them or a configured sync operation changes them. Temporary transfer data and diagnostic logs may remain on the runtime machine until cleared. Logs can contain file names, paths, timestamps, and error details; they should be kept only as needed for troubleshooting and protected from unauthorized access.

5. Revoking access and deleting data

The owner can stop the sync process and any scheduled jobs, revoke access in Google account connections and Microsoft account application-permission settings, and remove the relevant rclone configuration and tokens. Revoking access prevents future authorized operations; it does not automatically remove files already transferred.

To remove retained data, delete the relevant destination files, temporary files, and local diagnostic logs. Cloud provider trash, version history, and backup retention follow the provider’s settings and policies.

6. Google API Limited Use

Personal Cloud Sync’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements, and the applicable Google Workspace API user data and developer policy.

Google user data is used only for the disclosed file synchronization functionality. It is not transferred for unrelated purposes. Human access is limited to the owner’s use and permitted circumstances under the applicable policies, such as authorized troubleshooting, security investigations, or legal obligations.

7. This website

This site has no account registration, sign-in form, advertising, analytics scripts, or application cookies. Visiting it does not authorize access to OneDrive or Google Drive. Hosting-level processing may occur as described above.

8. Questions and changes

This utility is operated for the owner’s own accounts and has no public onboarding. The owner manages privacy requests directly through the connected accounts and the machine running rclone. If access is opened to others, operator contact details and an appropriate support channel will be published before onboarding.

Updates to this policy will be posted here with a revised effective date. Any change in how authorized data is used must be reflected in the disclosures and, where required, renewed consent.