Privacy policy
Last updated: 19 November 2026
DriveSync is a desktop app that runs on your own computer. It keeps a folder on that computer and your Google Drive in sync, using rclone. The developer runs no server, collects nothing and receives none of your data. This page explains what DriveSync does with the access you give it to your Google account.
What DriveSync accesses
When you sign in, Google asks you to let DriveSync see, edit, create and delete all of
your Google Drive files (the https://www.googleapis.com/auth/drive scope).
DriveSync needs the whole Drive because it mirrors it into a folder on your computer in
both directions. It reads the names, sizes, dates and contents of your Drive files. It
asks for nothing else from your Google account.
How DriveSync uses it
Only to keep the two copies the same, and to show you how that is going. On each run it lists the files on both sides, copies new and changed files each way, and deletes on one side the files you deleted on the other (files deleted from the folder go to the Drive trash). File names appear in the DriveSync window, in desktop notifications and in a log on your computer, so you can see what each run did. It does nothing else with your data: no advertising, no profiling, and no training of AI or machine learning models.
Where your data is kept
-
Your files: in the folder you chose (
~/Driveby default) and in your Google Drive. They travel only between your computer and Google's servers, over HTTPS. When you let one run past the max-delete guard, the files that run deletes or overwrites on your computer are moved to~/.local/state/drive-sync-app/accounts/<account>/allowed-backup/instead, and stay there until you delete them. -
The sign-in token Google gives back: in rclone's configuration file on your computer
(by default
~/.config/rclone/rclone.conf). -
The sync log, with file names:
~/.local/state/drive-sync-app/accounts/<account>/drive-sync.log, or~/.local/state/drive-sync.logfor a drive-sync DriveSync took over or an earlier version set up. DriveSync's settings:~/.config/drive-sync/, with each account's config inaccounts/<account>/and therunOnlyWhencheck every account shares inmachine.json. Its state:~/.local/state/drive-sync-app/, with each account's inaccounts/<account>/.
All of this stays on your computer until you delete it. The developer has no copy of any of it, so there is nothing to keep or delete on the developer's side.
Sharing
DriveSync does not send your data, your file names or anything about your use of the app to the developer or to anyone else. It has no analytics, telemetry or crash reporting, and it does not sell or share data. The only party it talks to is Google, to read and write your own Drive, and Google's own privacy policy covers that.
Google API Services User Data Policy
DriveSync's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Removing the access
- Revoke DriveSync's access at any time on your Google account's third-party connections page. Syncing stops at the next run.
-
Remove the token from your computer with
rclone config deletefollowed by the name of the Drive remote. -
Uninstall the app with
sudo pacman -R drive-sync, and delete the folders listed above if you want them gone too. Your files stay in the folder and in your Drive.
Changes and contact
A change to this policy is published on this page with a new date, and its history is in the source repository. Questions go to the project's issue tracker.