How we handle your data and AI.
This page sets out the commitments that govern every automation Turing Automate builds: what we connect, how we protect it, and what you own.
Five commitments, stated clearly
These aren’t aspirations: they’re how every project is scoped, built and handed over.
- 01
Your data stays yours
We use only the data a job needs. Before a connection is made, you see and approve every service that will receive or store it in a written data-flow map.
- 02
AI data use is agreed before the build
We do not use your content or customer data to train models. For each third-party AI provider, we record the account type, training-data controls and retention terms before you approve it.
- 03
You approve every connection and can revoke it
Every connection requires your approval. Access is scoped to the job in hand and you can revoke it at any time.
- 04
A human stays in control
You sign off each launch. Automations route uncertain or sensitive decisions to a person, so AI handles the busywork while your team keeps the judgement.
- 05
You own everything we build
Your automations, documentation and logins are yours. You can take over at any time with the complete system and a clean export.
What happens on a project
The commitments above, applied at each stage of a build.
Before a build
Every data flow is mapped and written down. You see which tools connect, what passes between them, and which AI provider handles each step, with its data terms explained clearly.
During the build
Access is granted by you and scoped to the work. We test against representative inputs and launch after you sign it off.
After handover
You keep the automations, documentation and logins. Revoke our access whenever you like. The system keeps working under your ownership.
The provider is a recorded project choice
The AI step is selected, tested and documented alongside every other system in the workflow.
Provider decision
We compare suitable commercial AI providers against the agreed examples, data terms, response time and usage cost. The scope names the provider and account type you are approving.
Documented boundary
The model call sits behind a documented input and output contract. Portability depends on the providers and response formats involved, so the handover states what would need to change and be retested.
Controlled change
We do not silently switch the provider handling your data. A proposed change is checked against the acceptance set, data terms and operating cost before it enters the live workflow.
UK GDPR, by default
Turing Automate is UK-based and handles personal data in line with UK GDPR: a lawful basis for processing, data minimisation, and your rights to access, correct or delete the data we hold. The full detail lives in our Privacy Policy.
Got a specific question about data or AI before you commit? That’s exactly the kind of thing we’d rather answer up front: get in touch or raise it when you ask for your free plan.
Get started
Automation you can track, then trust.
Tell us what you want to automate. You get a free plan and a fixed quote to approve before anything gets built.
Fixed price you approve firstYou own everything we buildPause or cancel anytime