What happens to your data when your organisation connects the Just connector to Claude. This supplements the Just privacy policy, which continues to govern everything else.
Last updated: 17 August 2026
This notice describes what happens to your data when your organisation connects the Just connector, an optional integration that lets your users query their own Just data from Anthropic's Claude. It supplements the Just Privacy Policy and your organisation's agreement with Just, including any Data Processing Agreement you have entered into with us, which continue to govern everything else.
The legal bases on which Just processes personal data, and how individuals exercise their rights, are set out in the Just Privacy Policy and are not changed by the connector.
If your organisation has not connected the connector, nothing in this notice applies to you.
No data reaches Anthropic through the connector unless a user in your organisation actively connects it and signs in with their Just credentials. It is not enabled by default, and it carries no separate charge. It can be turned off again at any time. See "Turning it off" below for how to do that so it takes effect immediately.
When a user asks a question that a connector tool answers, the response contains data drawn from your organisation's own records in Just. Depending on the question, that includes:
This is identifiable data about your organisation. It is not aggregated or anonymized, because the purpose is to answer questions about your own trades.
Traffic through the connector's query tools runs one way. Just answers requests. It does not receive what your users type.
When a user asks a question in Claude, Claude decides which connector tool answers it and calls that tool with structured parameters: a date range, a currency pair, a provider, a business unit. That structured request is all Just receives. The question itself, and everything else in the conversation around it, stays in your Claude workspace and is never sent to us.
This holds because of how the connector's query tools are defined, not because of a policy we apply after the fact. None of them accepts a free-text parameter, so there is no field in a request for a sentence to travel in, whether about a counterparty, a colleague, a negotiation or anything else. If we ever add a query tool that accepts free text, we will update this notice before it ships.
Uploading a trade confirmation is the exception, and it is deliberate. When a user uploads a confirmation through the connector, the document itself is sent to Just and parsed, exactly as the web application parses an upload. That is the only path on which content travels from Claude to Just. It happens because a user chose to send that document, and nothing else in the conversation travels with it.
Responses travel from Just's servers to the Claude client your user is signed in to. That client is operated by Anthropic PBC, United States.
Anthropic is not a subprocessor engaged by Just. Your users sign in to Claude with your organisation's own Anthropic account, under your organisation's own agreement with Anthropic, and Just transmits data to that client at your user's request. Anthropic processes it for you, not for us. Just neither selects nor instructs Anthropic on your behalf.
Once data reaches your Claude workspace, its handling is governed by the agreement between your organisation and Anthropic, including retention, access by your users, and whether it may be used to improve Anthropic's models. Just does not control your Claude workspace and cannot delete data from it. We recommend confirming your Anthropic plan's data handling terms before connecting, particularly if your users connect from individual rather than organisational Claude accounts.
Just stores and processes your data in the region that matches your organisation. Customers in Europe are hosted in the EEA. Customers in North America are hosted in the United States. Your subscription records which applies to you, and the connector reads from the same regional store as the Just application. Connecting the connector does not move your data between regions.
Wherever your data is hosted, it leaves that store when a user in your organisation queries it through the connector, because that user directed it to their own Claude client. For an organisation hosted in the EEA, that is a transfer outside the EEA.
Because the destination is a service your organisation has engaged directly, the transfer is made on your instruction as controller rather than by Just on your behalf. The safeguards covering it are those in your own agreement with Anthropic. If your organisation needs Just to stand behind that transfer instead, tell us before connecting, because that is a different arrangement and needs to be agreed in writing.
Just logs the fact that a connector request was made: the timestamp, the signed-in user, the tool called, and its structured parameters. These logs are retained for 30 days and are used for security monitoring, support, and understanding which tools are used. As described above, no free text from your users is present in these logs, because none is received.
Trade data queried through the connector is the same data already held in Just under your subscription. Using the connector does not change its retention, and it is deleted on exit under the existing terms.
An administrator can end a user's connector access at any time by removing or suspending that user's access in Just. This takes effect immediately.
Removing the connector inside Claude also stops that client from making further requests. A session token already issued to it may remain valid until it expires, so where access must end at once, remove the user's access in Just as well.
Ending access stops all future transmission. It does not remove data already delivered to your Claude workspace, which you control.
Questions about this notice go to privacy@gojust.com.
Just Technologies AS · Oksenøyveien 8, 1366 Lysaker, Norway · Org. nr. 918 907 661