Privacy Policy
mbgapp is a personal tool with a single user: its owner. It does not collect, store, share or sell data from anyone. This page explains, in plain language, what the tool does with the owner’s own data.
What data the tool accesses
mbgapp accesses files in the Google Drive folders that the owner chooses, using the Google Drive API. It only reads the folders the owner points it at. It does not access any other Google account data.
Why the data is accessed
The only purpose is to copy those files from the owner’s Google Drive to the owner’s own computer. The data is not analysed, profiled, used for advertising, or used to train any model.
Where credentials are stored
The OAuth credentials that Google issues to the tool are stored locally on the owner’s machine, in the rclone configuration file. They are never sent anywhere other than to Google’s own API endpoints to authorise requests.
What is shared with third parties
Nothing. No data, credentials or usage information is transferred to any third party. There are no analytics, no telemetry and no external servers involved beyond Google Drive itself.
Data retention
Copied files remain under the owner’s control on the owner’s computer for as long as the owner keeps them. The copies in Google Drive may be deleted by the owner after download. The tool keeps no other record of the files it has transferred.
How to revoke access
Access can be revoked at any time from the Google Account permissions page at myaccount.google.com/permissions. Deleting the rclone configuration file on the owner’s machine also removes the stored credentials.
Google API Services User Data Policy
mbgapp’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Changes and contact
Any change to this policy will be published on this page with an updated date. Questions can be raised through the issue tracker of the GitHub repository.