The AI AdoptionFree AI pre-audit Security & data handling
How we handle your systems and your information while we work together, set out plainly.
The working system is delivered into your own accounts and tools. We keep reusable build infrastructure, not client data, in our shared automation library. Any client-specific files or examples stay in a separate client workspace and are never reused for another business.
You hold and pay for the Claude or OpenAI account selected for the work. We build inside that environment, so the delivered workflows and custom business apps & tools run on an account that belongs to you.
We ask for the least access the agreed workflow needs. Your source systems stay read-only by default. If a workflow later needs to write something back, the exact action, scope and human approval gate are agreed before that access is enabled.
We build and dry-run in a separate sandbox. A final test in your real environment happens only after the workflow passes the agreed checks, and the manual process stays in place until you accept the result.
We sign an NDA before collecting your operational or financial figures. We only ask for the examples and access needed to map, test and verify the agreed workflow.
Training happens in your own accounts, on the person's real work. We do not take copies of your documents or data away with us, and what we see in a session sits under the same NDA as the rest. What we keep is the teaching itself, written so it carries no trace of your business. A session is recorded only if the person agrees to it.
Every build has a written spec, and you sign acceptance against it before anything goes live. Irreversible actions keep a human approval gate.