What we won't claim
We do not hold SOC 2, ISO 27001, HIPAA, PCI, or Cyber Essentials certification, and we won't imply otherwise. If a page, a proposal, or a salesperson ever tells you differently, that's wrong and we want to know about it. Plenty of vendors treat a compliance badge as a shortcut past this conversation. We'd rather have the conversation — walk through exactly what a given build touches, what controls sit around it, and what your own compliance program still needs to cover. For businesses in a regulated space, our AI security checklist is a useful starting point before that call, because it lays out the questions worth asking any vendor, us included.
The principles every build follows
Regardless of certification status, every system we build is designed against the same working principles:
- Least privilege. An agent gets scoped credentials for exactly the systems and actions its job requires — never an admin account "to keep things simple." If a workflow only needs to read a calendar, it gets read access to that calendar and nothing else.
- Data minimisation. A system is given the data it needs to do its job and no more. We push back on requests to pipe in a whole database when a workflow only ever touches a handful of fields.
- Audit logging. Every consequential action an agent takes is logged in enough detail that you can reconstruct, months later, exactly why it did what it did. "The agent decided" is never an acceptable answer to "why did this happen" — the logs have to back it up.
- Human approval gates. Actions that carry real consequence — refunds, contract changes, anything touching money or an external customer relationship — sit behind an explicit approval step rather than running unattended, until you've seen enough of the system's behaviour to trust it further.
- Data staying where it needs to stay. Where an engagement calls for it, client data stays inside the client's own environment rather than moving into ours. We design the integration around that constraint instead of asking you to relax it for our convenience.
These are design defaults, not a menu — but the exact configuration is always scoped to your engagement, your systems, and your risk tolerance, which is part of what gets agreed before any build work starts.
Supporting your compliance obligations, not replacing them
If your business operates under HIPAA, GDPR, PCI, or an industry-specific regulatory regime, that obligation is yours and stays yours. We don't position anything we build as a substitute for your compliance program, and we won't tell you a system is "compliant" as a marketing shorthand — compliance is a property of your whole operation, not of one vendor's code. What we do is build inside the constraints your program sets: the access controls, the logging, the data-handling rules your compliance or legal team requires, engineered into the system rather than bolted on after the fact.
We also won't lock you into a specific model provider or cloud platform as a guarantee baked into the architecture. Which underlying services a build uses is a decision made with your security team, against your existing vendor agreements and risk appetite, not decided for you in advance.
Reviewing the architecture before anything is built
Any custom AI agent or automation we design can be reviewed by your security team before a line of production code is written. That means walking through the data flow, the access boundaries, the logging, and the failure modes on a call, and answering a security questionnaire directly rather than sending back a generic vendor packet. If your review surfaces a requirement we hadn't scoped for, we'd rather find that out at the design stage than after launch — it's cheaper for both of us and it's how the pricing for the engagement stays accurate.
What this looks like in practice
A support agent we build to handle refund requests, for example, gets read access to order history and a scoped, single-purpose credential to draft (not send) refund actions. Sending is gated behind a person's approval until the agent has a track record. Every lookup and every drafted action is logged against the ticket it came from. None of that requires a certificate — it requires the system to be built that way from the start, and for us to be able to show you exactly how, system by system, when you ask. The same approach applies across the different systems we build, whether that's a single agent or a broader automation touching several parts of your business.