Version 1.0, 18 September 2026. Ring Janine is a trading name of Cinco Recycling Limited, company number 13964443, 85 Great Portland Street, London W1W 7LT. 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 Janine is the data processor: we operate Janine 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) | Twilio speech recognition, 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 | Janine'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 |
| Payment link | Stripe Checkout | The payments log (link and status only; no card data is ever seen by Ring Janine) | Deposits |
Not collected: date of birth, health details, ID numbers, card numbers. Janine's scripts tell her 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.
Default 90 days, set per customer. A nightly job wipes transcripts, captured details and recording links older than that; the call's outcome, timing and score are kept as statistics with no personal data. Bookings that went to the customer's own calendar or sheet are then 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, speech recognition, SMS, recordings | 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 Janine'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 | Project region to be confirmed and stated here (EU West if available). |
| Stripe | Payment links | Stripe's own controller role for card data; Ring Janine never receives card numbers. |
| Google (only if the customer links Calendar/Sheets) | Writing bookings into the customer's own Google account | The customer's own Google account; tokens stored encrypted at rest in Supabase. |
Action before launch: confirm the Supabase region and pin Twilio recordings to Ireland, then fill in the two "to be confirmed" cells.
Every webhook and dashboard link carries a random 36-character token; a wrong token gets a 403. 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 Janine staff with two-factor on the Supabase account. Incidents: the customer is told within 48 hours of Ring Janine 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 Janine the phone number. Ring Janine 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.
Cinco Recycling Limited must hold an ICO data protection fee registration covering the Ring Janine service (tier 1, £52/year for a small company) 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 Janine. 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 for 90 days. 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: [email protected] or ring 07360 266999.