Everything you put in here is confidential. We built it as if we knew.
You have a duty of confidentiality that doesn't bend for a software vendor. So confidentiality isn't a feature we added. It's the frame the product was built inside, from the first line of code.
Last updated October 2026
- Data in the EUDocuments and matters are stored in the EU.
- AI in the EUThe language model runs via AWS Bedrock in the EU.
- No trainingYour data trains no models. Not ours, not anyone else's.
- Data processing agreementYou are the controller. We are the processor under GDPR.
Where it sits, and what happens to it.
- 01
Your data stays in the EU
Documents, conversations and work product are stored in the EU. The language model runs via AWS Bedrock in the EU. Neither leaves the EU.
- 02
We don't train on your data. Nor does anyone else.
Your information is read to answer your question, and then it's done. It never becomes training material, for us or for a model provider.
- 03
Your firm has its own space
However many firms use Clerk'r, every query is limited to your organisation, so your documents and matters cannot be reached from outside it. Inside it, access follows the permissions you set on the matter. Your administrators can see every matter.
- 04
Email that isn't about a matter stays out of your matters
If you connect Outlook, only email that matches a matter is filed on it. For email that doesn't match, Clerk'r keeps the sender, subject and date on a list only you can see, so you can file or dismiss it. The body is not stored. Connecting is per person.
- 05
Your originals stay, and the work is recorded
When Clerk'r changes a document you uploaded, the original stays and the change becomes a new version. Every agent run is recorded: what ran, on which matter and on whose instruction. If you need to account for how a document came to be, the record is there.
- 06
Encrypted in transit and at rest
All traffic runs over TLS 1.2 or higher. Documents are encrypted with AES-256, the database is encrypted on disk, and integration keys are encrypted in the application before they are stored.
Not just where data sits, but what the agent may do with it.
Most legal AI tools answer questions. Ours does work. That needs its own limits, and they are built into the system. They aren't instructions we hope it follows.
It cannot send
Clerk'r has no tool that can send. It writes drafts, and a person sends them. It isn't told to hold back. The ability isn't there.
Nothing leaves Clerk'r without a person
Pushing a draft to Outlook, sending a document to Legis365, moving or archiving a file. Each one stops and waits for an approval.
It cannot read outside the matter
Access follows the permissions on the matter. A lawyer who can't open a matter can't reach it by asking Clerk'r either.
It shows where it got it from
Answers drawn from your documents point to the passages they are based on, so you can check the source before you use it.
It doesn't guess
Work Clerk'r starts by itself only begins when the matter is certain. If it can't tell which matter, or the instruction is unclear, it asks you instead.
From your question to your answer.
- Your organisation01
Your question
Asked from the web, Word or Outlook.
- EU02
Clerk'r
Checks your access against the matter and fetches only what you may see.
- EU03
Language model
Runs via AWS Bedrock. No training, nothing kept by the model provider.
- Back to you04
Your answer
With sources. Logged. Anything that leaves Clerk'r waits for your approval.
You are the controller. We are your processor.
- Data processing agreement
Processing is governed by a data processing agreement with technical and organisational measures and a list of sub-processors.
- Security breaches
If we discover a breach, we notify you without undue delay and help with what you need for your own notification.
- Deletion and access
We help with access, rectification and erasure on your instruction. When the agreement ends, we delete or return your data, as you choose, without undue delay.
Built with people who do this for a living.
Security and data protection in Clerk'r aren't something we guessed at. Emil Marburger, partner at Skau Reipurth and member of the Danish Bar and Law Society's committee on data protection, advises us on data protection, GDPR and the AI Act, and has helped set the frame for how the system handles your data.
Bring your IT lead to the demo.
The questions they ask are the ones we designed around. We'd rather have them in the room early.