Always On It

Data processing agreement

This agreement is part of the Always On It customer terms. It covers the personal data of the people who ring you (your callers) when Sophie answers for you. If the terms and this agreement conflict about callers' data, this agreement wins.

1. Who this agreement is between

  • You: the business that signs up to Always On It. For your callers' personal data, you are the controller.
  • Us: Russell Utting, trading as Always On It (hello@always-on-it.co.uk). For your callers' personal data, we are your processor.

2. The processing

  • Subject matter: answering calls that you divert to your Always On It number, and passing each caller's message to you.
  • Duration: while you are a customer, plus the periods in section 10.
  • Nature: an AI voice assistant ("Sophie") answers the call, converts speech to text, asks questions, picks out the details below and writes a short summary. We send the message to you by email.
  • Purpose: only to let you call the caller back about their enquiry, and to check calls are handled properly (for example, that safety advice was given when needed). Nothing else.
  • People: anyone who rings your diverted number, usually members of the public, landlords, letting agents and other businesses wanting work done.
  • Data: the caller's phone number, and what they tell Sophie: name, the job, postcode and address, property type, access notes, urgency, the best time to call back, whether they're in your area, whether they're a returning customer, any safety concern, and a short summary. We don't record calls. A written transcript is kept for 30 days. The phone network keeps call records (number, time, length).
  • Special category data: we don't ask for it, but callers sometimes mention it (for example, a health condition in their access notes). We treat everything a caller says as confidential.

3. Your instructions

  • We process callers' data only on your documented instructions. The customer terms, this agreement and your settings (business name, hours, area, trade, where messages go) are those instructions. They include the transfers to the providers listed in section 7.
  • If the law makes us do something else, we'll tell you first, unless the law forbids that.
  • If we think an instruction breaks data protection law, we'll tell you.
  • We never use callers' data for our own purposes. We don't sell it, market to callers or ring them.

4. Your responsibilities as controller

  • You have a lawful basis for having your calls answered and your callers' details passed to you.
  • You tell your callers how their data is handled, through your own privacy notice. Sophie says she is an AI assistant at the start of every call.
  • Once a message reaches you, it's yours to look after: your inbox and phone are yours to secure.

5. Confidentiality

Everyone who handles callers' data for us is bound to keep it confidential. Today that is Russell Utting, and an AI agent that works on his behalf under his own accounts.

6. Security

We use appropriate technical and organisational measures, including:

  • the program that sends you messages checks a signature on every incoming call record and rejects anything unsigned;
  • it writes nothing about callers to any log;
  • access keys are kept in secure key stores, never in code;
  • two-factor sign-in on our accounts with our providers;
  • no call recordings, and callers' data kept only for the periods in section 10.

7. Sub-processors

  • You give us general written authorisation to use the providers below.
  • Changes: when one of them tells us it's adding or replacing a sub-processor, we email you. Our providers give us between 10 and 30 days' notice, so you may have as little as 10 days.
  • Objecting: you can object by email before the change takes effect, on reasonable data protection grounds. If we can't resolve it, you can cancel straight away and we refund any fees paid for the period after you leave.
  • Each provider is bound by data protection terms of the same kind as this agreement, and we stay responsible to you for what they do.
ProviderWhat it does for usData it handlesSafeguard for transfers outside the UK
ElevenLabsRuns Sophie: answers, speech to text, replies, picks out the details, keeps transcripts (no audio)Everything said on the call; the caller's numberUK Extension to the EU-US Data Privacy Framework; UK Addendum to the EU standard contractual clauses
TwilioProvides the phone number and carries the callThe caller's number; call times and lengthsUK Extension to the EU-US Data Privacy Framework; then Binding Corporate Rules or the UK International Data Transfer Agreement
CloudflareReceives each message and emails it to youMessage contents in transit; your settings and email addressUK Extension to the EU-US Data Privacy Framework; otherwise EU standard contractual clauses with the UK Addendum

Our payment provider (Stripe or GoCardless) takes your payments. It never sees callers' data, so it isn't a sub-processor under this agreement.

8. Helping you with callers' rights

  • If a caller asks us for a copy, correction or deletion of their data, we pass the request to you within 5 working days, and don't answer it ourselves unless you ask us to.
  • We help you answer, for example by finding or deleting a caller's transcript or call record. This help is free within reason.

9. Breaches and impact assessments

  • Breaches: we tell you without undue delay, and within 48 hours, after we become aware of a personal data breach affecting your callers, so you can meet your own 72-hour deadline to report to the ICO. We tell you what we know and add more as we find it.
  • Impact assessments: if you need a data protection impact assessment, or to consult the ICO, we give you the information we have about how the service works.

10. How long callers' data is kept, and the end of the service

  • Our message program (Cloudflare): keeps no caller details. It keeps only each call's reference number, for 30 days, so a message isn't sent twice.
  • Transcripts (ElevenLabs): 30 days, then deleted. No audio is recorded.
  • Call records (Twilio): kept by Twilio under its own terms. We can delete a caller's record when you ask.
  • The email to you: once delivered, it's in your inbox, and you decide how long to keep it.
  • At the end: when you leave, we delete the callers' data we control within 30 days, or return it first if you ask before you leave, unless the law requires us to keep it. Copies held by our providers, including backups, are deleted on their own timetables, which can take longer.

11. Information and audits

  • We give you the information you reasonably need to show this agreement is being kept.
  • You may audit us, or have an auditor do it, on 30 days' notice, at your cost, no more than once a year unless there has been a breach. For our providers, we rely on their own audit reports.

12. Liability

Each of us is liable under this agreement within the limits in the customer terms (clause 11), except where the law doesn't allow liability to be limited.

Last updated: 21 November 2026.