Technical and legal pack

Your data, your processing, your models. Under your law alone.

This document answers, in the order they are asked, the questions an IT department and a security officer raise when assessing the platform before deployment.

1. Two definitions, set out first

Environment

Throughout our documents, “environment” means the client’s private instance, whichever deployment mode is chosen. When we write “no data outside your environment”, we mean that no uploaded data, no derived index and no inference request leaves that instance.

Private instance

An application stack, storage and a model dedicated to a single client. The instance is never shared between clients, including between entities of the same group if the client asks for separation by entity.

The direct consequence for a frequent question: no client data is used to train a shared model, neither ours nor a third party’s. A model further trained on a client’s documents remains attached to that client’s instance and disappears with it.

2. The three sovereignties, and why hosting covers only one

Most sovereignty commitments on the market concern storage. That is the first of the three questions, and the least demanding of the three.

The test to put to any provider, including us: ask where the inference request goes, not just where the file sits. European hosting protects storage; it says nothing about processing if the request leaves the instance.

3. Three deployment modes

The on-premise mode serves classified environments, export-controlled data and internal policies that prohibit any processing outside the organisation’s walls. It changes neither the features nor the evidence mechanism.

4. Reversibility: the clause to read before all the others

An experienced IT department judges a provider on its exit before judging it on its features. Four commitments, to be checked in the contract.

Return of data

Your documents and all approved answers, exported in a format reusable without our platform, with their metadata: source, page, version, score, approver, timestamp.

Dated and complete deletion

Documents, indexes, vector representations, application logs, caches, backups, and propagation to any subcontractors. Each scope is named in the contract, with its deadline.

Auditable attestation

A signed, dated document listing what was deleted, where and when, which you can rely on at your next audit.

Model

The model dedicated to your instance is destroyed with it. Nothing learned from your documents survives anywhere else.

In on-premise mode, reversibility is inherently simpler: nothing has ever left, deletion is an operation internal to the client, and our attestation covers only the software deliverables.

5. Certifications: distinguishing the vendor from the host

6. The twelve questions, to send back to us completed

Send this page to your sales contact, or write to us directly: we return it completed, dated and signed, and it becomes a document in your assessment file.