Security model - Clarivy

Tenant and connector boundary

Clarivy tenant boundary with approved connectors and audit lineage — Authority is server-derived. Connectors do not choose tenants, rewrite policy or bypass audit lineage.

Secure document request loop

Clarivy secure document request, reminder and upload loop — Evidence requests use approved templates, tenant-bound dispatch, a secure upload portal and delivery outbox status before case attachment review.

Control model

Control	Product behaviour	Production evidence
Identity	Bearer session or scoped service credential establishes the caller.	Enterprise sign-in policy, MFA and access-review records
Tenant scope	The API derives organization context; the browser cannot select another tenant.	Cross-tenant denial tests and database RLS tests
Least privilege	Roles, use-case scopes and capabilities guard protected actions.	Role matrix, periodic review and denied-action logs
Evidence integrity	Sources, excerpts, timestamps, actors and hashes remain attached.	Hash verification and artifact lifecycle records
Human oversight	AI output is a proposal; material evidence and decisions require a named person.	Model-run ledger and reviewer rationale
Replay safety	Idempotency and signed-event checks prevent duplicate effects.	Retry, duplicate and stale-event tests
Audit lineage	Actions append rather than overwrite historical state.	Exportable event chain and verification results

Shared responsibility

Area	Clarivy provides	Customer confirms
Purpose and policy	Case-bound purpose, legal basis and immutable workflow versions.	Approved use cases, legal interpretation and prohibited uses.
Identity and access	Roles, server-derived tenant context and scoped credentials.	Identity provider, MFA policy, joiner/mover/leaver process.
Data handling	Retention metadata, lineage and controlled evidence storage paths.	Residency, retention, legal hold, deletion and export requirements.
AI providers	Provider adapter, minimization, schema and citation validation.	Approved provider, region, model, DPA and remote-processing permission.
Connectors	Signed intake, replay protection and explicit event allowlists.	Provider licence, credentials, field mapping and sandbox certification.
Incident response	Product logs, evidence preservation and technical runbooks.	Notification contacts, regulatory assessment and customer response process.

Security rules for evidence

The client cannot choose tenant, audit actor or storage path.
Every uploaded artifact receives a generated identifier and hash.
Public and regulatory claims require a reviewable source URL.
Connector events remain signals until mapped and reviewed.
Qdrant or vector retrieval is never the authoritative record.
Sensitive prompt and document bodies stay out of telemetry.
Secrets never enter workflow documents, Git or browser code.
Historical policy and review state is not silently rewritten.

Required before regulated production

Gate	Required outcome
Enterprise authentication	OIDC or SAML SSO, MFA, provisioning and auditable access reviews.
Authoritative data isolation	PostgreSQL row-level security and tenant-filtered retrieval.
Keys and encryption	Managed KMS, rotation, encrypted object storage and backup controls.
Document safety	Malware scanning, quarantine release and recipient verification.
Privacy operations	DPIA, processing inventory, rights handling, retention, deletion and legal hold.
Operational resilience	Monitoring, incident response, restore tests and agreed recovery objectives.
Customer acceptance	Security, privacy, legal and provider boundaries approved in contract.

No compliance certification by implication

Product controls support a customer’s governed process. They do not make Clarivy, a connector or an AI model automatically compliant with every regulator, jurisdiction or customer policy.

Deployment guidance