Overview
Courtzy is a racket-sports queue, live-session, social, rating, public event discovery, sanctioned-event, and court booking management app. This policy explains what data is stored on your device, what data is stored online when you sign in or use connected features, and which service providers help operate the app.
Local Session Data
Courtzy stores app preferences and regular session history on your device using AsyncStorage. Active sessions may include full player, court, queue, score, and match state so they can be resumed. When a regular session ends, Courtzy stores a compact summary instead of the full match-by-match history. You can delete local session history in the app.
Account and Public Profile Data
Optional sign-in is provided by Firebase Authentication using email/password, Google Sign-In, or Apple Sign-In. When you sign in, Firebase may store your email address, display name, sign-in provider, verification status, and Firebase user ID. Courtzy stores account profile data, a unique display-name reservation, previous display-name aliases used for matching participation, and a public profile containing your display name and join date.
Ratings and Participation Statistics
For signed-in users, Courtzy stores per-sport Elo ratings and aggregate participation statistics such as sessions, games, wins, and MVPs in Cloud Firestore. Regular session records remain local, but their aggregate contribution may be synced to your online statistics. Sanctioned-event results may also contribute to those statistics. Public profiles and statistics are available to signed-in users for leaderboards, player selection, and profile views.
Friends, Notifications, Live Sharing, and Events
Friend requests, friendships, social notifications, event invitations, sanctioned-event details, participants, and event summaries are stored in Cloud Firestore. Active sanctioned events may store full live session state — including, for Tournament Mode events, the bracket structure, seeding, per-game results, and standings; ended events store a compact session summary that keeps the final tournament bracket. If a signed-in host shares a regular live session, Courtzy uploads the live session state and a six-character join-code record so spectators can follow it. Spectators may keep a local copy until they stop spectating or remove it.
If you grant the notification permission while signed in, Courtzy stores a push token for your device in Cloud Firestore so that friend requests, friend-request acceptances, event invitations, event join requests and host decisions can be delivered as device push notifications. Push tokens are linked to your account, may cover multiple devices, are removed for a device when you sign out on it, and are deleted with your account. Notification delivery is handled by the Expo push notification service together with Apple Push Notification service (iOS) and Firebase Cloud Messaging (Android); notification content is limited to the notification type and related display or event names. You can decline or later disable the notification permission in system settings — social notifications then remain available inside the app.
A host may also enable co-hosting, which creates a separate co-host join code. Signed-in users who join with a co-host code can view and modify the shared live session (for example players, scores, and match results), and Courtzy stores a co-host record containing their user ID, the code used, and the join time until co-hosting is disabled, sharing stops, or the session ends. Shared links use courtzy.vercel.app, with older links on courtzy.netlify.app. Session and invitation links carry a code or invitation identifier; treat them like the codes themselves. Published Find links carry a listing identifier and open a public event page without sign-in. Spectator links can show a read-only web view; co-host controls and event join requests require the mobile app. Hosting and messaging services may receive the shared URL and retrieve page information or preview images.
Event and sharing records may include display names, user IDs, player assignments, scores, match results, ratings, timestamps, and host or participant information. The Courtzy interface normally surfaces sanctioned events based on host, invitation, participant, or link visibility. Current Firestore access controls permit signed-in users to retrieve sanctioned-event records. Shared regular sessions are available through their join-code records. Do not include sensitive personal information in player names, session names, or event details.
Find: Public Listings, Participants and Location
Find expands cloud-backed sanctioned events with public discovery. A signed-in Pro host can publish an event from Find > My Listings. Published event information is readable without sign-in through shared web pages and our public listing service, even though browsing Find inside the app requires sign-in. This includes the event title, description, sport, host display name and account identifier, venue name, country, Google Maps link, schedule, event status and public game settings.
Published events can also show a public participant list: display names, Member or Guest labels, list order and sport-specific Elo snapshots when available. Guests do not need Courtzy accounts; their names and host-assigned Elo ratings are stored with the event. The public participant list does not include participant account IDs, phone numbers, invitation codes or private live-session records. Hosts should tell participants, including guests, what will be published and obtain any permission needed before adding them. Do not put private contact details in public titles or descriptions.
Event country is selected by the host. The initial suggestion uses the device timezone, with Philippines as a fallback, and can be corrected. This suggestion does not use GPS, public-IP lookup or Google's geocoding API. Country filters use listing information, not your live location. Opening a Google Maps link sends you to Google's service, subject to its own privacy practices.
Ending an event does not automatically remove its published page or participant list. Unlisting makes the public post and roster unavailable through Courtzy's public listing service but does not delete the cloud event or copies already shared, downloaded or cached by others. Past in Find shows your hosted events and events where you actually participated, rather than every expired public listing.
Event Join Requests and Private Phone Numbers
Publishing an event requires the host's international contact number. Requesting to join requires a signed-in player to provide their own contact number and confirm mutual sharing. Courtzy stores the requester's account ID, display name, phone number, event/host identifiers, request status and timestamps to let the host review and respond. Phone-number format validation does not verify ownership of that number.
The host can read the requester's number. A requester who has supplied a number can read the host's number, including before acceptance. These numbers and join requests are stored separately from public event listings and are not shown on the public web page. Host-only participant controls may show a requester's supplied number; invitations alone do not supply a participant contact number.
Acceptance adds the requester to the event; a pending request is not participation. Cancellation and decline retain the request record and supplied number, and previously disclosed host contact access remains available. Cancelling a request, leaving an event or unlisting it does not retract information another person has already received. Account deletion removes join-request records you submitted or received as a host; contact us for questions about other retained event data.
Court Booking Marketplace
The Book area lets signed-in users list courts for rent and request to book courts listed by others. Courtzy does not process payments for court time and is not a party to any booking; it stores and displays the listing and booking information described below so that a court owner and a player can arrange a booking and contact each other directly.
Court listings. When you list a court, Courtzy stores the listing details you provide in Cloud Firestore: the listing name, sport, number of courts, hourly rate and currency, the address, city, and country, a Google Maps link, the opening hours you set for each day, amenities, an optional description, and the contact details you choose to publish — any combination of a phone number, an email address, and a link. A new listing, and any later edit to an approved listing, is reviewed by Courtzy before it becomes visible or takes effect. Once approved, a listing — including the contact details you publish so players can reach you — is visible to signed-in Courtzy users browsing the Book area. Do not publish contact or address information you are not comfortable sharing with other signed-in users.
Bookings. When you request to book a court, Courtzy stores the requested courts, dates, and hours, an optional note to the owner, and a contact detail you enter so the owner can reach you about the booking. That contact detail is saved on your device so you do not have to retype it, and it is sent to the court owner with your request. Booking requests, confirmations, declines, cancellations, and owner block-outs are stored in Cloud Firestore and shared with the relevant court owner or booker. The booker's name, contact, and note are shown to the court owner; notifications sent from an owner to a booker do not reveal the owner's account name.
Ratings, reports, and reputation. Signed-in users can leave a one-to-five-star rating on a listing and can report a listing they believe is fake, misleading, or otherwise objectionable; one rating and one report per user per listing are stored in Cloud Firestore, and a listing that receives reports from several distinct users is automatically hidden pending review. Courtzy also stores a per-user booking-reputation score derived from your completed and cancelled bookings, which may be shown as a stat on your profile and is used to help review the marketplace.
Notifications. Booking requests and updates, and listing-review messages, use the same in-app notification and optional device push pipeline described above.
Payments happen outside Courtzy. Any payment or other arrangement for court time is made directly between the booker and the court owner, outside the app, using the contact details on the listing. Courtzy does not collect, process, or store court-rental payment information.
Courtzy Pro
Courtzy Pro is an optional subscription. Pro users receive ad-free use and cloud-backed sanctioned event hosting, in Open Play or Tournament Mode, now available through Find > My Listings with public listings, join-request management and guest participation. This continues and expands the existing sanctioned-event benefit. Browsing Find and participating do not require Pro; app browsing and member join requests require sign-in. Normal session history remains stored locally on the device. Legacy users who purchased the previous one-time Support the Developer product keep lifetime Pro access. Listing and booking courts in the Book area does not require Courtzy Pro.
Purchases
Subscriptions and legacy purchases are processed by Apple or Google and validated by RevenueCat. Courtzy and RevenueCat receive purchase identifiers, transaction/receipt status, entitlement status, and a pseudonymous app user ID. Courtzy does not receive payment card details.
Advertising
Courtzy displays Google AdMob ads to non-Pro users on supported native platforms. Pro users do not see ads. Where your tracking permission and any required regional advertising consent allow it, ads may be personalized, and the Google Mobile Ads SDK may use the device advertising identifier for ad selection, frequency capping, and measurement (including Apple SKAdNetwork attribution on iOS). Courtzy does not share Courtzy profile, friend, session, score, or event content with AdMob for ad targeting.
AdMob may also process device identifiers, IP address, network information, diagnostics, product interaction, advertising data, coarse location, and ad-interaction data needed to serve, secure, limit, and measure ads according to Google's policies. On iOS and iPadOS, Courtzy uses Apple's App Tracking Transparency prompt before initializing Google Mobile Ads when tracking permission has not already been decided. If you decline tracking permission, Courtzy still works and AdMob should not receive the device's IDFA from Courtzy; ads then appear as non-personalized or limited ads. Where required, Courtzy also asks for advertising consent and provides an in-app Ad Privacy Choices option so you can review or change regional advertising consent choices. Those choices do not override your Apple App Tracking Transparency setting.
Third-Party Services
- Firebase Authentication and Cloud Firestore by Google: sign-in, profiles, friends, cloud events, public event listings and participant lists, private event contacts and join requests, court bookings, live sharing, and notifications.
- Expo push notification service, Apple Push Notification service, and Firebase Cloud Messaging: delivery of device push notifications for signed-in users who grant the notification permission.
- Google Sign-In and Apple Sign-In: optional account login.
- RevenueCat: purchase and subscription validation.
- Google AdMob: ads for non-Pro users, including ad serving, security, fraud prevention, frequency limiting, and ad measurement.
- Apple App Store and Google Play: subscription billing and purchase management.
- Vercel and Netlify: Courtzy website, public event pages and shared-link pages. Web requests disclose standard connection information such as IP address, browser information and requested URL to the hosting service.
- Google Maps: external location links you choose to open.
Your Choices
You may use regular local session features without signing in. Friends, public profiles, online ratings, Find browsing in the app, event hosting and member join requests, hosting live shared sessions, listing or booking courts, and cross-device purchase restoration require an account. Public event web pages and host-added guests do not require a Courtzy account. You can delete local session history and your Courtzy account in the app.
You can manage iOS tracking permission in Apple Settings after responding to the App Tracking Transparency prompt. If Ad Privacy Choices is available in your region, you can also open Profile > About Courtzy > Ad Privacy Choices to review or change regional advertising consent preferences.
Account deletion removes your Firebase Authentication account, Courtzy account profile, public profile, social statistics, owned display-name reservation, friendships, and stored push tokens. It also removes your Find listings, their public participant projections and organizer contact records, and join-request records you submitted or received as a host, including their phone numbers. It removes your court listings and everything on them, the booking requests you made on other courts and the notes and contact detail they carried, the corresponding booking holds, and your booking-reputation record. Some records involving other users or external systems—such as invitations, notifications, sanctioned-event records, live-sharing records, security logs, and store or RevenueCat transaction records—may remain where needed for service integrity, legal obligations, dispute handling, or other users' records. In rare cases an older confirmed booking hold on another owner's court can only be cleared by that owner, so a technical hold record may briefly remain even though the underlying booking has been deleted. Contact us to request review of remaining Courtzy-controlled data. Deleting your account does not cancel an App Store or Google Play subscription; cancel it separately through the applicable store.
Data Retention and Security
Local data remains on your device until you delete it, clear app data, or uninstall the app, subject to device backup behavior. Online data is retained while your account or the relevant social, sharing, or event record is active and may be retained afterward when reasonably necessary for the purposes described above. We use the security features provided by Firebase, Apple, Google, and RevenueCat, but no storage or transmission method is completely secure.
Children's Privacy
Courtzy is not directed to children under 13, and we do not knowingly collect personal information from children under 13.
Changes
We may update this policy as Courtzy evolves. The effective date above will change when updates are made.
Contact
Questions or data requests: loqzcorp@gmail.com