Gmail Data Use

Permission requested

33io requests gmail.readonly plus basic Google account email and profile scopes. Read-only Gmail access is required because role discovery and inbox intelligence need message headers and content across user-selected mailbox windows. Metadata-only access cannot provide the message context needed to identify responsibilities, workflows, reply load, or tone.

User-facing features

• Inbox intelligence: summarize actionable and aging work threads.
• Role discovery: infer a private role profile with message-level evidence references.
• Agent recommendations: propose bounded, draft-only assistants based on claims the user reviews.
• Drafting support: prepare suggestions and drafts without sending or changing the mailbox.

What 33io never does

• 33io never sends, deletes, archives, labels, moves, or marks Gmail messages read.
• 33io does not sell Gmail data or use it for advertising, surveillance, or credit decisions.
• 33io does not use Gmail data to train generalized AI models.
• 33io does not expose raw mailbox content to production teammates or other 33io customers.

Storage and processing

Message bodies are processed transiently for the feature the user requested and are not persisted in role profiles. Stored records are limited to connection metadata, encrypted credentials, aggregate signals, evidence identifiers with limited header metadata, user-reviewed claims, agent decisions, and security audit records. Short excerpts may be sent to a contracted AI processing provider solely to produce the visible requested feature.

Disconnect and delete

A user can disconnect Gmail from the 33io connection surface. 33io then asks Google to revoke the token, deletes its stored OAuth credentials, stops future access, and can delete the derived role profile for that scope. A user can also revoke access from the Google Account permissions page or request full deletion at any time.

Contact