- Hosting and residency
- Microsoft Azure, UK South. Compute, database, key management, logs and AI all stay in the UK. The only global component is Microsoft Entra ID, used for sign-in.
- Encryption
- TLS for every connection, with a minimum of TLS 1.2. Encryption at rest on all storage.
- Separation between customers
- Each organisation's data is isolated by row-level security enforced inside the database, with a default of deny. Isolation tests run on every code change.
- Sign-in
- Through your own Microsoft 365 / Entra ID, so there is no separate password store for your users. Roles are checked on the server for every request.
- AI
- Azure OpenAI in a UK South deployment, reached over a private connection. Your data is not used to train any model. AI only proposes; a person in your organisation approves, and the approved result runs deterministically.
- Audit trail
- Every configuration change, approval, key operation, exchange step and denied access goes into an append-only audit log. Every produced value records the source field and transformation it came from.
- Outbound connections
- All traffic to your systems leaves from one fixed IP address, so you can allow-list us. Connections are HTTPS only, to public addresses, with no redirects followed.
- Retention and exit
- Retention periods are agreed per customer in the data processing agreement. On termination your data is exported if you ask, then deleted within 30 days.
- Backups
- Automated database backups with point-in-time restore. Longer retention, geographic redundancy and a tested restore drill are part of the production build before pilots.