Data sent to Anthropic
Liberty Next uses Anthropic's models in two ways, and the path of the data is not the same:
- the AI assistant — the server calls Anthropic's API with the API key of the installation;
- Claude connected through MCP — Liberty calls nobody: it answers the tool calls of the user's Claude client, and that client talks to Anthropic under the user's own Claude account.
Nothing is sent while nobody asks a question: no background send, no telemetry, no other AI provider. An installation can also name its sensitive data and keep it from the assistant.
At a glance
The AI assistant
Each question is sent to Anthropic's API with the Anthropic API key of Liberty Next → Administer → App → AI Assistant. A request holds:
| Sent | Content |
|---|---|
| Instructions | The built-in instructions, or the installation's System prompt in their place, and today's date. |
| Tool list | The name and the description of each tool offered to this user. |
| Page context | What the user is looking at: the application, the screen and its read query, the active filters, the number of rows loaded and their columns, the row last clicked. 4,000 characters at most; the × of its chip stops sending it. |
| Notes | The user's notes for the application, 2,000 characters at most. |
| Conversation | The questions and the answers of the conversation in progress — the last 40 messages. |
| Tool results | What each tool read to answer: the rows of a read query (200 by default), Data Explorer figures, the description of the installation (ids and labels — no data, no SQL), a playbook, the form of a screen, the record before and after a write. With the tools an installation turns on: the jobs, the server log lines and the integrity checks (operations tools, superusers only), the answer of an API endpoint (API tool), what an application's own tool returns. A result is cut at 60,000 characters. |
| Attached files | An image or a PDF as it is; a spreadsheet (its first sheet), a CSV or a text file as text, cut at 60,000 characters. A file stays with its conversation while the page is open, and is sent again with each question of it. A file chosen on the card of a job is not one of them: it goes to the job's own upload, never to the model. |
When domains are listed under Allowed domains, Anthropic reads those web pages itself; Liberty sends nothing more.
Within one question, each tool round sends the earlier rounds again; Anthropic reads the repeated part from its prompt cache for a few minutes, at a lower price. It is not a storage kept by Liberty.
Claude through MCP
| Step | Who talks to whom |
|---|---|
| The user asks Claude a question. | The Claude client ↔ Anthropic, under the user's Claude account. |
| Claude calls a Liberty tool. | The client → the server, with the user's access. |
| Liberty answers. | The server → the client: the result of that tool, 60,000 characters at most. |
| Claude writes its answer. | The client → Anthropic: the conversation, with the results it received. |
Liberty makes no call to Anthropic here, and the API key of the installation is not used. What a tool returned leaves the server towards the user's Claude client, and from there to Anthropic on the terms of the user's Claude plan. There is no page context and there are no notes over MCP. A file the Claude Desktop extension sends for a job goes from the user's computer to the server, not to Anthropic.
| Client | The server is called from |
|---|---|
| A custom connector in Claude Desktop or claude.ai | Anthropic's servers: the server must be reachable from the internet. |
| The Claude Desktop extension, Claude Code | The user's computer: an internal address or a VPN is enough. |
Sensitive data
An installation decides what is sensitive, and Liberty keeps it from the assistant — in the chat and through MCP alike. Nothing is flagged in what the applications ship: the flags are the installation's to set and to maintain.
| Step | Where | Effect |
|---|---|---|
| Flag an item | Liberty Next → Build → Dictionary → an entry → Rule → Sensitive | Covers every column carrying the item, on every screen, query and Data Explorer model. A column is matched by its dictionary item, by its name, or by its name without the connector's prefix (ABALPH → ALPH) — as the data scope finds its columns. |
| Flag a column | Liberty Next → Build → Screens → a column → General → Sensitive | Three choices: (default) follows the column's item, yes covers a column that carries no item, no exempts a column whose item is flagged. |
| Turn the hiding on | Liberty Next → Administer → App → AI Assistant → Hide sensitive data from the assistant | Off by default. Applied at the next call, without a restart. |
With the hiding on, the flagged columns are left out of:
| Place | What happens |
|---|---|
| Rows a read query returns | The flagged columns are removed from the rows. The assistant is told which columns are hidden, so it can say so and point the user to the screen. |
| Write and action cards | The values of the record are shown as (hidden: sensitive): the record before a change, the record of a delete, the screen's confirmation of an action, and the messages of the actions the screen runs after a save. The value the user asked to write is theirs, and is shown. |
| Page context | The flagged columns leave the column list and the clicked row, and a filter typed on one of them is not sent. |
| Data Explorer | A flagged field cannot be a row heading nor be read by a measure other than a count — no sum, average, minimum or maximum. It can be counted, and filtered on a whole value the user gives (equals) only: a range, a contains or a period on it is refused, as it would let the values be found out count by count. |
| Filters of a read query | The same rule: a flagged column is filtered on a whole value, not on a range. |
The screens themselves do not change: the users who may open them see the values as before.
What the hiding does not cover:
- what a user types in a question, or attaches;
- a free-text column that is not flagged;
- what an API endpoint (API tool), an application's own tool or the operations tools return — Liberty does not know their columns;
- the key of a record on a write card.
What is never sent
| Never sent | How |
|---|---|
| Pool passwords, API keys, encrypted secrets | The tools give descriptions only — never credentials. A password field of a form is shown as ••••••. |
| The SQL text of a query | The assistant sees the name, the label and the description of a query. |
| Rows the user may not read | Each tool checks the permission the screens check, and the user's data scope filters the rows. |
| Connectors left out of Allowed connectors | The assistant is told they are not available. |
| What a switched-off tool would read | A tool that is off is not offered at all. |
What stays on the server
| Kept | Content, how long |
|---|---|
| Conversations | What the user saw — questions, answers, the names of the attached files — for the 30 latest conversations of each user. |
| Notes | The user's own, until they delete them. |
| Usage record | Who asked, the model, the tokens, the time, and for each tool its name and a short summary of what it was called on; for a change made through the assistant, the screen, the operation, the key of the record or the job — never the question, the answer, a row, a value written or the text of a note. 90 days by default; see AI usage. |
| Clients connected by sign-in | The client's name, when it connected, its last use and the day its access ends — never a token. An ended access is dropped after 30 days. |
| Attached files | Not stored. |
The licence usage report goes to the licence management tool, not to Anthropic, and carries nothing of the assistant.
What decides
| Setting | Where | Effect |
|---|---|---|
| Enabled, Anthropic API key | Administer → App → AI Assistant | Off, or no key: no assistant, nothing sent. |
| The tool switches | Same section | Connector tools, Data Explorer tools, The applications' tools: on by default. API tool, Operations tools, Scaffold tools, Write tools: off by default. |
| Allowed connectors | Same section | The connectors the assistant may read; empty means all. |
| Hide sensitive data from the assistant | Same section | Off by default — see above. |
| File attached to a question | Same section | 0: no attachment. |
| MCP endpoint (/mcp) | Same section | Off by default: no Claude client can connect. |
| Allow changes over MCP | Same section | Off by default: a Claude client reads only — see Changes over MCP. |
ai:chat, ai:write, mcp:use | Administer → Access → a role → Beyond the menus | Who uses the assistant, who writes through it, who connects Claude. |
sql:, explorer:, api: permissions and the data scope | The role | What the assistant reads for that user. |
To know before opening it widely
- The tools read what the screens show. Without the hiding, a name, an e-mail address or an amount goes to the model when a query returns it.
- Flag before turning the hiding on. The switch hides what is flagged, nothing else: review the dictionary entries of the personal and banking data first.
- Keep the API tool and the operations tools for installations that need them. Their answers are not covered by the hiding.
- The use Anthropic makes of what it receives depends on the contract of the installation's API key for the assistant, and on the user's Claude plan for MCP.