Security
Secure by design, proven by decision
The essentials before you sign up: where your data lives, who touches it, what An:des’ own code does and how a decision is proven.
- Certified infrastructureThe database and the servers with ISO/IEC 27001:2022 and SOC 2 Type II; the network with ISO 27001, 27018 and 27701. Certifications held by its suppliers, with source and date.
- One passkey per actThe confirmation the app asks for corresponds to the content you are looking at. Use your passkey and review the decision before confirming; the authority needed to act is checked separately. You confirm decision by decision, or within the five-minute window you open for a case.
- The proof of a decisionThe PoD (Proof of Decision) carries its SHA-256 fingerprint. When a person with authority asks, An:des seals it with RFC 3161 (FreeTSA); its fingerprints are checked without An:des and the seal, separately, with OpenSSL.
- What is sensitive, with An:des’ own codeReading, OCR and screening are done by An:des’ own code, hosted on Render and Supabase, without third-party OCR or analysis services. Only the fragments a query needs go to Érika’s model.
- Traces without contentTraces go to Langfuse with a closed list of metadata: no prompt, answer, document or identifier of a person, organisation or case.
- Your AI, with permissionsClaude via MCP and your code via the SDK come in with OAuth and a per-case delegation, with an end date and revocation.
- In-house code, reviewed and defendedWe review and defend our own code with frontier models, under their verified-access programmes for cyber defence: Anthropic’s Cyber Verification Program and OpenAI’s Daybreak.
Test drive
Access starts with a conversation
Tell us whether we take you for a co-driver lap with a demo or, better still, you drive with your data room in a one-to-five-day Bootcamp and leave with your compliance map: what is on record and what is missing.
Let’s talk about your BootcampAlready working with An:des?
Sign in with a passkey or with Apple