Security and data
Your data, your rules.
How we handle data, access and AI in the systems we build. Clear boundaries, people in control, and nothing hidden.
Our practices
How we protect the systems we build.
Data boundaries first
What data a system may use, and what it may not, is agreed before anything is built.
Least access
Each system and person gets only the access their job needs, through roles you control.
People approve what matters
AI can prepare and recommend. Business-impacting actions wait for a named person to approve.
Secrets stay on the server
Credentials and keys are kept in server configuration, never in code shipped to browsers.
A record of every action
Agents record what they did and what needs a decision, so your team can review it.
Ownership in writing
Ownership of code and deliverables is set out in writing before work begins.
AI and your data
How an AI agent handles an action.
Every agent we build follows the same path. Your team stays in charge of business-impacting decisions.
- 1Reads only the information it has been given access to.
- 2Prepares the reply, record change or document.
- 3Requests approval where your rules require it.
- 4Acts only within the rules you set.
- 5Records the outcome for your team.
On this website
A project brief is sent by email to our inbox, checked on our server first and limited against repeated submissions. Email credentials never reach your browser. Full details are in our Privacy Policy.
Your project's requirements
If your business has specific security or regulatory requirements, tell us during discovery. We agree how they will be met, in writing, before the build begins.
Have a question about your data?
Ask us before you start. We will explain how your system would handle it.