Verified safeguards
- Bounded, staged reads
- Two-step Gmail writes and provider removal
- Subject-bound, single-use action and connection claims
- Origin and authorization checks on HTTP transport
- Tokens excluded from MCP results and cost telemetry
/data
Verified data handling
A concrete map of data, storage and control.
This matrix reflects the inspected SoMail Gmail implementation. Unknown retention and deletion behavior is treated as a launch blocker, not softened into marketing copy.
| Data | Verified handling | Current deletion behavior | Status |
|---|---|---|---|
| OAuth grants | AES-256-GCM encrypted vault; includes account identity, scopes and tokens. | Hosted removal revokes Google before vault deletion; the separate operator CLI keeps Google-side revocation as an operator step. | VERIFIED IN CODE |
| Connection transactions | Encrypted ten-minute OAuth state plus a SQLite ledger containing an opaque ID, keyed subject hash and timestamps. | State expires after ten minutes; expired ledger rows are pruned when a new transaction is registered. No raw subject or PKCE verifier is stored in the ledger. | VERIFIED IN CODE |
| Message metadata | SQLite can store IDs, subject, participants, dates, snippets, labels, attachment names and counts, and body hash. | No account-specific purge or retention period was found. | UNKNOWN |
| Full bodies and attachments | Fetched only by explicit read and fetch tools and returned to the connected MCP client; not written to the metadata index. | No separate local body store was found. Downstream client retention is not defined here. | UNKNOWN |
| Action ledger | Stores action ID, authenticated subject and claim timestamp to prevent replay. | No automatic purge was found. | UNKNOWN |
| Cost telemetry | Off by default. When enabled, stores tool and method names, sizes, timing and status — not arguments, content, headers or tokens. | File or platform-log retention has not been defined. | UNKNOWN |
Launch blockers
- Define and implement retention periods
- Purge indexed account data on deletion
- Document backup and log deletion
- Prove public onboarding and independent-user isolation
- Resolve publisher, controller and support identity
Hosted OAuth and mailbox callbacks have private pilot evidence. That does not establish public enrollment, independent-user isolation or approval by a platform.
UNKNOWN Unresolved before public release
Retention policyBackup purgePublic onboarding and isolationController identitySupport channel