Last updated 25 September 2026
This describes what Sports collects when a club uses the platform to run its sessions, and why. It covers players joining a session, organisers running the desk, and club owners/managers using the dashboard.
A club owner subscribing their club is billed through Stripe, our payment processor — we never see or store your card number ourselves; Stripe's own privacy policy covers what they hold. We don't use third-party advertising trackers or sell any data to third parties.
Platform staff (not your own club's organisers, owners, or managers) can see every club's owner/manager name and email, and subscription/billing status, in order to provide support and manage the platform — never a player's or member's own details, and never a club's session data. Staff may keep internal notes about a club (e.g. a support request and how it was resolved) for this purpose; these notes are never shown to that club's own owner, manager, or organiser.
A business running more than one club can group its own clubs into an organization for a combined view — total members, sessions run, and billing summaries across just the clubs it owns and has linked itself. This never gives one business visibility into a different, unrelated business's clubs, and a club's own billing relationship with the platform is unaffected either way.
If you reserve a specific court and time through a club's booking page, the club can see who booked it (your name and email), when, and for how long — the same way they can see who's registered to run the desk. A booking is separate from an organized session's roster and isn't shared with other players. If you join the waitlist for an already-taken slot, the club can see that request the same way; it's used only to tell you once — by email, and by push notification if you've turned those on — if a matching slot opens up. If you subscribe to your bookings calendar from your player account, anyone you share that private link with can see your upcoming bookings; changing your password immediately revokes it.
If a club opts into the public directory, the location its owner enters (e.g. a suburb and city) is looked up on OpenStreetMap to place the club on the directory's map. That lookup sends only the club's location text, never anything about a player. The map itself is loaded from OpenStreetMap's tile servers, which see your IP address the way any website you load images from would. If you tap "Near me", your browser asks for your location and uses it only on your own device to sort clubs by distance — it's never sent to us or stored.
A club may keep its own manual record of charges against its members — a membership plan, a per-visit fee, or a one-off charge, and whether it's been paid, is still owed, or was waived. This is currently a record the club keeps itself, not something processed through a payment provider on the club's behalf, and it's never shared outside that one club (platform staff can see aggregate, non-identifying totals only, for support purposes).
If an organiser records a match result, it's tallied into a per-level win/loss ladder — but only against players who gave an email at join (see above); a name-only player's result is still recorded but never shown on the ladder. The same email link lets a club see a member's attendance/check-in history across every session they've joined, and lets a member view their own history, ladder standing, and stats via a link on their session page. Those stats include the names of the players a member has shared a court with or played against most often — the same names already shown on that night's public board — and are visible to the member and to their club.
A session's roster and final court layout (who played where, at every level) is kept indefinitely by default, at the request of clubs who wanted a permanent attendance record rather than having it wiped nightly. A club owner can instead set a retention limit (a number of days, from their dashboard's History page) after which older session data is automatically deleted. Either way this is configured per club, not settable by an individual player — ask your club owner if you'd prefer one over the other.
Some clubs have junior members. The join form only ever asks for a first name and skill level — no age, contact detail, or other identifying information is requested. A club admitting minors is responsible for any guardian consent or additional safeguarding its own policies require; this Service doesn't verify age or guardianship.
Owner/manager/front-desk sign-in, a player account's own sign-in, and the organiser PIN each use a signed session cookie strictly to keep you logged in — no advertising or analytics cookies are set by the Service itself.
If you opt in, your browser issues a push subscription (an endpoint and keys) that we store to send you a court-change notification — or, if you turn it on from your player account, a notice when a court slot you're waitlisted for opens up. We never see the notification content your browser displays, and you can turn this off at any time from the same page you enabled it on. Turning your device or browser's notification permission off achieves the same thing.
To ask what data is held about you, or to request it be corrected or removed, contact your club's organiser or owner first — they hold the record — or reach us directly at privacy@nightos.com. A club owner can export their club's records (members, attendance, bookings, charges, and results) as a spreadsheet, which is how they can give you a copy of yours.
We may update this policy as the Service changes. Material changes will update the date at the top of this page.