SCRS is the firewall the whole suite is built on: it blocks unauthorised data before the AI can see it. Add SSO, BYOK, data residency and matter walls, and you have enterprise-grade trust without an enterprise project.
A firewall, not a filter — private data never reaches the model.
Permissions are enforced during retrieval — out-of-scope data is removed before results even exist.
The vector index holds no readable text; content lives in a separate encrypted store, tokenised.
Content is released only after cryptographic verification. Any failure returns nothing.
Most “AI privacy” relies on asking the model nicely to behave. We don’t. Identifiers are detected and swapped for reversible tokens before a single byte leaves for a third-party LLM — so the model reasons over client_4821 while you keep reading Henderson Ltd.
SCRS isn’t a feature of one app — it sits under all of them, so the same rules apply wherever data moves.
Pipelines, deals and client matters with field-level RBAC and ethical walls between clients.
See CRM →Bring-your-own mailbox AI triage and free Document, Workbook & Deck editors — all governed.
See Email & Docs →An autonomous chat agent and SLA-driven ticketing — transcripts redacted before the model sees them.
See Live Chat →Forms, booking pages and the joiner–mover–leaver directory — offboarding flips the kill-switch.
See Flows →DSAR, RoPA, consent, DPIA, AI impact assessments and operational registers in one workflow.
See Governance →Storage, residency, retention, access and billing governed from a single console.
See Control Center →Offboarding shouldn’t mean a frantic checklist and a forgotten share link. In Other Me, marking a person as a leaver in HR-lite trips the SCRS kill-switch — their access is logically revoked across every module at once, and the action is written to the audit ledger.
See HR-lite →Add a person once; role-based access flows to the modules they need — nothing more.
Change a role and permissions follow. SCRS re-scopes what the AI can retrieve on their behalf.
Mark them a leaver — the kill-switch revokes data access everywhere, logged with a reason.
Coming soon — ask us about early access.
SAML/OIDC single sign-on and automated provisioning.
Bring your own keys; crypto-shred to delete by destroying keys.
Pin storage and processing to your region.
Hard isolation between clients and teams, enforced and logged.
These enterprise controls are on the way and not yet purchasable. Talk to us about early access →
A live Trust Center shows your security posture, hosts your policies, and — with Governance — auto-answers the security questionnaires that slow deals down. Every claim backed by the tamper-evident audit ledger.
Explore Governance →Hash-chained log of every access and action.
Suspend AI or a tenant instantly, with a logged reason.
Your content is never used to train shared models.
The plain-English answers to the questions a buyer’s security team always asks.
Storage and processing sit in the UK / EU. Content is held in an encrypted store, kept separate from the search index — which carries no readable text at all.
Field-level role-based access decides what each person sees, and SCRS enforces it during retrieval — not as an after-the-fact filter on results that already exist.
Personal data is tokenised before any third-party model call. The model reasons over placeholders; real values are restored inside your tenant. Your content is never used to train shared models.
Every access and action is written to a hash-chained, tamper-evident ledger — the evidence behind a DSAR, an incident review, or a routine audit.
We’ll never claim a certification we don’t hold. Here’s exactly where we are.
| Framework | Status | What it means today |
|---|---|---|
| UK GDPR | Compliant | Lawful basis, data-subject rights and our DSAR / RoPA tooling are in place. |
| UK Age Appropriate Design Code | Compliant | Built to the Children’s Code where it applies. |
| ISO/IEC 42001 (AI management) | On track | Actively working toward it — not yet certified. |
| SOC 2 Type II | On roadmap | Planned (Q4 2026 / 2027). Not yet audited or certified. |
| ISO/IEC 27001 | On roadmap | Planned (Q4 2026 / 2027). Not yet certified. |
| HIPAA | By BAA / contract | Available under a Business Associate Agreement where required. |
| EU AI Act | Monitoring | Tracking obligations as the framework takes effect. |
Nothing on this page is certified yet. We use “on track” and “on roadmap” deliberately — and the audit ledger is there to back up what we do claim. See the Governance suite →
Accountancy, legal, mortgage & IFA and healthcare teams can’t paste client data into a generic chatbot and hope. SCRS lets them use modern AI without handing client identities to a model — with the ethical walls, audit trail and offboarding controls their regulators expect.
“The point isn’t to trust the AI with client data — it’s to make sure the AI never gets it in the first place. That’s the difference between a filter and a firewall.”
— The design principle behind SCRS
SCRS protects every module — CRM, Mail, Documents, Live Chat and the rest — and all of it is governed from one Control Center.
See the Control Center →