01Your data stays yours
Agents run inside your boundary, your data is never pooled with other clients and never fed into public model training.
AI your board can sign off on
Capabilities
Everything included, nothing bolted on after the fact.
- No training on your data
- NZ data residency
- Role based, least privilege access
- Full agent action audit logs
- Encryption in transit and at rest
- Scoped, rotatable keys and secrets
- Human in the loop on sensitive steps
- Privacy Act 2020 aware handling
Every build starts with a fixed-scope conversation, no surprise line items after the fact.
The build itself, not a proof of concept.
02Tight, scoped access
Least privilege service accounts and scoped keys, so every agent can only reach the systems and data it genuinely needs.
03A full audit trail
Every action recorded with who, what and when, so you can review, explain and prove exactly what the agent did.
04Local privacy aware
Data residency where you need it, encryption in transit and at rest, and handling that respects the Privacy Act 2020.
FAQ
Agents run inside your boundary with least privilege service accounts, every action logged with who, what and when, and handling that respects the Privacy Act 2020.
No. Your data stays in your environment, is never pooled with other clients, and is never fed into public model training.
You do not need one to get started, but the setup is built to the standard a NZ or AU board expects to approve, so your security and compliance people can review it if you have them.
A human stays in the loop on sensitive steps, access is scoped tight to least privilege, and every action is recorded in a full audit trail you can review and explain.
Interested in solving your problems with security & compliance?
Tell us what you are trying to do and we will reply with how we would build it, no obligation.
You get the upside of AI without handing over control, in a system your security and compliance people can review, approve and stand behind.
Let’s talkWas this helpful?
Thanks, that helps.