cmFile — Privacy Policy

Last updated: 9 September 2026

cmFile is a personal archival tool operated by a single individual for their own use. It is not a service offered to the public, and it has no users other than its author.

What data it accesses

When authorized, cmFile reads file content and metadata from the Google Drive account of the person who authorized it, using read-only scopes (drive.readonly and drive.metadata.readonly). It requests no other Google data and cannot modify or delete anything.

What it does with that data

Files are encrypted on the operator's own computer and copied to storage accounts belonging to the same operator. Encryption keys are held only by the operator. The purpose is redundancy: the archive is kept so that the data survives the failure or shutdown of any single storage provider.

What it does not do

• It does not transmit data to the developer, to any analytics service, or to any third party beyond the operator's own storage accounts.
• It does not sell, share, or disclose data to anyone.
• It does not use Google user data to develop, improve, or train generalized artificial intelligence or machine learning models.
• It has no advertising and no tracking.

Retention and deletion

Archived copies are retained for as long as the operator chooses to keep them, and can be deleted by the operator at any time by removing the archive repositories and revoking the application's access at Google Account permissions.

Limited Use

cmFile's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Contact

Questions can be directed to the repository owner via GitHub.