One dedicated instance per client
Every client gets their own instance: separate database, search index and files. No application is shared between clients.
Security & data
One instance per client, hosted in France.
Torus treats your documents as sensitive data. Every client gets their own instance, operated by Torus in France, and the AI is used under a ZDR contract.
01
One dedicated instance per client
Every client gets their own instance: separate database, search index and files. No application is shared between clients.
02
Access per knowledge base
Your administrators decide who reaches each base. A user only sees documents from the bases opened to them, including in the sources cited.
03
Contractual ZDR
Those models are used under a ZDR (Zero Data Retention) contract signed with Mistral: the data sent is not kept by the provider.
04
Hosted in France
Instances are operated by Torus at OVHcloud, in France. The instance exposes HTTPS only: neither the database, nor the search index, nor the internal services are published on the internet.
Principles
What Torus protects first.
Security governs how an AI may be used on internal documents. It shapes the way Torus stores, searches and transmits your data.
Access per knowledge base
Your administrators decide who reaches each base. A user only sees documents from the bases opened to them, including in the sources cited.
Hosted in France
Instances are operated by Torus at OVHcloud, in France. The instance exposes HTTPS only: neither the database, nor the search index, nor the internal services are published on the internet.
Traceability
Administration actions are written to an audit log; risk analyses keep the history of their decisions.
Documents scanned on the way in
Every imported file is scanned by an antivirus and its text is extracted in a sandbox, because a booby-trapped document attacks the extraction chain first. Your documents are never sent to a third-party scanning service.
Locked backups
Backups go to a separate object storage in another region, where they are locked against deletion for their retention period.
AI & confidentiality
Your data only serves to answer you.
Exchanges with the AI have to match what a CISO, a cyber consultant or a compliance team expects.
01
Which models, and whose
The models come from Mistral, a French provider. The model in use is set by Torus at deployment, per task: neither a user nor an instruction written inside a document can change it.
02
Contractual ZDR
Those models are used under a ZDR (Zero Data Retention) contract signed with Mistral: the data sent is not kept by the provider.
03
The minimum sent
Text extraction and indexing happen inside your instance. To answer, only the question and the retrieved excerpts are sent to the model.
04
No training on your data
Torus does not use your documents, conversations or analyses to train models.
05
Torus frameworks kept apart
The cyber pack's frameworks are managed by Torus in bases separate from yours; the pack's agents never mix your documents into them.
Limits we own
What Torus does not promise.
01
Torus does not promise automatic compliance.
02
An AI answer does not become evidence on its own.
03
Torus submits nothing to a regulator and takes no legal decision.
04
Generated deliverables remain drafts or working material to validate.
05
Risk decisions remain your team's responsibility.
06
The instance does not run in high availability: after a hardware failure, the service comes back through a restore, not an automatic failover.
07
The backup protects your accounts, analyses, conversations and document metadata, but not the source files: if the document storage is lost, the documents must be imported again.
Service availability
Service status is published continuously on our status page.
Let's talk about your trust framework.
A demo can also cover your constraints around hosting, data, validation and access separation.