M3 Drive Publisher

Privacy policy

This policy describes the personal Google Drive publishing workflow and this public information site.

Google Drive data

The operator authorizes rclone with Google OAuth. The integration reads folder and file metadata to locate the destination and downloads selected files to verify their bytes. It uploads the research files selected by the operator and a completion record to the selected private Drive folder.

The OAuth grant permits Drive access. The publishing workflow uses that access for the approved destination and readback. It does not change Drive sharing permissions, sell Google user data, use it for advertising, or use it to train AI models.

Storage and retention

Google OAuth credentials are stored in the operator’s private rclone configuration on GTR. Research files, local readback data and publication receipts are handled on that system. Published copies remain in the operator’s Google Drive until the operator removes them. The operator manages retention of local files and receipts.

This information site

These pages are public and do not accept logins, uploads, or OAuth tokens. They include no analytics scripts. Cloudflare delivers the pages and may process routine request metadata to operate and protect its service.

Access and contact

Manage or revoke access from Google Account connections. Revocation stops future access and does not delete copies already in Drive. Use the support contact shown on the Google consent screen for privacy questions or deletion requests.

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