Tenant isolation enforced in the database rather than in application code. Recordings encrypted with keys you hold. An audit log you can prove wasn't altered. Answer the questionnaire from the product.
Illustrative interface. Request identifiers, counts and states are sample data, not a performance claim. The screen shows an OptiML governance view: a completed erasure request with its scope and the number of recordings destroyed and transcripts redacted, an audit integrity proof verified, guardrail results, an approval gate on refunds, a cost cap, and the tenant's isolation, recording-key and data-residency settings.
Three numbers you can put straight into a questionnaire, each of them a property of the build itself and not a policy statement about it.
Nine control areas, and the specific mechanism that satisfies each one. This is the table that answers most of a security questionnaire before the call starts.
| Control area | What OptiML gives you |
|---|---|
| Tenant isolation | PostgreSQL row-level security on 231 tables, fail-closed tenant context |
| Access control | 300+ granular permissions, hierarchical and custom roles, resource-scoped grants, channel allow-lists |
| Identity | SSO across 8+ providers, SAML and OIDC, SCIM provisioning, TOTP MFA |
| Encryption | AES-256-GCM envelope encryption, per-recording keys wrapped by a tenant key in KMS, TLS and mTLS in transit |
| Audit | Immutable log of every mutation, per-tenant integrity proofs, signed exports, SIEM streaming |
| Data subject rights | Erasure with regulator-proof logs, DSAR register, opt-out handling, configurable retention |
| PII | Detection and redaction across transcripts, logs, exports and analytics, with severity scoring |
| AI-specific risk | Guardrails for injection and PII, cost caps, approval gates, full model-call tracing |
| Residency | Regional hosting with per-tenant retention; customer-managed data residency on Enterprise |
Six pages that carry the detail behind the table above, including the parts of the platform a risk review usually has to ask for separately.
The difference between a control and a claim is whether something other than good intentions stops the failure. Each of these four is enforced by a system that does not depend on application code behaving.
PostgreSQL row-level security on 231 tables with fail-closed tenant context, so a defect in application code cannot leak data across tenants.
AES-256-GCM envelope encryption, per-recording keys wrapped by a tenant key in KMS, TLS and mTLS in transit.
An immutable log of every mutation with per-tenant integrity proofs, signed exports and SIEM streaming, retained 30 days minimum and configurable per tenant.
Regional hosting with per-tenant retention. On Enterprise, customer-managed data residency puts your database and recordings in your own cloud account.
There is one product and one place it runs. The option on top of it concerns data location, which is usually what the obligation actually turns on.
Multi-tenant SaaS in the region you choose, with tenant isolation enforced by PostgreSQL row-level security on 231 tables. Operated, patched and scaled by RMT, against a 99.9% monthly uptime commitment in the SLA.
Everyone. This is the product.
Your database and recording storage in your own cloud account or your own datacentre, privately connected, with encryption keys you hold. The application, AI runtime, media plane and console continue to run in OptiML Cloud.
Regulated buyers whose obligation is about where the data lives.
Dedicated single-tenant hosting is an Enterprise option: an isolated single-tenant instance inside OptiML Cloud, in your chosen region, with its own retention windows and compliance posture and no shared infrastructure. Still operated by RMT. The platform itself always runs in OptiML Cloud. Customer-managed data residency moves your data, not the software. Your account holds the only durable copy of transcripts and recordings; PII-redacted operational telemetry and a bounded message-queue window persist with RMT, and the trust centre names every row.
The trust centre carries the full control inventory, the sub-processor list and the document request form. The customer story will sit here once a named customer has approved it in writing.
We publish outcome figures only with the customer's written approval, so this slot stays empty until one is signed off. In the meantime the mechanism above is the honest version.
Certification claims are statements about a third-party auditor's finding, so a badge appears only once the certificate is issued and links to the certificate or the auditor's register. Customer quotes need written approval from the named customer.
Everything on this page is the OptiML CX Platform configured for Security & Compliance, not a separate product. These are the modules it leans on.
Bring a call recording, a policy document or a WhatsApp thread from your own operation. We ground an agent in it and run it live on the call. What you hear is your own material, not a canned demo.
30 minutes, on your own content. No slide deck unless you want one.
Your details stay private. We never share them.
