Home / Trust & security
How we protect your data and your operations.
Plain answers for your IT, legal and procurement teams.
Draft policy. To be confirmed before launch.
- Where your data livesIn the UK or EU by default; another region where your law requires it; a data processing agreement with every client.
- Who holds the keysDuring the build, our secured accounts, with your project walled off from every other client. At handover, everything moves into accounts in your name, and our access is yours to revoke.
- How code is checkedHuman review of every change, automated security scanning, dependency updates and tested backups.
- Each client kept separateEach organisation’s data is walled off at the database level.
- Our use of AIWhich providers we use, what they see and how long they keep it, listed per project. Your data is never used to train models.
- ContinuityRunbooks and documentation, so another engineer can step in using access you control.
- Concerns and complaintsEmail [email protected]. A senior member of the team reviews every concern and replies within two working days.
Ownership and security, answered
Who owns the code?
You do, stage by stage. The work in each stage becomes yours as soon as that stage is paid. At handover we move the code, hosting and domains into accounts in your name, with the documentation and runbooks needed to run it without us.
Do you use AI to write code?
Yes, for routine work, because it’s faster. A person reviews every change before it’s merged, automated scans check for security flaws, and tests and documentation ship with each milestone.
Where is our data stored?
In the UK or EU by default, or another region if your law or regulator requires it, under a data processing agreement.
Will you sign our NDA or supplier agreement?
In most cases, yes. Send it before the first call and we’ll return it promptly or flag any clause we need to discuss.