Draft — not yet reviewed by a solicitor
The data flows described here were taken from the running system and are accurate. The legal language around them has not been reviewed by anyone qualified to review it, and this must not be relied on or published to customers until it has been.
Data processing agreement
Last updated 15 September 2026
This applies to every business with a CallPilot account and forms part of the terms of service. It covers personal data we handle on your behalf — what your callers and website visitors say to your agent, and what they tell it about themselves. It does not need signing separately; if your organisation requires a countersigned copy, ask and we will provide one.
1. Roles
You are the controller of your customers’ personal data. We are your processor and act only on your instructions. Your instructions are the configuration of your account — the agent’s script, what it is told to ask for, which integrations you switch on — together with anything you ask us in writing.
We are a separate controller for your own account data: the name and email of whoever signed up, and billing records. That is covered by the privacy policy, not by this agreement.
2. What we process, and why
| Category | Data subjects | Purpose |
|---|---|---|
| Conversation content | Your callers and website visitors | Answering them, and passing the transcript to you. |
| Contact details | Your callers and website visitors | Identifying a repeat caller, and letting you call back. |
| Booking and enquiry details | Your customers | Holding the appointment or enquiry you asked the agent to take. |
| Technical identifiers | Website visitors | Resuming a conversation, rate limiting, and abuse prevention. |
Processing lasts for as long as your account is open. We will not process for any other purpose, and will not use any of it to train models — ours or anyone else’s.
Nothing in the product asks for special category data. Your callers may volunteer it anyway — a caller ringing a dental practice will describe a symptom — so treat conversation content as capable of containing it and set your own retention accordingly.
3. Subprocessors
We use the following. Each is engaged under written terms imposing obligations equivalent to these.
- Twilio
- Carries the phone call, supplies the phone number, and sends text messages. The caller's number, the number they dialled, call times and duration, and the call audio in both directions while the call is live. If the business switches on call recording, the audio of each call, which Twilio keeps until it is deleted by an erasure, a deleted conversation or the business's retention period. For texts: the recipient's number and the message, which for a caller is their booking time and for the owner names the caller. Processed in: United States, with UK and Irish infrastructure for UK numbers.
- Resend
- Sends email alerts and the weekly summary to the business owner. The owner's email address and the alert itself, which names the caller and gives the number or email they left, what they asked about, and any booking time. Processed in: United States.
- Anthropic
- The model that decides what the agent says. The conversation so far, the passages retrieved from the business's own knowledge base, and anything the caller or visitor has said — which in practice includes names, numbers and addresses when they give them. Processed in: United States.
- Voyage AI
- Turns the business's website text, and each incoming question, into vectors so the right passage can be found. The text of the business's own pages, and the text of each question asked. Not the rest of the conversation. Processed in: United States.
- Stripe
- Takes the subscription payment from the business. The business's billing contact and card details, which are entered on Stripe's own pages and never touch our servers. No caller or visitor data. Processed in: United States and Ireland.
- OpenRouteronly if you enable it
- Routes to the premium voices a business can pay to use, and on to whichever vendor supplies the chosen voice. The sentences the agent is about to speak. Not what the caller said, and nothing identifying the caller. Processed in: United States, and wherever the chosen voice vendor operates.
- Calendlyonly if you enable it
- Only for businesses that connect Calendly: reads when they are already booked. A time range and the business's own Calendly user. Nothing about callers is sent. Processed in: United States.
- Shopify or WooCommerce (the business's own shop)only if you enable it
- Only for businesses that connect their shop: looks up an order a caller asks about. The order number the caller gives. The email or phone they give is compared with the order on our server and is not sent to the shop. Processed in: Wherever the business's shop is hosted.
Speech recognition and speech synthesis run on our own servers, using Vosk and Piper. Unless you enable an external transcriber or a premium voice, no call audio is disclosed to any third party other than the telephony carrier that is already carrying the call.
We will give thirty days’ notice before adding or replacing a subprocessor. If you object on reasonable data protection grounds within that period and we cannot resolve it, you may terminate without penalty and we will refund the unused part of your term.
4. International transfers
Our servers are in the United Kingdom. Several of the subprocessors above process in the United States, which means personal data leaves the UK in the ordinary course of answering a call. Those transfers rely on the UK International Data Transfer Addendum to the EU Standard Contractual Clauses, or on an adequacy decision where one covers the recipient.
To verify before relying on this: the transfer mechanism actually in place with each vendor named above needs confirming against their current terms, and a transfer risk assessment has not been done. A business in a regulated sector will ask for both.
5. Security
Data is encrypted in transit. Separation between customers is enforced by the database rather than by application code: every row carries the account it belongs to, the rule is applied by the database to every query including our own, and the credential the application runs under cannot disable it or read past it. A defect in our code is therefore not sufficient to expose your data to another customer.
Access to production is limited to named engineers and is not shared. Credentials are held outside the web root, readable only by the service account.
Not yet in place: encryption at rest beyond what the host provides, an audit log of staff access to customer data, and any third-party certification. If your procurement requires ISO 27001 or SOC 2, we do not have it.
6. Breach notification
If we become aware of a personal data breach affecting your data, we will tell you without undue delay and in any event within 48 hours, with what we know: what happened, which categories and roughly how many records, the likely consequences, and what we are doing. We will help you meet your own 72-hour deadline to the ICO. We will not notify your data subjects on your behalf without your instruction.
7. Your customers' requests
You can read everything held about any of your customers from your dashboard, which covers an access request without involving us. If a request reaches us directly we will not answer it; we will pass it to you within three working days.
Erasure you can also do yourself, and it is the fastest route. Erasing a contact deletes their details and every conversation with them, and strips their details from any calls — those are kept, without them, so your own billing stays correct. Appointments keep their slot in your diary and lose the name, so erasing somebody does not silently empty an afternoon. “Download their data” on the same record gives you everything held about that person as a machine-readable file, for an access or portability request.
Where you need something the dashboard cannot do — a correction, a bulk request, a whole-account export — ask and we will do it within thirty days at no charge.
8. Deletion and return
On termination we delete everything belonging to your account, including from backups as they age out, within ninety days — or sooner if you ask. Ask for an export before you close the account and we will provide your conversations, contacts and bookings as machine-readable files. A whole-account export is not self-service yet, so allow us a few days.
While the account is open you choose how long conversations are kept, from Settings: from 30 days to ten years, or everything. Conversations older than that are deleted automatically, the same way as pressing delete on one. Alerts and texts we send for you are kept only as a record that they were sent, and are deleted with the person they were about.
9. Audit
We will answer a reasonable written security questionnaire once a year. We do not currently hold a certification or a penetration test report to offer in place of one. On-site audit is available where a supervisory authority requires it, at your cost and on thirty days’ notice.
10. Your obligations
You are responsible for having a lawful basis for the processing you instruct, and for telling your own customers about it — your privacy policy should mention that calls are answered by an automated agent and written down. The agent gives a spoken notice at the start of every call; you can change its wording or, if you give notice another way, switch it off. Switching it off is your decision to justify.
You are also responsible for what you put in your agent’s knowledge base, and for not configuring it to collect more than you need.
Contact
privacy@callpilot.ai. We have not appointed a data protection officer, and on our current scale are not required to.