Security
Your security reviewer, your General Counsel and your privacy team all have to get comfortable. Here is what is in place today, and what we will send them.
Single sign-on over SAML or OIDC.
Multi-factor authentication, enforceable for privileged roles.
Ten roles, including a structurally read-only viewer.
Session revocation on password reset.
Per-tenant schemas with server-enforced scoping.
Encryption at rest for secrets, with key rotation.
Export, erasure and restriction for data subjects.
Review comments access-controlled, widened only by their author or the GC.
Append-only audit log.
Every decision signed into one chain, with a checker inside every download.
EU AI Act Article 50 marking, classification memo and system card.
Bring your own models and keys.
Secret and vulnerability scanning run on every build, and an incident-response runbook is in place. Containers and infrastructure-as-code are available for teams who want to run Sarga in their own cloud.
Certifications
Sarga is pre-revenue and early. Our SOC 2 roadmap is published, and Type I is scheduled with the first enterprise contract that requires it, with ISO 27001 and an independent penetration test on the same trigger. We would rather tell you that now than in a questionnaire later.
The pack includes our security overview, the control list, tenant-isolation design, the AI system card and the EU AI Act classification memo. Sent under NDA, usually same day.
Your data
Sarga trains no foundation models. There is one defined exception, and we would rather you read it here than find it in an appendix.
Review records — the content reviewed, the model's verdict and the reviewer's eventual decision — are kept to train a future Sarga-owned reviewer model.
It is a term of the master agreement, accepted by your company at contracting, not a consent checkbox collected from individual users.
A carve-out for your whole organisation is available, and it is enforced where the data is captured rather than promised downstream.
An export carries hashes of review comments rather than their text. Isolation is schema-level on shared infrastructure, not a separate database per customer.