Sub-processors
ClubShack stores clubs’ information on Google Cloud in London. These are the companies that handle any of it for us, what each one handles, and where.
| Company | What for | What it handles | Where |
|---|---|---|---|
| Google (Google Cloud and Firebase) | The database, files, server code, sign-in, app checks, crash reports and this website | Everything stored in the app; sign-in emails and passwords (stored only as secure hashes); crash reports from the phone apps (the error type and where it happened, phone model and a random installation number, nothing personal) | London (europe-west2) for club data and files. Firebase sign-in and crash reports are run from Google’s global infrastructure, including the US |
| Mailgun (Sinch) | Sending emails: notices, renewal reminders, receipts, invites and account emails | Recipients’ names and email addresses and the message | EU region |
| Apple and Google | Delivering notifications to phones | A device token and the notification’s title and short text | Their global push services |
| Cloudflare | The clubshack.app domain and its DNS | No member information (it doesn’t carry the app’s traffic) | Global |
What doesn’t handle member information
GitHub (GitHub Actions) and Codemagic build the app from its source code. They never receive member information.
Changes
We update this page before adding or changing a company that handles club information, and tell club owners in the app. A club that objects can talk to us, or export its records and leave.
Questions: hello@clubshack.app.