Security and governance
Serious about the information, and plain about the state of things.
Aiderra OS is built for organisations that handle sensitive business and care-related information. This page describes the controls that exist in the product today, where your data is held, and what we have not yet done. It does not describe a roadmap as if it were the present.
Tenant isolation
Each organisation's data is separated in the database, not just in the code.
Every table that holds workspace data carries a row-level security policy. Work done on behalf of a workspace runs on a restricted database role that can only see that workspace's rows. A boot-time check verifies the binding and reports any table without a policy.
Row-level security
Postgres policies keyed on the workspace bound to the request. A query without a workspace sees nothing.
A restricted role for tenant work
Requests, calls and events run as a role that is subject to those policies. Maintenance runs separately and is named as such.
Checked at every start
The tenancy doctor proves the binding reaches the database and lists any uncovered table. It reports ENFORCED or it does not.
Access control
Roles, second factors and rate limits.
Roles per workspace
Owner, operations lead, finance approver and others. Owner-only actions, such as changing the email identity or buying a phone number, are enforced on the server.
Two-factor authentication
Time-based one-time codes from an authenticator app. A deployment can require it for every account that can act on the business.
Passwords and sessions
Passwords are hashed with scrypt and never stored. Sign-in, sign-up and code entry are rate-limited by address.
Audit trail
Append-only, hash-chained, verifiable.
Every action and every decision is written to the audit log with the actor, the time, and the state before and after. Each entry stores a SHA-256 hash of the previous entry and its own contents. Editing or removing one breaks the chain, and the Audit Trail screen can verify any day on demand.
- What the AI proposed and what a person changed
- Who approved, sent back or rejected, and why
- Field-level redactions recorded without breaking the chain
- Verification from the screen or over the API
7f3a…c91e
b02d…41aa
e6c0…9d27
1a9f…70b3
c4e8…2f05
Human governance
The controls that keep a person in charge.
Approval gates in every workflow
Outward-facing actions stop for a person. The gate is part of the workflow definition, not a toggle an agent can reach.
Pause at every level
An agent, a department or the whole workforce. Pausing is immediate and in-flight work resumes only when you say.
Scoped tools
Each agent can call only the tools its department is allowed. A tool call outside that list is refused and recorded.
Data
Where it is, how it is protected, who else touches it.
Hosting
Workspace data is held in a managed Postgres database in London (AWS eu-west-2). The application that processes it runs on Railway in Amsterdam, in the EU. The AI, telephony and email providers operate outside the UK and the EU; the privacy policy names each one with the transfer safeguard that applies. If every processor must sit inside the UK for your organisation, tell us before you start.
Encryption
Connections use TLS. Credentials you connect for your website, social accounts and phone are encrypted at rest with AES-256-GCM under a key held only by the deployment. Webhooks from Twilio, Resend, Stripe and GitHub are signature-verified before they are trusted.
Sub-processors
The services Aiderra OS calls are listed by name in the privacy policy: database and application hosting, email delivery, telephony, the language and voice models, calendar, and the public registers Sales reads. Nothing is sent to a model that a person has not put into the workspace.
Your rights and your data
Your data stays yours. Access, correction, erasure and export requests are handled as the privacy policy describes. Financial records are kept for the six years UK law requires.
Certifications
What we do not yet hold.
Aiderra does not currently hold ISO 27001, Cyber Essentials or SOC 2 certification, and this page does not claim GDPR compliance as a badge. The controls above are what exist in the product. We would rather you knew that than found out.
If your procurement process needs a completed security questionnaire, a data-processing agreement or a conversation with the people who built this, ask.
Questions a DPO would ask? Ask them.
We will answer plainly, including when the answer is not yet.