Version 1.1, 14 November 2026. Ring Verity is a sole trader business in the United Kingdom. Not legal advice; written to be reviewed by your adviser.
The customer (the plumber, salon, clinic) is the data controller for their callers' data: they decide why calls are answered and what is done with the bookings. Ring Verity is the data processor: we operate Verity on the customer's instructions and only for the purposes in the contract. Callers are the data subjects. This split is standard for answering services and CRMs and it is what the data processing agreement below records.
| Data | Where it comes from | Where it lives | Why |
|---|---|---|---|
| Caller's phone number | Caller ID from the network | The call record and the messages log | To text the confirmation, alert the owner, spot repeat spam |
| Call transcript (speech to text) | Speech recognition through Twilio (Deepgram), in the caller's language | The call record | To hold the conversation and let the owner read what was said |
| Booking details (name, postcode, job, time, site) | What the caller says | The call record and the bookings log | To book the job and text both sides |
| Vulnerability flag | Verity's judgement from the call | The call record | So the owner treats the caller with extra care; never used for anything else |
| Call recording | Twilio, only when the customer turns recording on | Twilio storage, with a link on the call record | Training and dispute resolution, only with the consent line played |
| Texts and photos | SMS/MMS from callers and the owner | The messages log (photo URLs are Twilio-hosted, auth-protected) | Two-way SMS, photos before a visit, owner instructions |
| Owner's mobile, hours, prices | The customer at setup and by text | The customer's account and availability records | To run the service |
| Deposit link | The business's own payment provider (Stripe, SumUp, Square or PayPal), set by the business | The payments log (link, amount and status only; no card data is ever seen by Ring Verity) | Texting the customer the business's own deposit link after a booking |
Not collected: date of birth, health details, ID numbers, card numbers. Verity's scripts tell Verity not to ask for them; a clinic persona takes "pain 1 to 10" as triage, not a medical record.
For the customer: performance of a contract (the caller rang to book a service) and legitimate interests (answering the phone, following up a quote, sending a review link once). Marketing texts beyond that (the 90-day win-back) rely on the soft opt-in under PECR reg. 22: existing customer, similar service, opt-out in every message ("reply STOP"). Recording relies on the consent line played at the start of every recorded call.
Call recordings kept 30 days, transcripts 12 months, adjustable per account. A nightly job wipes records older than those periods; the call's outcome, timing and score are kept as statistics with no personal data. Bookings the customer holds in their own calendar or sheet are the customer's records under their own retention. Deletion on request: any caller can be erased across every record by phone number within 72 hours, and the recording is deleted at Twilio at the same time.
| Sub-processor | What for | Data location |
|---|---|---|
| Twilio (Twilio Ireland Ltd) | Phone numbers, calls, SMS, recordings. Speech recognition (Deepgram) and Verity's voice (ElevenLabs) are provided through Twilio; both are listed as Twilio sub-processors. | EU/UK edge, US processing for speech; SCCs in Twilio's DPA. Recordings can be pinned to the Ireland region, set per account. |
| Anthropic (Claude API) | Generating Verity's replies from the transcript | US processing under Anthropic's DPA; zero data retention on API traffic by default; no training on customer data. |
| Supabase | Database and functions | London, UK (AWS eu-west-2). |
| Stripe | Ring Verity's own subscription billing only | Stripe's own controller role for card data; Ring Verity never receives card numbers. Customer deposits are paid through each business's own payment provider, never through Ring Verity. |
| Google (only if the customer links Calendar/Sheets, not live yet) | Writing bookings into the customer's own Google account | The customer's own Google account; tokens stored encrypted at rest in Supabase. |
Every webhook and every private page link carries a long random token (24 characters or more); a wrong one is refused. All tables have row-level security on with anonymous and authenticated roles revoked; only the server-side service role reads or writes. Secrets (Twilio, Anthropic, Stripe, Google) live in Supabase's encrypted secret store, never in code or chat. Recordings are only reachable through Twilio's authenticated URLs. Access to the database is limited to Ring Verity staff with two-factor on the Supabase account. Incidents: the customer is told within 48 hours of Ring Verity becoming aware, the ICO within 72 hours where required.
Played before the greeting whenever recording is on: "Calls may be recorded for training and quality." The customer can change the wording but not remove it while recording is on.
A caller (or their solicitor) asks for their data: the customer, as controller, tells Ring Verity the phone number. Ring Verity exports every record matching that number as caller, owner or recipient, plus any recording, as a JSON and MP3 bundle within 5 working days so the customer can respond within the statutory month. No charge.
Ring Verity must hold an ICO data protection fee registration (tier 1, £52/year for a small business) and list "telephone answering and appointment booking" among its processing purposes. Check the register at ico.org.uk/ESDWebPages/Search and add the purpose if it isn't there.
"Calls to this number may be answered by an AI receptionist provided by Ring Verity. Your number, what you say and your booking details are used to book your job and send you a confirmation by text, and are kept as set out in our retention periods: call recordings 30 days and transcripts 12 months. Calls are recorded only when you are told so at the start. You can ask us to delete your details at any time by texting this number."
Questions about this pack: hello@ringverity.co.uk.
A business can choose to link its Google Calendar so that each job Verity books appears there. Linking is optional and is done by the business itself, on Google's own permission screen. Calendar linking is being switched on account by account and is not yet available on every account.
Ring Verity's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.