Security & data handling
Your accounts.
Clear boundaries.
A useful AI workflow needs more than a connection between apps. Before implementation, we agree what information it can use, what it can do and who checks the result.
These are the practical decisions we work through with you. The specific access, responsibilities and support arrangements belong in your agreed project scope.
01 / Accounts & access
Keep ownership.
Your business keeps its accounts and subscriptions. We agree the access needed for the task, use the narrowest suitable permissions available and identify who can approve changes.
Do not send passwords or API keys through the enquiry form. Any required access should use an agreed account invitation or appropriate credential-sharing method.
02 / Approved information
Choose the sources.
Agree which documents, records and fields the workflow may use, and who is responsible for keeping them current. Start with sample or de-identified information where practical.
Discuss sensitive information and any handling requirements before it is connected. Access to one source does not mean permission to use everything in an account.
03 / Third-party tools
Check the plan.
AI tools, hosting and connected apps have their own terms and data settings. Available controls depend on the provider and your subscription.
We review the relevant settings and limitations when scoping the workflow, including data use and retention. A basic setup does not include enterprise-only controls or guarantees from a provider.
04 / Actions & review
Name the reviewer.
Drafts and proposed changes are the starting point. Agree which outputs need checking, who approves external actions and what happens when information is missing or a step fails.
Sending messages, updating records or taking other external actions requires suitable permissions, an agreed approval policy and testing within the project scope.
05 / Retention & handover
Plan the finish.
Agree what working data and records are kept, where they live, who can access them and when they should be removed. Provider retention limits need to be considered separately.
At handover or offboarding, agree how instructions are transferred, access is removed and scheduled work is stopped or reassigned. Ongoing monitoring and support are included only when explicitly scoped.
06 / Your first enquiry
Start with an outline.
A broad description of the task is enough. Leave out credentials, private client records and sensitive personal information.
The enquiry form prepares a draft locally and opens it in your email app. You choose whether to send it. The website does not submit the enquiry to a delivery service, confirm receipt or create a booking. Copy and download options are available if your email app does not open.
Read enquiry privacy detailsA clear starting point
Talk through the boundaries.
Tell us what you want the workflow to do and which tools are involved. We can discuss access, review and handover before deciding on a setup.
Discuss your workflow