ControlOS

Privacy Policy

This policy describes how the private, owner-operated ControlOS pilot accesses, uses, stores and protects Google user data.

Effective date: 21 September 2026

Data ControlOS accesses

How the data is used

Google user data is used only to provide owner-requested planning, reconciliation and reminder functions. Calendar source events are not modified. Merchant Center, Google Analytics and Google Tag Manager access is read-only and restricted to exact owner-approved client evidence checks. Gmail bodies are processed transiently; the system retains only the minimum derived planning records and provenance required for reconciliation, deduplication and audit.

Storage and security

OAuth refresh credentials and protected derived fields are encrypted at rest with independent production keys. Access is restricted to the owner-controlled Main environment. ControlOS does not sell Google user data, use it for advertising, or share it with data brokers. Google Calendar or Gmail content is not sent to paid OpenAI API services.

Retention and deletion

Derived records are retained only while needed for the private planning service and its audit trail. Source updates and deletions are reconciled. The owner may disconnect an account, revoke Google access, or delete associated connector data. Encrypted backups expire under the system's backup-retention policy.

Owner control

The owner can revoke ControlOS access at any time from Google Account security settings. Revocation stops future synchronization; ControlOS also supports server-side connector disablement and credential deletion.

Current safety boundaries

Employer-gated connectors, external email sending, Slack sending, external posting, campaign publishing and paid OpenAI API access are disabled. Gmail access, where activated, remains read-only.

Return to the ControlOS public information page.