Your accounts. Your data. Your say.
Handing an automation over the front door of your business is a real decision, and 92% of small business owners say they are worried about the risks. This page is the honest version of what we can and cannot see, what the law requires, and the one thing we will not sell you.
What we hold, and what we never hold
- No passwords, everEvery connection is authorised on the provider's own login screen.You click Allow on Google's, Microsoft's or Meta's page and we receive a scoped access token. We never see, store, or ask for a password. If anyone selling you automation asks for your email password, stop the conversation.
- Revocable in one clickFrom your own account settings, without asking us.Google, Microsoft and Meta all list connected apps in account settings with a Remove button. Removing ours stops the workflow immediately. We would rather you knew that up front than discovered it during a dispute.
- Your data stays in your accountsMessages in your inbox, calls in your phone system, bookings in your diary.The automation reads what it needs for a single message and writes the result back to your system. We do not maintain a copy of your customer database. The one exception is workflow logs, which we can see while you are on the Run plan so we can fix things, and which contain the decision trail rather than your customers' message history.
- Nothing is used to train anythingNot our models, not anyone else's.We use commercial API access to the underlying models, which is not used for training. Your price list, your tenant messages and your guest conversations are not material for anyone's model.
- You keep it if you leaveIt runs on your own accounts, so nothing switches off when you stop paying.The workflows live in your own automation account. Cancelling the Run plan ends our monitoring, tuning and updates. It does not end the service. We think that is the only fair way to sell something a business comes to depend on.
Three obligations we take seriously, and one we will not help you break
It says it is an AI
Every agent we build introduces itself as an AI assistant, says so plainly whenever anyone asks, and transfers to a person on request. Article 50 of the EU AI Act has required this of systems that interact with people since 2 August 2026, and it was not delayed by the later amendments. The UK has no equivalent statutory duty yet, but any client of yours taking calls from EU guests or tenants is plausibly in scope, and it is the honest default regardless.
Callers are told, first
Recording a call captures personal data, so it needs a lawful basis, a stated purpose, a retention period and a privacy notice, and the caller must be told at the start of the call. We set the announcement and the retention window with you during the build, and write both into your scope document rather than leaving them to chance.
No automated outbound marketing calls
UK regulations treat pre-recorded and automated marketing calls as requiring the recipient's prior specific consent. They are otherwise prohibited. Answering calls that come to your business is comfortable ground. Having an AI ring strangers to sell for you is not, and we will not build it, whatever a competitor tells you is possible.
This page is a plain-English summary of how we work, not legal advice. The Information Commissioner's Office publishes the authoritative guidance on call recording and marketing calls, and we will happily walk your own adviser through exactly what a workflow does before it goes live.
UK-based, on infrastructure you can name
We are a London business. The automation layer runs on your own account in a region you choose. The models we call are run by Anthropic and, where a client prefers it, OpenAI. Your phone line stays with your existing provider, with a forwarding rule added.
Every build comes with a written list of exactly which services touch your data and what each one does. If a supplier cannot give you that list on request, that is the answer to your question about them.
- The no-guessing rulePrices, dates, availability and policies come only from your data.If the fact is not in your sheet, calendar or system, the workflow does not answer it. It tells the customer a person will come back to them and sends you the thread with a suggested reply. This single rule is written into the instructions of every workflow we build, and it is the one we would never trade for a smoother demo.
- Two weeks of human reviewEvery reply comes to you before it goes to a customer.On every build, without exception, and for as long after the fortnight as you want it. We watch which drafts you edit and tighten the instructions the same day. Only once it is consistently clean do simple replies start going out on their own.
- Tested on your real messages firstAgainst last month's actual enquiries, before a customer ever sees it.You export a month of real messages or call logs. We run the workflow against every one and put its answer beside what your team actually sent. You see the whole comparison before go-live, including the ones it got wrong.
Next stepTwenty minutes on the phone. Then a straight answer.
Tell us what you keep doing by hand. We'll tell you which workflow pays back first, what it costs, and whether it's worth doing at all. If it isn't, we say so.