docMan and AI – what happens to your documents.
docMan reads receipts and invoices using artificial intelligence: Claude by Anthropic. This saves most of the typing – and raises the legitimate question of what happens to the documents in the process. Here it is, openly: when something goes to the AI, what exactly, what Anthropic does and is allowed to do with it, and where the limits are.
↓ Download PDF (German)In short
- Only what docMan is currently meant to read or write goes to the AI – one receipt, one question, one letter. Never the whole database, never passwords, never bank logins, never the backup.
- Anthropic may not train AI on it. This is in the contract.
- Anthropic deletes the requests after 30 days at the latest (exceptions below).
- Transmission is encrypted; the agreement under Art. 28 GDPR, including the EU Standard Contractual Clauses, is part of the terms.
- Voice recordings (dictation) never leave the premises: speech recognition runs on the docMan server itself.
- The AI never acts on its own: it makes suggestions, a person decides.
When does what go to the AI?
| When … | sent to Anthropic |
|---|---|
| a receipt or invoice is imported | the PDF of the document (text and page image) and the lists used for sorting: companies, categories, payment methods. What comes back: supplier, date, amount, invoice number, IBAN, filing location. |
| someone asks docMan Ai something | the question and what docMan has found on it in its own database – only the relevant rows; on request, the pages of a document as an image |
| a contract is analysed | the text of the contract PDF |
| a letter is drafted or translated | the draft or the document to be translated |
| docMan Ai searches the internet | only general search terms – no names, amounts, IBANs or invoice numbers from docMan |
What never goes to the AI
- Passwords, login details, bank PINs and TANs – they are stored encrypted on the docMan server
- the database as a whole, the backups and any documents not currently being read
- voice recordings from dictation – speech recognition runs locally, and the recording is deleted afterwards
What Anthropic may do with it – and what not
| Question | Answer |
|---|---|
| Is it used to train AI? | No. The terms of business for the interface rule this out: Anthropic may not train models on customer content. |
| Who owns the results? | The customer. Inputs remain theirs, and the outputs belong to them. |
| How long is it stored? | Requests and responses are deleted after 30 days at the latest. Exceptions: up to two years if abuse detection is triggered; also where required by law. |
| How is it protected? | Encrypted in transit (TLS 1.2 or later), encrypted at rest (AES-256). Anthropic is certified to ISO 27001 and ISO 42001 (AI management systems) and has SOC 2 reports. |
| Who is the contracting party? | For customers in the EU: Anthropic Ireland, Limited – under Irish law. |
| Where is it processed? | Data is stored in the USA and processed in data centres in several countries. Anthropic does not currently offer EU-only processing for the interface. The transfer is safeguarded by the EU Standard Contractual Clauses, which are part of the contract. |
| What if something happens? | Anthropic reports security incidents within 48 hours. |
Legally on a sound footing
- Data processing: Anthropic processes the data only on instruction. The agreement for this (Data Processing Addendum, under Art. 28 GDPR) is part of the terms of business, and the EU Standard Contractual Clauses are included in it.
- In the contract with us: Our data processing agreement names Anthropic as a sub-processor. The customer therefore knows in advance who sees what.
- If you want more: On request, Anthropic offers businesses an agreement under which requests are not stored at all (Zero Data Retention). We are clarifying whether and how we can use this for docMan customers.
To be honest: AI-assisted document import is not possible today without any data transfer at all. We keep it as small as possible – only the one document, only the relevant rows – and we say openly where it goes. Everything else stays on your own server.
Sources (accessed 15.11.2026): Anthropic Commercial Terms (anthropic.com/legal/commercial-terms), Data Processing Addendum (anthropic.com/legal/data-processing-addendum), Privacy Center (privacy.claude.com: training, retention period, server locations, certifications), developer documentation on data retention and data residency (platform.claude.com/docs). Anthropic may change these terms; we review them regularly.