Built for a regulated environment
Built for regulated desks. EU-resident by design.
Pasted investor-relations material may contain inside information. That is why the product sits behind a login. Storage and inference are held in-region, access is gated and tenant-isolated, and the design separates where data is stored from where it may be sourced.
Data residency
Persistent data stays in London.
Supabase Postgres, Auth and Storage run in the London region (eu-west-2). All stored data stays in-region, and there is no out-of-region replica of documents, claims or surfaces.
The regulated part is storage, not sourcing. Sourcing may reach anywhere in the world; a public-sourcing request carries a query out, never stored material. Only stored data and document text sent to inference are held in-region.
Document text goes to the EU, never the US.
Claude runs via AWS Bedrock on an EU inference profile, not the direct Anthropic API. Document text enters through London and stays within the EU.
The fallback chain is EU-only: another EU Bedrock region, then an EU Vertex path. There is no fall-through to a US region. Restricted content does not leave the EU.
MNPI handling
Restricted documents are handled as restricted.
Anything that may contain inside information can be flagged as restricted on paste, and then it is:
- Encrypted at rest in a private bucket
- Held to a 30-day default retention
- Reachable only through signed URLs on demand
Every document, restricted or not, is sanitised before it is stored and is never treated as instructions to the model.
Access and tenancy
Auth gates everything. Multi-tenant from day one.
Access is by magic-link, and an open URL onto a store that may hold inside information is exactly what the login prevents. The schema is multi-tenant from the first migration: a user_id column and row-level security on every table, so onboarding a second client is a grants change, not a rebuild.
Information barriers are designed in from the start. The data-depth regime (listed or private) is separate from access control.
Secrets are kept out of the code.
Keys are held outside version control. A pre-commit hook scans staged changes as a quick local check, and Gitleaks runs in CI on every pull request and on every push to main, checking the full history on main.
Trust that shows its work.
Data residency and analytical honesty come from the same rule: nothing is asserted beyond what the sources support.