Effective date: 17 September 2026
This Privacy Policy describes how the personal application named MyDrive (“the application”) handles Google user data.
Who this applies to
The application is a private, single-user tool. It is used solely by its author on the author’s own computers, with the author’s own Google Account. It is not distributed, not published to any app store, and has no other users. There is no hosted service, no back end server, and no account system: the software runs locally on the author’s own machines and communicates directly with Google’s APIs.
Because there are no third party users, no third party Google user data is ever processed by this application.
What Google user data the application accesses
The application requests a single OAuth scope:
https://www.googleapis.com/auth/drive
This scope grants read and write access to files in the author’s own Google Drive. The application uses it to present the author’s Google Drive as a folder on the author’s local filesystem, and to keep a small number of folders mirrored between the author’s own computers.
The application does not request access to Gmail, Google Calendar, Google Contacts, Google Photos, YouTube, or any other Google service. It does not read file contents beyond what is required to copy files between the author’s own machines and the author’s own Google Drive.
How the data is used
Google user data is used for one purpose only: to synchronize the author’s own files across the author’s own computers. Files stored in the author’s Google Drive are read and written so that selected folders stay identical on each of the author’s machines.
The data is not used for advertising, profiling, analytics, machine learning, or any purpose other than the file synchronization described above.
How the data is stored
- Credentials. OAuth credentials, including a refresh token, are stored locally on the author’s own machines in the file
~/.gdfuse/default/state, readable only by the author’s user account. - File contents. Files are stored on the author’s own disks and in the author’s own Google Drive. The application keeps no separate copy anywhere else.
- No servers. The application transmits data only between the author’s machines and Google’s APIs. No copy is sent to any third party system.
Sharing and disclosure
Google user data accessed by this application is never sold, rented, traded, or otherwise transferred to any third party. It is not shared with advertisers, data brokers, analytics providers, or any other organization. No person other than the author can access it, and no automated system processes it for any purpose beyond the synchronization described above.
Limited Use disclosure
The application’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Retention and deletion
The author can revoke the application’s access to the Google Account at any time at myaccount.google.com/permissions. Revoking access immediately invalidates the stored refresh token, after which the application can no longer read or write Google Drive data.
Deleting a file locally removes the local copy; deleting it in Google Drive removes the Drive copy. Deleting the credential file removes the local credentials. Because there is no server and no backup held by the application, revocation and deletion are complete and immediate.
Children
The application is not directed at children and is not used by anyone other than its author.
Changes to this policy
If this policy changes, the revised version will be published at this URL with an updated effective date.
Contact
Questions about this policy can be sent to bigkpwns@gmail.com.