Security and reliability
Where your clients’ data is. Who sees it, how long it stays.
For each measure we say whether it is already in place, guaranteed before you start, in progress or available on request.
Documents encrypted in Milan, database in Frankfurt, AI processing in the European Union.
No retention on the model service and no access for the people who develop the models. Your content trains no model.
Isolation enforced by the database, access by invitation. Of our staff, only those working on your engagement have access.
The questions
The questions we are asked most often.
- In place
- Before you start
- In progress
- On request
- “Before you start” means in force before you upload your first papers.
- Where is the data?
- In Milan the documents and the application, in Frankfurt the database, in the European Union the AI processing.
- In place
- Does any data leave Europe?
- Only login details, name and email, and notification emails, handled by two US providers under standard contractual clauses. Documents, database and AI processing stay in the European Union.
- In place
- Is any model trained on the content?
- No, neither the providers’ models nor ours.
- In place
- Does the AI provider retain the content?
- No. The model service is configured to retain nothing, and the model developers have no access to it.
- In place
- What encryption do you use?
- TLS 1.2 or higher in transit, AES-256 at rest.
- In place
- Can other clients see my data?
- No. Isolation is enforced by the database and proven by dedicated tests.
- In place
- Does your staff access my documents?
- Yes, but only a small group of people, named individually and bound to confidentiality: they run the service and prepare the documents you order.
- In place
- Can I find out who has had access?
- Yes. Every access is logged with its reason, and you can ask for the report.
- Before you start
- What can an agent do on my engagement?
- Only the task it is given, with the tools for that task and on that engagement’s papers. It does not write into your systems, and you decide what goes into the document.
- In place
- Can I see what an agent did?
- Yes. Every step is recorded with the agent, the paper and the outcome, and the full trail arrives with the document.
- In place
- Who owns what the engagements produce?
- Your organisation: the knowledge graph, the wiki and your standard, that is, your analyst’s corrections. At the end of the contract you export them.
- In place
- Can our systems and our agents connect to ArgusOne?
- Yes, through the API and an MCP server, with your organisation’s credentials. Through the API a system opens an engagement, uploads the papers and collects the documents, and every request is recorded.
- In place
- Is the data pseudonymised?
- Protection lies in the architecture: processing in the European Union and no retention. Pseudonymisation is an extra layer that can be switched on.
- On request
- Can it be kept in Switzerland?
- Yes, in a dedicated environment in Zurich for documents and database. AI processing runs between Switzerland and the European Union.
- On request
- Can I manage the encryption keys myself?
- Yes, in the dedicated environments. If you revoke the key, the data becomes unreadable, even to us.
- On request
- What happens at the end of the contract?
- Export on request, then deletion within 30 days, with written confirmation.
- Before you start
- And in case of a data breach?
- We notify you within 48 hours of becoming aware of it. It is written into the contract.
- In place
- Do you have ISO 27001?
- It is in progress with IMQ, and the audits are scheduled for the first half of 2027.
- In progress
The details
The details for IT and compliance.
Why we do not write “end-to-end”
A service that analyses documents has to be able to read them, and that holds for anyone who uses AI. The correct wording is “encrypted in transit and at rest”, and you can use it with your own clients too:
Data is encrypted in transit (TLS 1.2 or higher) and at rest (AES-256). It is decrypted only in memory, for the time needed for processing, in European Union data centres. The AI service does not retain it and does not use it for model training.
How long the data staysAutomatic deletions are carried out by scheduled processes.
| Uploaded papers and delivered documents | Until you delete them, or until the end of the contract |
|---|---|
| Conversations with the assistant | 90 days after the last message |
| Tool outputs | 30 days |
| Audio to be transcribed | Until the transcription is finished |
| Export archives | 24 hours |
| Everything, at the end of the contract | Within 30 days, with written confirmation |
CertificationsWe say what we have, and when we will have the rest.
| ISO/IEC 27001:2022 | In progress with IMQ, an accredited body. Audits scheduled for the first half of 2027. |
|---|---|
| Cloud infrastructure | AWS, certified ISO 27001, 27017, 27018, SOC 1, 2 and 3, C5. |
Need the detail for your due diligence?
The full white paper, with the list of providers and the measures guaranteed before you start, is available under NDA.