Separated client spaces
Data is organised by space and scope, with clear separation between client contexts, administration and operational work.
Security & data
A trust posture designed for European cyber teams.
Torus treats client documents, exchanges and evidence as sensitive material. The platform favours separation, minimisation, human validation and no default reuse.
Explicitly enabled documents
Client documents are used by the assistant only when they are enabled for the relevant scope.
Human-controlled evidence
Torus can help review uploaded evidence and flag what appears sufficient, incomplete or inconsistent; validation remains human.
Auditable exports
Reports, workbooks and evidence are designed to be reviewed, shared and retained as working material.
Principles
What Torus protects first.
Security is not decorative copy: it shapes how the assistant, e-learning, risk analysis and evidence workflows are designed.
Separated client spaces
Data is organised by space and scope, with clear separation between client contexts, administration and operational work.
Explicitly enabled documents
Client documents are used by the assistant only when they are enabled for the relevant scope.
Human-controlled evidence
Torus can help review uploaded evidence and flag what appears sufficient, incomplete or inconsistent; validation remains human.
Auditable exports
Reports, workbooks and evidence are designed to be reviewed, shared and retained as working material.
AI & confidentiality
No client reuse by default.
AI exchanges must remain aligned with the expectations of a CISO, cyber consultant or compliance team.
ZDR enabled
ZDR means Zero Data Retention: client data sent to the model during AI exchanges is not retained for training or reuse.
No reuse for training
By default, Torus does not reuse client documents, evidence or conversations to train models or enrich datasets.
Separate agreement for contributions
Any potential contribution to a Torus reference set would need a separate, explicit, minimised, redacted and validated contractual process.
Client context comes first
When client documents are enabled, they remain the primary source; Torus cyber and compliance references support without replacing client context.
Clear boundaries
What Torus does not promise.
01
Torus does not promise automatic compliance.
02
An AI answer does not become evidence by itself.
03
Removing a name from a document is not enough to call it anonymous.
04
Generated deliverables remain drafts or working material to validate.
05
Risk, audit and compliance decisions remain under human responsibility.
Discuss your trust requirements.
A useful demo can also cover your data, validation, evidence and scope-separation constraints.