Google data controls

Supported access

• Read-only Gmail search and bounded extraction.
• Files and folders deliberately selected with Google Picker.
• Read-only calendar or analytics access when explicitly enabled.
• Knowledge-source files shared with a dedicated reader identity.

Generic Google shell and Drive executables have been retired for managed access. Any future customer-supplied OAuth option will keep the same CodePress scope, content, consent, and output controls, while the customer remains responsible for verification of its own Google Cloud project.

AI processing

The relaunch design keeps raw Google content ephemeral and screens it inside CodePress's backend. The main agent receives only a compact extraction with source provenance; unsafe or instruction-like content is withheld. Any AI processor used at this boundary must be tools-disabled, approved for Google processing, and contractually restricted from training before access is enabled.

Disconnect, revoke, and delete

Today's containment gate fences managed Workspace calls and new grants. Relaunch requires disconnect to stop watches and runtime access and revoke the Google grant, and requires Google-data deletion to remove retained derived content from active chats, recordings, caches, indexes, and artifacts associated with that consent. Audit tombstones must be content-free.

Dedicated self-service consent, status, disconnect, and deletion controls are required before relaunch. Until then, account owners can email privacy@codepress.dev with a data or revocation request.

Human access and incidents

CodePress personnel do not access Google user data for routine support. Access requires case-specific consent or a documented security or legal exception. Suspected incidents can be reported to security@codepress.dev; CodePress will investigate and make required user, regulator, and Google notifications.