Privacy Notice
Version 2026-10-19 · Planned effective date October 19, 2026
1. Who is responsible
Kaizen Brands LLC operates Club Hub and is the personal information controller for the data described here, under the Philippine Data Privacy Act of 2012 (Republic Act No. 10173). For any privacy question or request, contact hello@clubhub.ph.
2. What we collect
- Players: your name, email and mobile number; your account details if you sign up (directly or with Google); your bookings, payments, refunds and receipts. When you confirm details about a venue or answer a question about it, we store your answer with your account. Public pages show only how many players agreed and when. If you add a photo of a venue, we store it with your account. Club Hub checks each photo before it appears on the venue page, where it shows as “From a player” without your name. Club Hub removes the photo’s location and camera details when it is uploaded. Please don’t share photos in which other people can be recognised.
- Payments: the amount, method (GCash or Maya) and the payment reference from Xendit. We never receive your e-wallet PIN or password.
- Venues: business name, address, map location, sports, hours and public contact details (phone, email, WhatsApp, Facebook page) from lawful public sources, and anything the venue gives us. Staff accounts hold a name, email and role. Payout details hold the account holder name, channel and account number.
- Messages: the booking messages we send by SMS, email, push, WhatsApp and Messenger, and venues' replies to them.
- Usage: if analytics are switched on, anonymous page views without query strings and without session recording. Error reports have personal data removed before they leave your device or our servers.
- Google Calendar: When a venue owner or manager connects a Google Account, we store a refresh token (a credential that lets Club Hub keep the connection working) and connection details for the venue, calendar and staff account that connected it. A booking event sent to Google contains a booking identifier, the court name, booking status (such as “Walk-in,” “Hold (unpaid)” or “Booked”), and its start and end times. It does not include the player’s name, contact details or payment information. To connect, we request Google’s
calendar.eventspermission, which allows an app to view and edit events on all calendars in that Google Account. Club Hub’s current sync writes booking events only to that account’s primary calendar and does not read existing calendar events.
3. Why we use it
- To take, confirm, pay for, refund and support your bookings (our contract with you).
- To pay venues and keep tax and accounting records (legal obligation).
- To list venues and contact them about booking requests, and to prevent fraud and abuse (legitimate interests, balanced against your rights).
- To show players what a venue looks like, using photos players choose to share (legitimate interests). Signed-in players can report a player photo; we hide it while we check it, and the venue can also take down photos of its venue. We remove photos that are spam, abusive, off-topic or fake, or that show personal details, and we remove a photo of a recognisable person if they ask.
- For anything else, such as marketing messages, only with your consent.
- To keep a venue’s Club Hub booking events in sync with the Google Calendar its owner or manager connects. We create or update events when a booking changes and mark an event cancelled when its booking is cancelled.
4. Messaging venues
We contact venues by SMS, email, WhatsApp and Messenger about booking requests. Follow-ups are not sent between 22:00 and 07:00 Philippine time. Our SMS sender name cannot receive replies, so venues answer through the link in the message, WhatsApp, Messenger or email. If a venue asks us to stop, we stop messaging that number or address and keep a one-way hash of it so it is never contacted again, even if the listing is rebuilt.
5. Who we share it with
- The venue you book, which receives what it needs to host you.
- Service providers acting for us: Xendit (payments, refunds and payouts), Semaphore (SMS), Resend (email), Expo (app notifications), Convex (database), Vercel (hosting), Google (Maps, sign-in, and Calendar sync for venues that enable it), Meta (WhatsApp and Messenger), Sentry (error reports) and PostHog (analytics, when switched on).
- Authorities, when the law requires it.
Some of these providers store data outside the Philippines, including in the United States. We use them under agreements that require them to protect it. We do not sell personal information.
6. How long we keep it
| Record | Kept for |
|---|---|
| Ledger lines, receipts and invoices | The BIR record-keeping period |
| Dispute evidence | 90 days after the dispute is resolved |
| Message bodies (outbox and follow-ups) | 90 days; links inside them are removed once the message is sent |
| Stop requests (suppressions) | Indefinitely, stored only as a one-way hash of the number or address |
| Guest booking links | 30 days after the slot ends, stored as a hash |
| Your account and profile | Until you delete your account |
| Venue photos you add | Until you, the venue or Club Hub remove them, or you delete your account. A removed photo’s file is deleted at once. |
| Records of which terms you accepted | As long as needed to show what was agreed |
| Google Calendar connection and refresh token | While the venue connection is active. When it is disconnected, we remove the active Club Hub connection record and ask Google to revoke the token. The revocation request can fail. |
Disconnecting stops future sync but does not delete booking events already sent to Google Calendar. You can remove those events directly in Google Calendar. If Google does not process the revocation request, you can also remove Club Hub’s access in your Google Account settings.
7. Keeping it safe
Booking links, one-time codes and stop requests are stored only as hashes. Payout account numbers are never written to logs. Access to venue data is limited by role, and every sensitive action is recorded in an audit log. Google Calendar refresh tokens are stored in our Convex database. Convex states that customer data is encrypted at rest; Club Hub sends the token to Google over HTTPS when refreshing access or requesting revocation. Club Hub uses the token on its servers and does not return it to your browser. Only venue owners and managers can connect or disconnect a calendar, and we record those actions in our audit log.
8. Your rights
You can ask to be informed, to access, correct, object to, block or erase your personal data, and to get a copy of it. You can delete your account from your account page; we then erase your profile, your messages, your answers about venues and the photos you added, but keep the payment and tax records the law requires. Venues can ask us to correct or remove a listing, and we act within 48 hours. If you are not satisfied with our answer, you can complain to the National Privacy Commission (privacy.gov.ph).
9. Changes
We will post changes here with a new version and date. See also our Terms of Service and the Venue Partner Agreement.