AntOS Drive Writer privacy policy
Last updated: 18 September 2026
Scope and purpose
AntOS Drive Writer is a private service operated by Marmalade Parade Ltd. It uses Google Drive data only to read, verify and, following separate human approval, update Markdown records selected by the operator.
Google data accessed
The service may access the identity, name, MIME type, modification time, revision information and complete content of files explicitly selected through Google Picker. It requests only the Google Drive drive.file scope.
How data is used and stored
Selected file content is used for consistency checks, approved replacement, read-back verification, reconciliation and recovery. Local audit records can retain approved before-and-after content, hashes, revisions and verification receipts.
The offline Google credential is encrypted for the Windows account running the service. Authentication material is not included in source control, application reports, audit databases or logs.
Disclosure and AI use
The Google Drive integration sends Drive data only to Google Drive APIs for the requested operation. It does not sell Google user data, use it for advertising, disclose it to data brokers, or use it to develop, improve or train generalized or non-personalized artificial-intelligence or machine-learning models. Google Drive file content handled by this integration is not sent to OpenAI by the provider or writer.
Retention and deletion
Local audit and recovery records are retained for operational integrity and disaster recovery until the operator deliberately archives or removes the local service data. Revoking Google access prevents future API access but does not automatically erase existing local audit records. The operator can separately remove the DPAPI credential and local service data.
Security and control
Drive access is constrained by Google Picker selection and a local destination allowlist. Production writes additionally require human approval and provider-backed verification. Authentication errors and unexpected provider state stop the affected operation.
Revoking access
The operator can revoke the application's Google Account access at any time through the Google Account third-party connections page. The local DPAPI credential can then be removed to prevent further token use.