Privacy Policy.

With your consent, the public landing site uses Google Analytics 4: pages without query parameters, language, clicks, section views and active viewing time. Google also processes IP addresses and technical browser/device information under its policies. This analytics is separate from the console and connected-service data.

Our events exclude prompts, form contents, messages, account data and secrets. Advertising signals and personalization are disabled. The Google tag is not loaded before consent. Your choice is stored locally; change or withdraw it through Website analytics in the footer. Withdrawal stops further measurement transmission. Analytics cookies last up to one year. Previously collected data is processed by Google according to property settings. Google privacy: https://policies.google.com/privacy. Analytics data practices: https://support.google.com/analytics/answer/6004245.

Data serves two distinct purposes: account data enables sign-in and connections; business-service data passes through Context4 during your requests. CRM records, documents, messages and API responses are not used as a Context4 database.

Account data includes your identifier, email, workspace, permissions and connection status. Support processes your sender address and the information you include in an email.

Context4 receives the parameters of your selected action, calls the connected service API and returns its response to your authorized client. Request and response content is processed in memory during execution and response transfer, then released.

Context4 does not persist request or response content in databases, files, queues, caches, logs or backups. It does not create a CRM archive, conversation history, document copies or result store. Retrieving data again requires a new request to the source service.

Context4 does not automatically receive your entire AI conversation: it receives the parameters of the invoked tool. Conversation text you include in those parameters is processed as request content. Do not include unnecessary data.

Account records, connection settings and tokens required for authorization are stored separately from request content. They enable sign-in and access to your selected accounts on your behalf. Proxying without content storage does not mean there are no account records or authorization secrets.

OAuth tokens and keys are used only for permitted operations on the relevant connection. Secrets are restricted to server-side access and are not included in tool responses, public documentation or logs. With OAuth, the external service password is entered on its provider page.

Disconnecting removes the relevant secrets from active storage and stops their use. Revoke the external provider grant as well. Your AI client authorization to Context4 and Context4 authorization to a CRM are separate grants.

Account data is used to provide the service, verify authority, protect access and answer requests. Business-service content is not used for advertising, model training, customer profiling or Context4 analytics products.

The applicable supplier identified above is responsible for Context4 user data. Context4 technically processes organization data on its instructions and within granted permissions. The organization determines purposes, legal bases and permitted recipients. Arrange a separate processing agreement before connecting if one is required.

Processing relies on the basis applicable to its purpose: providing the requested service, meeting mandatory requirements, and consent where necessary. Connecting an account does not replace employer authorization or a lawful basis for processing customer data.

Your selected business service receives the operation parameters; the AI client or application that made the request receives the result. Vercel delivers the website and console and forwards API/MCP traffic, processing IP addresses, technical metadata and the content of transmitted operations. Authentication infrastructure, the server and secret storage receive information necessary for their functions. Data is not sold.

Support email is processed by Yandex email. External AI clients and source services handle received data under their own terms. Context4 no-content-storage rules do not extend to their systems. Contact support before connecting for details of infrastructure processors and processing locations.

Using ChatGPT, Claude or other foreign clients may transfer data outside the country of the user or source-system owner. Establish permitted recipients and necessary legal bases before connecting corporate data. OAuth consent does not replace international transfer requirements. Disclosures to authorities are limited to binding lawful requirements.

Request and response content is not kept after execution and response transfer complete. No backups of that content are created. Logs do not contain payloads, documents, messages, passwords or tokens.

Account records and settings are retained while you use the service. Sessions and authorization remain valid until expiry or revocation. Connection secrets are deleted when disconnected. Request account and associated service-data deletion through support, with verification of your authority.

Support correspondence is kept to handle the request and deleted after handling, except for information legally required or necessary for a specific dispute. Such information is limited to what is necessary and is not used for other purposes.

Account deletion removes service data from active systems. Residual copies are removed through backup rotation; before then they are excluded from ordinary use and deleted again after restoration. Support explains the procedure and timeline for a specific deletion subject to mandatory requirements. Data already received by an AI client or source service is deleted under those providers' rules.

The public site stores your selected theme in browser local storage. After sign-in, technical cookies and sessions enable authentication. You can manage them in your browser settings. They are not copies of business-service data.

Access is restricted by account, workspace and granted permissions. Do not send passwords or keys in AI chats or support email. If access is compromised, revoke grants and contact support.

Subject to applicable requirements, you may request processing information, correction, deletion, restriction and withdrawal of consent where processing relies on it. Email the supplier above. Identify the account, workspace and request; secrets and CRM exports are not needed.

The supplier verifies the requester's identity or authority over the organization. Revoking access and deleting data are separate actions. Mandatory applicable requirements determine response times. Your right to contact a competent supervisory authority or court is preserved.

The policy version appears on this page. Material processing changes are communicated before they apply; additional consent is requested where necessary.