01How to read this register
A provider listed here does not receive every club record. The feature, selected fields and permissions determine what is sent. The groups explain who starts the sharing; they do not imply that a club can consent for every member or that every provider is legally a sub-processor.
A processor acts on instructions. An independent controller determines some purposes of its own, such as a bank’s fraud checks or a social platform’s operation. The club’s DPA applies to Ruckr’s sub-processing of club records; independent services also have their own terms and privacy notices.
02Providers needed to run Ruckr
Hosting, storage, sign-in and service email. Ruckr selects these providers; clubs instruct Ruckr about their club records. Some services process Ruckr’s own account and security data too.
Google Cloud and Firebase Hosting
- Purpose
- Run the API, database, service logs and websites
- Information shared
- Club records submitted to Ruckr, account identifiers, request and security logs; website requests include IP address and device/browser information
- Your choice and control
- Needed to provide the service; officers control club access and members can exercise their data rights
- Provider’s role
- Ruckr’s hosting processor, including sub-processing of club records; Google also handles its own service/account information under its terms
- Where it is handled
- The main API and database are configured in London, UK. Website delivery, support and operational service data can involve Google’s global infrastructure
Cloudflare R2
- Purpose
- Store uploaded photos, clips, documents, receipts and generated files
- Information shared
- The file and associated storage identifiers; a file may contain personal information supplied by its uploader
- Your choice and control
- Uploading and publishing are governed by club permissions; private and public files have different access rules
- Provider’s role
- Ruckr’s storage processor and a sub-processor of club uploads
- Where it is handled
- R2 object storage uses the EU jurisdiction endpoint. This does not mean every operational or support record is confined to that region
Firebase Authentication (Google)
- Purpose
- Create and secure sign-in sessions
- Information shared
- Email address, account ID, sign-in provider information, authentication factors and security/device information required for authentication
- Your choice and control
- Used when you create or use a Ruckr account; club records and the sign-in account have separate deletion processes
- Provider’s role
- Authentication processor for Ruckr’s account service
- Where it is handled
- Firebase Authentication processes data in the United States and uses Google’s service infrastructure; it is not covered by the London database location
Twilio SendGrid — service email
- Purpose
- Deliver invitations, account/service messages, enquiry confirmations and requested updates
- Information shared
- Recipient email, message content, delivery status and unsubscribe/suppression information; update-list contacts where you request updates
- Your choice and control
- Necessary service messages follow the action you take; optional marketing updates can be stopped separately
- Provider’s role
- Email processor for Ruckr and sub-processor where it delivers club instructions
- Where it is handled
- The configured global SendGrid service can process information in the United States and other countries used by Twilio’s providers
03Sharing a club enables
Payments, club email, social publishing and optional coaching tools. The club must explain its purpose, choose an appropriate lawful basis and obtain any required consent before using members’ information.
Stripe — Ruckr Pay
- Purpose
- Operate the club’s payment account and process cards, Direct Debit, wallets, refunds and disputes
- Information shared
- Club representative and verification details, bank/payment information, payer contact details, amounts, purchase references and fraud/security signals; Ruckr receives payment status and references rather than a complete card number
- Your choice and control
- An authorised officer connects the club account; a payer supplies payment information at checkout. Financial and verification records may have to remain after disconnection
- Provider’s role
- The club is merchant of record. Stripe’s role depends on the activity: it provides payment processing and also acts as an independent controller for matters such as fraud prevention and regulatory obligations
- Where it is handled
- Stripe’s international payment infrastructure, including the UK, EEA and US, as described in its privacy policy
Klarna
- Purpose
- Offer an optional pay-later method where enabled by the club and available to the payer
- Information shared
- Purchase amount and references, identity/contact and payment information needed to assess and service the payer’s agreement
- Your choice and control
- The club chooses whether to offer it; the payer separately chooses it and sees Klarna’s terms. Choosing a club membership does not itself authorise a credit agreement
- Provider’s role
- Klarna handles its own eligibility, credit, fraud and repayment decisions as an independent provider
- Where it is handled
- Klarna and its international service providers, under the notice shown for the payer’s country
Twilio SendGrid — club email
- Purpose
- Deliver club newsletters, event messages and permitted reports
- Information shared
- Selected recipients’ email addresses, the club’s message, delivery and unsubscribe information
- Your choice and control
- Authorised club senders select the message and audience. The club must distinguish necessary club administration from marketing and respect objections and opt-outs
- Provider’s role
- Ruckr’s delivery sub-processor; the club is responsible for the mailing purpose and recipient selection
- Where it is handled
- The configured global SendGrid service, including processing in the United States
Meta — Instagram publishing
- Purpose
- Publish a club-selected image, reel or story to its connected professional Instagram account
- Information shared
- Instagram account identifiers, an access token, chosen media and caption, publishing status and post identifiers. The connection does not import members’ personal Instagram accounts or their private messages
- Your choice and control
- A permitted officer connects or disconnects the account and chooses what to publish. Removing the connection does not delete posts already published on Instagram
- Provider’s role
- The club chooses the publication; Meta controls processing on its platform under its own terms. It is not simply a Ruckr hosting sub-processor
- Where it is handled
- Meta’s international services; temporary publishing media is made available from EU object storage
Google Vertex AI — optional drill and play drawing
- Purpose
- Turn a coach’s drill or play description into an editable diagram and suggested fields when the coach requests it
- Information shared
- The coach’s words and the drill or play fields already on the record (title or name, objective, player counts, space, equipment, coaching points, call, description and tags). The tool does not need names, contact details, medical information or safeguarding records; do not put them in the prompt or those fields
- Your choice and control
- Only a requested generation sends these fields. A coach can use the manual editor instead and must review the generated drawing and fields before using them. The creating coach is the author; their name is not sent
- Provider’s role
- A Google Cloud processing service. Google’s cloud terms restrict training without permission; safety/abuse monitoring may still retain prompts, so this is not a promise of zero retention
- Where it is handled
- The implementation defaults to Google’s europe-west1 endpoint in Belgium; a configured deployment can use a different supported region. Ask Ruckr to confirm the region for your deployment
Postcodes.io
- Purpose
- Look up coordinates for a UK venue postcode
- Information shared
- The postcode of the ground or venue; the lookup does not need a member list or a person’s live location
- Your choice and control
- Triggered when a club saves venue information without coordinates. Officers should use the venue address, not a private address without a reason
- Provider’s role
- External postcode lookup service; its own service logs are governed by its policy
- Where it is handled
- The Postcodes.io service; no country-specific hosting assurance is made here
04Connections a player or member chooses
Phone health data, notifications, wallets, calendars, directions and optional sign-in. A club subscription does not switch these permissions on for you. Device permission and agreement to a club’s use of data are separate choices.
Apple Health and Android Health Connect
- Purpose
- Read selected workout information from an adult member’s phone for optional sharing with their club
- Information shared
- Workout type, date, duration, distance where permitted and source identifiers used to synchronise records. This integration does not request an entire medical record or route/GPS history
- Your choice and control
- The member enables sharing in Ruckr and grants device permissions. Stop future sharing in the app or phone settings; use the removal control to remove imported workouts, as stopping permission alone does not erase prior copies
- Provider’s role
- Apple/Android provide the device health store; Ruckr processes the imported club records under the applicable club purpose. This reads selected data into Ruckr, rather than uploading a club medical record to a health store
- Where it is handled
- The phone’s health store and the user’s device/account settings; shared workout records are sent to Ruckr’s UK-hosted service
Apple Push Notification service and Firebase Cloud Messaging
- Purpose
- Deliver phone notifications and supported live match updates
- Information shared
- Device delivery token, notification text, routing identifiers and delivery information. Sensitive workflows use discreet notification text; device previews and ordinary club messages can still reveal information to someone looking at the screen
- Your choice and control
- You control phone permission and Ruckr notification preferences. Choose preview settings appropriate to a shared or locked phone
- Provider’s role
- Delivery services used by Ruckr; Apple and Google also administer their own device services
- Where it is handled
- Apple’s and Google’s global notification networks
Sign in with Apple or Google
- Purpose
- Use the identity provider you choose instead of a separate email sign-in
- Information shared
- A provider account identifier and the profile/name/email information the provider releases, including an Apple relay email if you choose to hide your email
- Your choice and control
- You choose this sign-in method and can manage its permissions in that provider account. Revoking it does not automatically delete club records
- Provider’s role
- Apple or Google controls its identity service; Ruckr uses the returned identity with Firebase Authentication
- Where it is handled
- The selected provider’s international account infrastructure
Apple Wallet and Google Wallet
- Purpose
- Save a club membership pass or ticket to the wallet you select
- Information shared
- The selected pass fields, which can include your display name, club, membership/pass status, expiry and verification code; device/pass identifiers support updates
- Your choice and control
- You request the pass and can remove it from the wallet. A copied pass or screenshot remains a copy and should be protected
- Provider’s role
- Apple and Google provide the wallet under their own terms; Ruckr issues and updates the selected club pass
- Where it is handled
- Your device and the selected wallet provider’s international infrastructure
Your calendar and maps providers
- Purpose
- Subscribe to a fixture calendar, export diary entries or open directions in Apple Maps, Google Maps or what3words
- Information shared
- Calendar event titles, times, venues and permitted event details; a directions link sends the destination. The provider may process your own location under your separate settings
- Your choice and control
- You choose the app/service and whether to subscribe. Keep private calendar feed links secret; stop or reset a feed and remove cached calendar copies when no longer needed
- Provider’s role
- Your selected provider handles its service under its own privacy terms, outside Ruckr’s control
- Where it is handled
- Your device and the infrastructure used by your selected provider
05Exports, public pages and other recipients
A club or member can choose to download or share information with a recipient they select, including an accountant, governing body, visiting club or photographer. Those recipients are not all Ruckr service providers. The sender is responsible for the lawful disclosure and the recipient’s handling must be assessed separately.
Publishing a club page, graphic, calendar or social post can disclose information to the public, search engines and people who copy it. A public link and a private authenticated record are different. Check the audience and any child/media restrictions before publishing.
06Optional AI and model training
Ruckr does not use club records to train its own AI models or sell those records for model training. Optional drill and play drawing sends the coach’s words and the blank fields of that drill or play to Google Vertex AI only when requested. Do not include people’s names, contact details, medical information or safeguarding material in those fields. This feature does not need membership lists, private messages or welfare records. Google’s cloud terms restrict training without permission, but safety and abuse monitoring may retain prompts; we do not promise zero retention. Coaches review the result and can use the manual editor instead.
07Providers and international processing
The provider register separates core service infrastructure, sharing enabled by a club, and connections chosen by an individual. It explains the data, purpose, choice and provider role for each. An optional connection does not give that provider general access to a club’s records.
The main application database and API are configured in London. Uploaded object files use EU storage. This is not a promise that all processing stays in the UK: authentication, email, payments, device services, optional integrations and provider support can involve other countries.
Restricted international transfers require an applicable adequacy arrangement or appropriate contractual safeguards, together with any necessary transfer assessment and supplementary measures. A provider’s country or a privacy-policy link is not, on its own, a transfer safeguard. Clubs can request information about the relevant arrangements from Ruckr, subject to protection of confidential security and contractual information.
08Changes, disconnection and retention
Ruckr maintains this register and gives club controllers notice of intended additions or replacements of sub-processors under the DPA, with a route to raise a reasonable data-protection objection. A new optional integration needs its own explanation before use; listing it does not authorise an unrelated purpose.
Disconnecting generally stops future requests through a connection, not records already lawfully held by a provider, a club, a payer or a recipient. Delete public posts at the destination where required, remove local exports and exercise rights with the relevant controller. Ask Ruckr if a feature’s disclosure or the provider list is unclear.