Privacy & data
This page explains how data moves when you use kōdlo from Claude. The kōdlo Privacy Policy is the binding document. It also lists every sub-processor.
What the connector can access
Section titled “What the connector can access”The connector acts as you, with your role’s permissions, inside your workspace. It can read and change:
- campaigns, contacts, timeline events, tickets and comments in your workspace;
- Knowledge Hub documents you can see (and add documents to your own projects);
- your own kōdlo conversations and tone-of-voice prompts, never a colleague’s;
- your workspace’s company profile (read-only).
It never reads another workspace. A read-only key cannot change anything or start paid runs. Contacts marked Do Not Contact cannot be changed through the connector.
What goes to Claude
Section titled “What goes to Claude”When Claude calls a tool, the tool’s result, for example a contact record or search results, becomes part of your Claude conversation. From that point Anthropic processes it under the terms of your Claude account. kōdlo does not control what Claude stores. Ask only for what you need, and use a read-only key if you only want lookups.
Text written by third parties or imported from the web (contact bios, posts, documents, report text) is returned inside a field called untrusted. That tells Claude to treat it as data, not as instructions, which reduces the risk of prompt injection from web content. It is a safeguard, not a guarantee.
What kōdlo records
Section titled “What kōdlo records”- Keys: only a hash of your key is stored. The full key is shown once. Logs contain the key’s id and a short display prefix, never the key.
- Audit trail: every change made through the connector is recorded with the key used, the tool and the names of the changed fields, not their values.
- Key usage: each key stores when it was last used and from which IP address.
- Operations: background runs keep their input and results for 30 days after they finish, then are deleted. Retry records for
client_request_idare kept for 7 days. - Every background run also appears as a conversation in your kōdlo archive.
Things to know before you run research
Section titled “Things to know before you run research”- Deep research reports are filed in the workspace’s shared Deep Research Reports folder, which every member of your workspace can read.
- Lookup and enrichment write to the contact’s timeline. Enrichment also fills empty profile fields.
Third parties used by the connector’s tools
Section titled “Third parties used by the connector’s tools”| Purpose | Used by |
|---|---|
| Web search and entity discovery | Lead discovery, deep research, contact lookup |
| Partner data for enrichment | Contact enrichment |
| Large language models | Lead discovery, deep research |
| Embeddings | Knowledge Hub and conversation search |
Fetching public web pages (as KodloCRMBot/1.0) |
URL imports, lookups |
| Hosting (EU) and file storage | All tools |
The named providers, their locations and the transfer safeguards are listed in the Privacy Policy.
Your controls
Section titled “Your controls”- Revoke a key at any time in Settings → AI apps (MCP). It stops working on the next request.
- The workspace owner can revoke any member’s key, or turn external AI apps off for everyone.
- To exercise your data-protection rights, see the Privacy Policy or email info@kodlo.ai.