Security & privacy
Enquiry data deserves the highest protection.
Casey is built for UK firms handling sensitive accounts and lead files. This page covers the current controls, limits, and shared responsibilities.
Approach
Privacy, access, and a trail you can explain.
Privacy
Designed for sensitive legal work
Lead files, accounts, written drafts, and exhibits can contain highly sensitive personal data. Casey is built around controlled access, clear accountability, and cautious defaults.
Access
Firm-scoped at the database layer
Casey uses Supabase row-level security policies so firm boundaries and role checks are enforced in the database, not only in the user interface.
Audit
A trail you can explain
Important activity across statement preparation, follow-up, final review, and administrative actions is designed to leave an operational trail.
Controls
How Casey protects access and activity
Security is applied across the user, firm, lead, account, and private-link layers. The controls below are a high-level summary, not a substitute for a firm's own information security review.
Role-based write controls
Firm users are assigned roles such as firm admin, solicitor, or paralegal. Sensitive case, statement, magic-link, and storage writes are restricted by database policies to appropriate roles.
Time-bound account links
The fuller account is accessed through tokenised links tied to one person, with expiry and state checks before sensitive actions proceed.
Server-side enforcement
Public account operations go through server-side routes that validate token scope, account state, expected document paths, upload limits, and rate limits before privileged storage actions run.
Scoped data access
Application queries, RLS policies, and storage policies are designed to limit access to the correct firm, matter, statement, and document context.
Operational monitoring
Request logging is sanitized to avoid bearer-token leakage, and audit-style event records help identify unexpected access patterns and reconstruct important workflow activity.
Document safeguards
Template and DOCX review tooling helps reduce errors in generated legal documents before they are published or used in live work.
Implementation
What is enforced today
The controls below describe the current implementation rather than a future target state. They are intentionally specific so firms can evaluate whether the model fits their risk profile.
Current model
- Firm isolation is enforced with Supabase RLS policies for application tables and storage policies for organisation buckets.
- Paralegal, solicitor, firm-admin, and app-admin roles are not treated as interchangeable for write access.
- Account links are bearer-style access tokens, so logs redact token-like path segments and public routes re-check token validity before each sensitive action.
- Uploaded evidence is stored only through server routes for public intake, with server-derived metadata and expected path prefixes.
- Data is not currently application-level encrypted before it is written to Supabase. Transport encryption, Supabase platform controls, RLS, and access controls are therefore important parts of the current model.
- Firms with a requirement for customer-managed keys or field-level encryption should raise that during security review before using the platform for highly sensitive matters.
- Interview replies and analysis prose are generated through Cloudflare AI Gateway. Jev scores interview routing and case-analysis completeness or contradictions through Cloudflare's typesafe/jev model. Jev is fail-open: if scoring is unavailable, Casey continues with the LLM path.
Account links
An account without opening the rest of the file.
People giving an account do not need access to an internal legal dashboard. Casey uses a private link for that account.
Account-link security model
This separation helps firms collect an account while reducing exposure of unrelated leads, team dashboards, template settings, or administrative tools.
Account safeguards
- Privacy notice acknowledgement before the account continues
- Token checks before interview, follow-up, evidence, and final-review actions
- Direct anonymous storage access removed from public account flows
- Statement-specific storage path validation for evidence and signed documents
- Upload count, size, file-type, and persistent rate-limit controls for public evidence endpoints
- Statement-state validation to reduce accidental post-submission changes
- Final-review and follow-up routes separated from internal firm dashboards
Shared responsibility
Platform controls, practice obligations.
Casey provides platform controls, but each firm remains responsible for how it configures access, instructs users, and applies its own professional, regulatory, and data-protection obligations.
What the firm owns
- Choose appropriate user roles and remove access when team members change matters or leave the firm
- Confirm the legal basis, privacy notices, retention rules, and client-care wording used for live matters
- Use strong identity practices for firm email accounts and devices used to access the platform
- Avoid sharing account links outside the intended recipient and matter context
- Review exported documents before filing, serving, or relying on them
- Maintain internal policies for incident response, retention, supervision, and staff training
Incident and vulnerability reporting
If you believe you have found a security issue, please report it promptly and avoid accessing, modifying, or sharing any data that is not yours.
Ready to map Casey to your intake process?
This page describes the product's high-level security design. Read it alongside your own policies, supplier due diligence, and professional duties before using the service for live matters.