For the Codext CRM connector for Claude (the MCP server built into Codext CRM).
The short version. The connector is a door into a CRM workspace you already have, opened by you, for you. It stores the minimum an OAuth connection needs — who approved what, for which workspace — and an audit line for each call. Your CRM data travels between Claude and the CRM instance you connected, and nowhere else (one search tool sends its search phrase to the instance's configured AI provider — section 5). Codext GmbH runs no analytics, no advertising and no tracking in it, and sells or shares nothing. If you run your own instance, Codext GmbH receives nothing at all.
This connector is published by Codext GmbH, Frankenstraße 10, 74549 Wolpertshausen, Germany ("we", "us"), the developer of Codext CRM. You can reach us at crm@codext.de.
Codext CRM is open-source software (MIT licence). The source of the CRM, including every line of the connector, is public at github.com/codextde/codext-crm, so every claim on this page can be checked rather than taken on trust.
The connector is an MCP server that is part of the CRM itself — the same software, the same database, the same address. When you connect it in Claude, Claude sends you to your CRM to sign in and approve one workspace; from then on, when you ask Claude something the CRM can answer, Claude calls the CRM over HTTPS, as you, with the permissions you granted, and shows you the result. Nothing runs in between.
crm.codext.de, the instance Codext GmbH hosts.
Then we operate the server and act as processor for the organisation whose workspace you
approved, under the hosting agreement with that organisation. This policy describes what that
instance stores and how it is run. Connecting the connector on its own never creates a hosting
relationship — workspaces on crm.codext.de exist by invitation.Stored on the CRM instance you connected to, and only there:
| What | Why | How long |
|---|---|---|
| Client registration — the connecting application's name, redirect address and requested scope, as Claude sends them when it registers (RFC 7591). | So the CRM can tell which application is asking, and send the sign-in result back only to an address that application registered. | Until the CRM administrator removes it. |
| Grant — which user approved which client, for which workspace, with which scope (read, write or both), and when. | This is the permission itself. Every request is checked against it. | Until you disconnect in Claude or revoke in the CRM, whichever comes first. |
| Tokens — the access and refresh tokens issued to Claude, stored as one-way hashes; the plain token is never written down. | To authenticate each request without a password. | Access tokens expire after 8 hours. Refresh tokens rotate on every use and die with the grant. |
| Audit log — one line per tool call: which tool, the shape of its arguments — field names and types, never the text you typed — which user, which connector, when. Writes are recorded against the record they changed, like any other change in the CRM. | So a workspace administrator can see what every connected assistant did, and you can see what was done in your name. | As long as the workspace exists, alongside the rest of its audit history. |
| Request logs — the calling address, timestamp, endpoint and outcome of each HTTP request, and error details when something fails. | To operate the service, rate-limit abuse and diagnose failures. | Rotated on a rolling basis; not used to build profiles or for anything beyond operating the service. |
The connector does not collect your conversations with Claude. It receives only the arguments of each tool call — the search term, the deal id, the note you asked it to log — and those are exactly what the tool needs to do its job. It does not read Claude's memory, chat history or files, and it has no way to.
When Claude calls a tool, the CRM returns the records the tool describes — a contact, a list of deals, an invoice total — to Claude, over HTTPS, and to no one else. What Anthropic then does with content that passes through Claude is governed by Anthropic's privacy policy and the terms of your Claude plan, not by this one. The CRM itself sends nothing to Anthropic that you did not ask Claude to fetch.
The connector opens no other network connections. It calls no analytics, advertising, tracking
or error-reporting service, and it has no AI model provider of its own. One exception is worth
naming: search_knowledge, the tool that searches a workspace's sales knowledge
base, turns the search phrase into an embedding using the AI provider the instance's
administrator configured — the same provider the CRM's own assistant uses — and falls back to
a plain keyword search when none is configured. Only the search phrase is sent, never the
results; which provider sees it is a decision made on the instance, by its administrator, and
governed by that provider's own terms.
crm.codext.de only: the instance runs on
servers rented from Hetzner Online GmbH in the European Union, which hosts the machine and
sees network traffic to it in encrypted form. Hetzner is engaged as a sub-processor under a
data processing agreement.If you run your own instance, there is no third party on our side at all.
Retention per item is in the table in section 4. Disconnecting the connector — in Claude, or under Settings → MCP server in the CRM — revokes the grant and every token under it at once. The audit trail of what was done while it was connected stays with the workspace, as any audit trail must. Deleting a workspace deletes its grants, tokens and audit log with it.
Connections use OAuth 2.1 with PKCE (S256 only), over HTTPS only. Tokens are stored hashed, bound to the workspace and the endpoint they were issued for, and rate-limited per connection. Every tool resolves the records it touches inside the approved workspace before reading or writing anything, so an id from another workspace is refused rather than served. How to report a vulnerability is in SECURITY.md.
Codext CRM is business software, not directed at children, and not intended for anyone under 16. We do not knowingly collect anything from children.
Under the GDPR you have rights of access, rectification, erasure, restriction, portability and objection over your personal data, and the right to lodge a complaint with a supervisory authority. Because your CRM data sits on the instance you connected to, those requests are addressed to whoever operates it — in most cases your own organisation. If Codext GmbH operates your instance, write to crm@codext.de and we will handle it as processor for the controller, or pass it to the controller where that is what the law requires.
If this policy changes we will update the version and date at the top of this page, and the history is visible in the repository. Material changes to what the connector does will also appear in the release notes for the version that makes them.
Codext GmbH
Frankenstraße 10, 74549 Wolpertshausen, Germany
Managing director: Daniel Ehrhardt · Amtsgericht Stuttgart, HRB 772091 · VAT ID DE327501500
Email: crm@codext.de
Source and issue tracker:
github.com/codextde/codext-crm