Your data. Plainly explained.

You can connect Claude, or another app that speaks the Model Context Protocol (MCP), to your workspace through our connector at mcp.klientele.io. You sign in with your Klientele account and choose what the app may do: read only, read and write, or full access. The app then acts as you, and never beyond what your role and your data scope allow. A workspace admin can switch API access off for the whole workspace under Configuration → Advanced.

What passes through the connector. Each request from the app (the tool it calls and the values it sends) is passed to the Klientele API, and the answer is passed back. The connector keeps only what it needs to hold the connection open: which workspace and member it acts for, and a hash of the sign-in token. That lives in memory and is dropped after 30 minutes without use. It does not store the requests or the answers.

What reaches the AI provider. The answers contain the workspace data the app asked for, such as a client's open work or an invoice. They go to the provider of the app you connected (for Claude, Anthropic) and are handled under that provider's terms. The connector never asks the app for your chat history, its memory or your files.

What we store about AI sessions. Changes an app makes are saved like changes made in the app, in the item's history and, on the Agency plan, in the audit log. For each AI session we also record:

• which app it was and which member it acted as;
• when it started and when it was last active;
• for each item it changed: how many actions it took, when, and the last one (for example a status change or a comment);
• the token counts the app reports, and the model it names, if it reports them.

An app may send a session label, an opaque id it picks so that parallel agents are counted apart. It carries no conversation content. Token counts are only billed when the workspace owner turns AI usage billing on. Session records are kept as long as the workspace's other data, and are deleted with it.

Money. The connector can record a payment you received elsewhere, record prepaid credit, and issue or apply a credit note. It never moves money: no tool charges a card, triggers a payout or calls a payment gateway. Claude asks you before each of these actions.

How to disconnect. In Klientele, open Settings → Security → Connected apps and choose Disconnect. The app loses access at once. A workspace admin can disconnect any member's app under Configuration → Integrations → Connected apps. Changing your password disconnects all of your apps. Removing the connector in Claude stops Claude from using it; disconnecting it in Klientele also revokes its access.

Some workspaces use our healthcare or veterinary templates, so their records can hold health information about patients or animals: care tasks, care episodes, treatment plans, notes and attachments. We treat it as workspace data, owned by the practice and processed by us only to run the workspace.

• How it is stored. In the same database as the rest of the workspace, on infrastructure in India, encrypted in transit. It is never used to train AI models and never shared with advertisers.
• Who can see it. Members of that workspace, as their role allows. The healthcare template limits clinicians to the patients they are given, and every role can be limited to chosen clients. Portal users see only their own records.
• Our staff. Klientele staff open a workspace only to help with a support request. Each visit needs a stated reason, is limited to 15 minutes, is listed for the workspace under Configuration → Staff access and is notified to the owner. A workspace can require its approval first.
• Through an AI app. A connected app sees only what the member who connected it can see. What it reads goes to that app's provider, as described above. A practice that does not want this can switch API access off.

Klientele holds no HIPAA or other health-data certification today. See our security page for what we do and don't claim.