How data is handled.

Request flow

Your AI → Context4 → selected business service
Your AI ← Context4 ← service response

Context4 executes a permitted operation as a proxy. Request and response content is processed in memory during execution and result transfer. No persistent content store, chat history, CRM archive or response backups are created. Payloads and secrets are excluded from logs, queues and caches.

Connection data

Account records, workspace permissions, connection settings and required authorization tokens exist separately from operation content. They enable sign-in and access on your behalf. They do not authorize advertising or model training using your data.

What your AI receives

The AI client you select and authorize receives tool results. Its own retention and deletion rules continue to apply. Context4 cannot delete data from an existing conversation in another application. No storage in the proxy does not mean no processing by every participant.

Corporate systems

Obtain authority from the system owner and a lawful basis for disclosure to your selected AI before connecting. Sign-in capability and OAuth consent do not replace these requirements. Check applicable international transfer requirements where data crosses borders. Arrange a processing agreement before disclosure if necessary.

Disconnect and delete

Disconnecting stops use of the relevant connection secrets. Revoke the AI client MCP grant, Context4 API key and CRM grant separately. Contact support to delete your account and service data. Source-service and AI-client data rules apply separately.

The full contract is in the Privacy Policy and Terms of Use. All revocation steps.