Privacy Policy

Personal Drive Mount · Last updated: 1 October 2026

1. Who this applies to

Personal Drive Mount ("the application") is a private, single-user tool. It is operated by one individual for the purpose of accessing that individual's own Google Drive account. There are no other users of the application, and it is not offered to the public.

2. What Google user data is accessed

When the owner authorises the application with their Google account, Google grants it an OAuth 2.0 access token for the following scope:

• https://www.googleapis.com/auth/drive — see, edit, create and delete all of the owner's Google Drive files.

With this scope the application can read file contents and metadata (such as file names, sizes, folder structure and modification times) belonging to the account that authorised it.

3. How the data is used

The data is used for one purpose only:

• To present the owner's own Google Drive as a local filesystem on the owner's own computer, so that the owner can read, write, and back up their own files with normal desktop tools.

The data is not used for advertising, profiling, analytics, credit assessment, or any other purpose. No automated decision-making is performed on it.

4. How the data is stored

• OAuth credentials (access and refresh tokens) are stored locally on the owner's own machine, in the application's configuration file, readable only by the owner's operating-system account.
• File contents that are opened or uploaded may be cached temporarily in a local cache directory on the owner's machine. This cache is limited in size and age and is deleted automatically; the owner can also delete it at any time.
• No copy of Google user data is stored on any server operated by this application, because the application operates no servers.

5. How the data is shared

Google user data is not shared, transferred, sold or disclosed to anyone. Specifically:

• No data is transferred to third parties, advertising platforms, data brokers or resellers.
• No data is used to serve advertisements, including retargeting or personalised advertising.
• No data is used to determine creditworthiness or for lending purposes.
• No human reads the data, except the owner reading their own files.
• The only network destination the data is sent to is Google's own API (googleapis.com), which is the service the data belongs to.

6. Data retention and deletion

• The owner can revoke the application's access at any time at myaccount.google.com/permissions, which immediately invalidates the stored tokens.
• Deleting the application's configuration file removes the stored credentials from the machine.
• Deleting the local cache directory removes all locally cached file contents.
• Because the application keeps no server-side copy of any data, revoking access and clearing the local files leaves nothing behind.

7. Security

Credentials are kept on the owner's machine with filesystem permissions restricted to the owner's user account. The application is not exposed to the internet, runs no listening service, and is not accessible to anyone but its owner.

8. Children

The application is not directed at children and is not used by anyone other than its owner.

9. Changes to this policy

If this policy changes, the revised version will be published on this page with an updated date.

---