Sub-processors
Last updated: October 2026
Where you are the controller of your staff and client data, we are your processor, and these are the companies we use to deliver the service. Every one of them is named here with what it actually does and what data reaches it.
| Sub-processor | What it does | Data it receives | Where |
|---|---|---|---|
| Supabase | Application database, authentication, file storage and server functions | All customer data: staff records, client records, rota, care notes, documents | United Kingdom (London) |
| Cloudflare | Hosting and content delivery for the website, web app and admin console | Request metadata (IP address, user agent) in transit; no customer records stored | Global edge; United Kingdom origin |
| Postmark (ActiveCampaign) | Transactional email: demo enquiries and account email | Name, work email, organisation, message content | USA (UK GDPR safeguards via the provider’s DPA) |
| Stripe | Subscription billing for the provider’s own account with us | Billing contact and payment details of the care provider; no care data | USA / EU |
| Expo (Expo Application Services) | Delivery of push notifications to the carer mobile app | Device push token, notification title and body. The body carries a client’s INITIALS and the shift time, never their name; a coordinator’s free-text note is passed through as typed. | USA |
| Sentry | Error and crash reporting from the mobile app | Diagnostic data: stack traces, device model, OS version, user id | USA / EU |
| OpenStreetMap (OpenStreetMap Foundation) | Address search (the Nominatim service) and map tiles for the map on a client or staff record in the web app | When a manager presses “Find their address on the map”: the address as typed, with no name attached, plus the browser’s IP address. Showing the map requests the tiles for the area on screen. | Global (the Foundation’s servers and its content delivery network) |
| Apple, Google | App distribution, and the push networks behind Expo (APNs, FCM) | Device push token, notification title and body: the same body Expo receives, so initials and shift time rather than a client’s name | Global |
What does not leave the platform
Care notes, medication detail, safeguarding records and staff pay data are held in the application database and are not sent to any other company on this list. Addresses are the exception worth naming: an address typed into a client or staff record goes to OpenStreetMap, with no name attached, when a manager asks the map to find it. No customer record is sent to an analytics provider, an advertising network or an AI service. The matching engine that ranks carers for a shift runs inside the database and no data leaves it to do that work.
Changes
We will update this page before a new sub-processor starts handling customer data, and we will email the billing contact of each organisation when we do. If you object to a new sub-processor, tell us; the process for that is in the data processing agreement.
Questions
Ask at hello@oncallcare.co.uk. If you need a signed data processing agreement or a completed supplier questionnaire, ask for that too. See also security and compliance and our DPIA pack.