Security

Least access, project separation, and human approval

The security model applies across the portal, API, and operational MCP.

Identity and authorization

Human session for the portal and OAuth 2.0 with PKCE consent for compatible connectors.
One-hour OAuth access tokens and rotating revocable refresh tokens.
Compatibility with existing dpa_ tokens.
OWNER or ADMIN required to grant access, with read by default and write separately confirmed.

Queries scoped to the authorized project.
Provider credentials encrypted at rest.
Private account, project, lead, campaign, credential, and audit data is not authorized for model training.
The commercial MCP never contains customer data.

Email [email protected]. Do not include unnecessary secrets or personal data. We will acknowledge receipt and coordinate responsible validation.

Machine-readable evidence