Subprocessors
The outside services that store or handle club data for Raliera, what each one holds, and where it runs.
Last updated . This list is updated when a service is added or removed.
The services
| Service | Used for | What it holds | Where |
|---|---|---|---|
| Render | Hosting | The Raliera app and its database: clubs, members, bookings, programs and payment records. | Oregon, United States |
| Supabase | Sign-in | The email address and sign-in details it checks when someone signs in to Raliera by email code or password. Not club records. | Oregon, United States |
| Stripe | Card payments | Card numbers and saved cards. Card numbers go to Stripe, not to Raliera, and a club’s charges and saved cards sit in the club’s own Stripe account. | Being confirmed with the provider |
| Resend | Account email | The emails Raliera sends for a club: sign-in codes, receipts, invites and alerts. | Being confirmed with the provider |
| Amazon Web Services (Amazon SES) | Club email campaigns | The emails a club writes to its members from the club’s own domain, and which ones were delivered or bounced. | Ohio, United States |
| Telnyx | Texting and phone | A club’s texts with its members, and for clubs that use its phone line and AI receptionist, their call summaries and transcripts. | Being confirmed with the provider |
| Cloudflare | Sign-in protection | The visitor’s browser and network details, to check that a sign-in or a form comes from a person, not a bot. Not club records. | Being confirmed with the provider |
-
Questions.
For a data processing addendum or a security questionnaire, email [email protected]. Questions about a member’s data go to [email protected].