Integration Data Use — founder-review draft

Provider passwords are not collected. Connections will use OAuth and minimum scopes, with tokens kept behind a server-only production credential vault.

Provider data is translated into workspace-scoped canonical records. Provider identifiers do not become global customer identity, and unrelated business data is not included in another workspace’s AI context.

Reading, drafting, sending, publishing and calendar access are separate capabilities. Granting one does not imply another.

Disconnection stops new provider access. Imported-data deletion is a separate, auditable request and may require provider-side action.