In your own cloud account
Most systems we build run in your cloud account, under your logins and billing. You can see everything that is running and switch it off at any time.
Where it lives, who can see it, and what you keep at the end.
We fit the system to where your data already is, rather than moving it somewhere new.
Most systems we build run in your cloud account, under your logins and billing. You can see everything that is running and switch it off at any time.
Where data should not leave the building, we can run the system on-premise or on a local device, including models that run inside your network.
If a quick pilot is easier to run on our side first, we agree that in writing, keep it separate from other clients, and move it to your environment at handover.
We ask for the narrowest access that lets the workflow run, start with read-only where we can, and give access back when the engagement ends.
We do not use client data to train or fine-tune models we reuse elsewhere. Where a hosted AI provider is involved, we use business terms with training turned off.
We sign an NDA on request before we see anything sensitive, and we never name clients publicly without their permission.
The code, configuration and documentation are yours. At handover you get the repositories, credentials and a written guide, so there is no vendor lock-in.
None of this is unusual. What matters is doing it consistently, including on small projects where it is tempting to skip a step.
Only what the workflow needs. We map this together at the start and use sample or anonymised data for early work wherever possible.
Often, yes. We tell you which provider would process which data before anything is sent, and use business terms with training turned off. If that is not acceptable, we use models that run inside your own environment instead.
We keep it to a minimum. Personal details are left out of AI prompts unless the task needs them, masked where possible, and handled under a written agreement covering purpose, retention and deletion.
Yes. We can set up hosting and AI models in the region you need, or run everything on your own servers.
Not at present. We are a small team, so we describe our practices plainly instead. We work inside your environment and controls, fill in security questionnaires honestly, and say clearly which controls are ours and which are yours.
We hand over the code, documentation and credentials, remove our access, and delete any copies of your data we hold, then confirm this in writing.
Email [email protected] with “security” in the subject line. We reply within one business day and agree any disclosure timeline with you before anything is published.
Send us your security questionnaire. We fill it in completely and mark anything we cannot show evidence for as not in place, rather than giving an optimistic answer.
An AI Opportunity Audit covers where your data lives and what can and cannot leave your environment, before anything is built.