Ravini is a data processor acting on your instructions (Terms section 8.1). To deliver the Service we use the sub-processors below. Each entry was compiled from the application source code: every one is a service the platform actually sends data to, not a list of accounts we hold.
We will notify you before adding or replacing a sub-processor that handles your members' personal data, as set out in Terms section 8.5.
Each of these receives identifiable information about your members or leads.
Supabase
Primary database and file storage
All platform data: member records, bookings, memberships, messages, uploaded photos and documents
Processing location: London (eu-west-2)
Twilio
SMS, WhatsApp and voice
Member and lead phone numbers, the full text of every SMS and WhatsApp message sent and received, and call recordings
Processing location: United States (see section 3)
Mailgun
Transactional and campaign email
Member and lead email addresses, names, and the full content of emails sent
Processing location: EU
Anthropic
AI assistant (Claude)
The text of member and lead conversations, names, and the conversation history used to generate replies
Processing location: United States / vendor-managed
OpenAI
AI features and call transcription
Audio recordings of sales calls, the resulting transcripts, and text from members and leads passed to classification and drafting features
Processing location: United States / vendor-managed
ElevenLabs
Spoken AI replies (text to speech)
The text of each AI reply that is read aloud: Atlas replies spoken to your staff, and AI Coach replies spoken to your members. That text can include member names and details from the reply
Processing location: United States / vendor-managed
Stripe
Card payments
Member name, email, billing address and payment method. Card numbers are entered directly into Stripe and never reach Ravini's servers
Processing location: United States / EU, vendor-managed
GoCardless
Direct Debit
Member name, email and bank mandate details, collected through GoCardless's own hosted pages
Processing location: UK / EU
Google (Firebase Cloud Messaging)
Mobile push notifications
Device tokens and the text of each notification, which commonly includes class names and booking status
Processing location: Google-managed
Google (Gemini)
AI content generation
Content-generation prompts, primarily gym-authored marketing copy rather than member conversations
Processing location: Google-managed
Meta (Facebook / Instagram)
Lead messaging and ad attribution
For the DM channel, the text of lead messages and Meta's recipient identifier. For ad attribution, email and phone hashed before sending, plus event metadata
Processing location: Meta-managed
Resend
Transactional email (secondary paths)
Recipient email address and message content, for a narrower set of emails than Mailgun, such as account-deletion confirmations
Processing location: Vendor-managed
InBody (LookinBody Web)
Body-composition device integration
Body-composition measurements including weight, body-fat percentage and muscle mass, linked to a member. See section 4
Processing location: EU region
GoHighLevel
CRM relay, only if you connect your own account
Lead phone numbers and SMS content
Processing location: Vendor-managed
Xero
Accounting, only if you connect your own account
Invoice and contact records you choose to sync
SendGrid
Internal Ravini business reporting
An internal weekly summary sent only to Ravini staff addresses, containing account-level business metrics
These support the Service without being sent member records deliberately.
Our primary database is hosted in London (eu-west-2). Member records, bookings and message history live there. Email is sent through Mailgun's EU region.
Two flows leave the UK and EEA, and you should know about them specifically:
Where personal data is transferred outside the UK, those transfers rely on the safeguards in the relevant vendor's published data processing terms, which in most cases means the UK Addendum to the EU Standard Contractual Clauses. We are working through each vendor to confirm and record the specific mechanism in place, and this page will name it per vendor once that is done.
AI providers receive whatever a member writes. Our AI assistant answers inbound messages, so the member's message is sent to the AI provider as written. Members sometimes volunteer health or financial information unprompted. We do not ask for it, we do not store it as structured health data from this route, and we do not redact it before the message is processed. If your members' messages must not reach a third-party AI provider, the AI assistant can be disabled for your organisation.
InBody is primarily a source we read from rather than a party we send member records to: Ravini authenticates to InBody to retrieve scans your members have taken on your device. It is listed here because body-composition data is health data and the integration is member-linked.
Email sam@ravini.co.uk with any question about this list, or to object to a new sub-processor.