Draft. This hasn't been reviewed by a solicitor yet and isn't final.
Version 2026-11-02
These are the sub-processors PBd uses. We will give coaches notice before adding or replacing one, so you can object.
What for: Database, sign-in and file storage.
Data involved: Everything held in the platform: accounts, programmes, messages, check-ins, progress photos, bookings.
Where: Region to be confirmed in the Supabase project (the UK or EU is intended).
What for: Hosting and running the application.
Data involved: Requests and responses as they pass through, and server logs.
Where: London (lhr1) for the application's functions.
What for: Taking payments into each coach's own Stripe account.
Data involved: Names, emails and payment details of people who pay. Stripe is also a controller in its own right for its legal duties.
Where: As set out in Stripe's own terms.
What for: Sending emails (confirmations, reminders, messages in a coach's name).
Data involved: Names, email addresses and the content of the emails.
Where: As set out in Resend's data processing terms.
What for: AI drafting features, only when a coach uses them.
Data involved: What the coach types into the AI feature and the programme or message text it works on. When a coach adapts a programme or drafts a next block for one client: that client's training records and, only if the client has separately agreed, their goals and injury information, never their name or contact details. Never sent without the coach asking.
Where: As set out in Anthropic's commercial terms (no training on this data).
What for: Hosting and streaming coaches' videos.
Data involved: Videos a coach uploads.
Where: As set out in Bunny's data processing terms.
What for: Connected devices, only when a client connects their own Oura account.
Data involved: We read the client's daily steps and sleep totals from Oura. Oura's sign-in tokens are stored encrypted and deleted when the client disconnects.
Where: As set out in Oura's terms.
What for: Connected devices, only when a client connects their own Withings account.
Data involved: We read the client's daily steps and sleep totals from Withings. Withings' sign-in tokens are stored encrypted and deleted when the client disconnects.
Where: As set out in Withings' terms.
What for: Looking up packaged products by barcode when a client scans one.
Data involved: Only the barcode number, sent from our servers. Nothing about the client or the camera image.
Where: As set out in Open Food Facts' terms.
What for: Push notifications to the native app, once one exists.
Data involved: A device identifier and the text of the notification.
Where: As set out in OneSignal's terms.
What for: Delivering web push notifications a person has turned on in their browser or installed web app.
Data involved: An address for the device and the encrypted text of the notification.
Where: As set out in each company's terms.