Seazn ClubSeazn Club

Privacy Policy

Last updated: 17 November 2026

1. Who we are

Seazn Club ("we", "us") operates the tournament management platform at seazn.club. We are the data controller for personal data processed through the service.

2. Data we collect

  • Account data: email address, display name, avatar URL.
  • Organisation data: organisation name, slug, member roles.
  • Tournament data: player names, results, standings, audit logs.
  • Billing data: subscription status, plan. Card details are held by Stripe and never stored on our servers.
  • Usage data: product analytics events (e.g. "first tournament created", page views) collected via PostHog, only with your consent. Withdraw anytime by clearing cookies or rejecting the cookie banner.
  • Communication preferences: email suppression list (bounces / complaints).
  • Consent records: when you create an account or submit a competition registration we record the time and policy version of your acceptance, so we can demonstrate it later.
  • Sponsor proof-of-play stills: when an organisation streams a match with the score overlay and one of its sponsors' cards appears on air, we capture one still picture of the stream a moment later. The still can show players. It is kept in private storage with the record of that showing, and is shown to that sponsor only through a private report link that the organisation creates and can revoke; each view uses a web address that expires within an hour. Deleting the sponsor ends its report links, so its stills are no longer shown to anyone, but they stay with the organisation's records of its showings. They are deleted when the organisation's account is deleted, and a still whose showing was never recorded is deleted within two days after the stream ends.
  • Sponsor short links: when someone follows a sponsor's short link (seazn.club/s/…), we count the click. To count repeat taps from the same visitor once, we keep a one-way SHA-256 hash of the visitor's IP address for 30 seconds; for a link that does not exist, we keep the hash for one minute, to limit guessing. The IP address itself is never stored.

3. Legal basis (GDPR)

  • Contract — processing necessary to provide the service you signed up for.
  • Legitimate interests — security logging, fraud prevention.
  • Consent — product analytics (PostHog), set only after you accept the cookie banner and withdrawable at any time.
  • Legal obligation — tax records, dispute resolution.

4. How we use your data

  • Providing, operating, and improving the service.
  • Sending transactional emails (verification, sign-in links, billing receipts).
  • Detecting and preventing abuse or fraud.
  • Responding to support requests.

We do not sell your data or use it for advertising.

5. Automated grouping when we build a schedule

When we lay out a timetable, player records that carry the same name are treated as one player while a timetable is built, so one person is never booked onto two courts at the same time. It is a scheduling safeguard only. No records are merged: the records stay separate on rosters, results and reports, nothing is written to them, and the grouping is discarded when the run ends. Every grouping we make is listed back to the organiser before they apply the schedule, so a wrong match can be corrected. This is not automated decision-making under Article 22 — it decides only what time a match is played.

6. Online chess: camera video and your Lichess account

When a competition is played online, each player links a Lichess account and plays from a match room on seazn.club with their camera on.

  • Your Lichess account: we store your Lichess username and the OAuth token you grant us, encrypted at rest. We use the token only to play your online games at Lichess: creating them, sending your moves and reading their state. Unlinking the account deletes the token and asks Lichess to revoke it. The game itself is played at Lichess under your own account, and Lichess’s privacy policy applies to it.
  • Your camera: during a match your camera video is carried by Cloudflare RealtimeKit (see the sub-processors list). Your opponent can’t see your camera. The competition’s organisers, acting as arbiters, can watch both players’ cameras live. We do not record the video.
  • Camera on or off: after the match, Cloudflare tells us when each player’s camera was on. We use it only to flag long gaps to the organiser, who decides what, if anything, follows. The flags are kept with the competition's records.

7. YouTube live streaming (YouTube API Services)

Seazn Club uses YouTube API Services. If an organiser of your organisation connects its YouTube channel, we use them (the YouTube Data API and Google's authorisation (OAuth) service for the YouTube permission) so that a match can be streamed live to that channel. By using this feature you agree to be bound by the YouTube Terms of Service. What Google does with your data is described in the Google Privacy Policy. Nothing in this section applies unless an organiser connects a channel.

Seazn Club's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

  • What we access: with the permission you give at Google, your channel's id and title, and the live broadcasts and live streams on that channel. For a match your organisation streams, we create a broadcast and a stream key on the channel, start the broadcast, and end it when the match is over.
  • What we store: the channel id and title; an identifier of the Google account that granted access; a refresh token (encrypted at rest); for each broadcast, its id, which is also its video id, and its title (the two sides, the division and the competition); the stream keys we create on the channel (encrypted at rest); a keyed one-way fingerprint of the channel id, kept on the channel's entry in your organisation's list of stream destinations; the visibility and made-for-kids choices your organisation made; and a record of who agreed to connect, when, and to which wording.
  • How we use it: only to stream your organisation's matches: to create, start and end broadcasts, to show a replay link on the match page once a broadcast is complete, and to check each day that the channel is still connected and still has the name we show. We do not use it for advertising, we do not sell it, and we do not use it for anything else.
  • Who it is shared with: Google, which receives the match picture and the title and description we set, as part of the broadcast your organisation asked for, under Google's own privacy policy. To carry the picture to YouTube it passes through our stream relay, which our sub-processors run: Cloudflare, to whose live-video service we give the stream key we created on your channel so that it can send the picture on to YouTube, and, when a match is streamed with the score overlay (where that is available), Fly.io, where a machine we start for the match adds the overlay. What we store is kept in our database and hosting sub-processors (see the sub-processors list). We share it with no one else. A replay link is shown on the match's page to anyone who can open that page; a broadcast that Seazn Club created as Private is not shown there. That is the visibility Seazn Club asked YouTube for when it created the broadcast, and it is not read back from YouTube, so a visibility you change later in YouTube is not followed here.
  • How long we keep it: the refresh token, the channel id and title and the Google account identifier are kept while the channel is connected. The broadcast and video ids and titles, the replay links and the stream keys are refreshed or deleted within 30 days: we re-confirm each stored video with YouTube after 25 days and delete it if YouTube no longer has it, we delete any that has not been confirmed within 30 days, and we delete a stream key that nothing has used for 30 days, asking YouTube to delete the stream where we can. The sealed token and channel names of a connection that was started and not finished are deleted when the channel is connected, and otherwise by the next daily check after the attempt expires, 10 minutes after it was started (choosing Cancel in the channel picker does not delete them sooner). The record of who agreed to connect, when and to which wording, and the visibility and made-for-kids choices, are not data from YouTube; they stay on the channel's record, after a disconnect too, for as long as your organisation's account exists on Seazn Club. If Google stops honouring the connection (for example because you removed Seazn Club at Google), Seazn Club shows it as needing to be reconnected, and if it is not reconnected within 7 days of that we delete everything we stored from YouTube for it (except the channel fingerprint described under Disconnecting below) and, unless another connected channel uses the same Google account or the token cannot be read, ask Google to revoke the grant.

Disconnecting and revoking access. An organiser can disconnect the channel at any time from the Streaming page (not while a match is streaming through it). Disconnecting deletes at once everything we stored from YouTube for that channel: the refresh token and stream keys, the broadcast and video ids and titles, the replay links on match pages, the channel id and title, the Google account identifier, and any reconnection of the channel that was started and not finished. One thing is kept: the channel's entry in your organisation's list of stream destinations is archived rather than deleted, because the history of earlier streams refers to it, and it keeps a keyed one-way fingerprint of the channel id. It is not the channel id and we cannot turn it back into the channel id, but it would let us tell whether a given channel id is the one it came from. It stays for as long as your organisation's account exists on Seazn Club. The same applies when we delete a connection that stopped working. Where Seazn Club can still reach YouTube when you disconnect, it also, within a time limit, ends any broadcast of ours that is still running, deletes any broadcast of ours that never went live, and deletes the stream keys it created on your channel; if it cannot (the access was already withdrawn, or YouTube does not answer in time), those stay at YouTube. Finished broadcasts and their videos stay on your channel: they are yours, and we delete only our record of them. Disconnecting also asks Google to revoke the access, unless another connected channel uses the same Google account (revoking would end that channel's access too) or the stored token cannot be read; the Streaming page tells the organiser when it could not confirm the revoke. You can revoke Seazn Club's access yourself, at any time, in your Google account's security settings; the connection then stops working and the deletion described above follows.

Cookies and your device. A recorded match on a public match page can show its replay in YouTube's player, which is third-party content from YouTube, not part of Seazn Club. Nothing from the player loads until you tap play: before that, only the video's thumbnail is fetched from YouTube's image servers. After you tap, Google's player may store cookies or similar data on your device, under Google's policy. Fetching the thumbnail and loading the player each send your IP address and browser details to Google. A replay of a video made for kids is a link to YouTube, not a player: nothing is fetched from YouTube for it until you follow the link. See our Cookie Policy.

Questions or complaints about how we handle YouTube data: [email protected].

8. The Seazn Club phone app

Seazn Club has a phone app for Android (com.seazn.capture) that an organisation's volunteers use to stream and score its matches. It has no account and no sign-in: it works from a stream code or a scoring link that the organiser gives the operator.

  • Camera and microphone: the app uses the phone's camera and microphone to stream a match. The picture and sound are sent only once a broadcast is started, by the operator's tap on Go live or by the organiser when the operator has allowed the app to start and stop automatically, and they stop when the broadcast ends. They go to our streaming infrastructure and from there to the organisation's YouTube channel or other destination the organiser chose. The app does not keep a recording on the phone. On our streaming infrastructure a recording of the broadcast is kept for up to 3 days so that a disputed match can be checked, then deleted. People in view of the camera may be seen and heard on the stream; the organisation running the event decides what is streamed and is responsible for telling the people it films.
  • Status reports: while the app is paired with a match or a court it tells us how the phone is doing, so the organiser can see whether the stream is healthy: the phone's model, the app's version, a random identifier the app makes for that pairing, the battery level and whether it is charging, and the state and quality of the connection and of the stream. These reports are deleted after 24 hours.
  • Technical record: if something goes wrong, the operator can tap Send record to Seazn. The record is a list of technical events from that session (timings, connection and encoder figures, error words). It holds no picture and no sound, and the app removes anything that looks like a code or a secret before it is sent. It is sent only on that tap, is used only to diagnose the problem, and is deleted after 30 days.
  • Scoring: when the operator scores a match in the app, the points they enter are saved to that match exactly as they are from the website.
  • Kept on the phone: the stream code or scoring link and the app's settings, in the phone's secure storage. Forget in the app, or uninstalling it, removes them.
  • What the app does not collect: it has no account, and it does not read the phone's location, contacts, photos or files, or its advertising identifier. It shows no advertising and holds no third-party analytics or advertising software.

Everything the app sends travels encrypted. Questions, or a request to delete data the app sent: [email protected].

9. Sub-processors

We share data with trusted sub-processors to operate the service. See our sub-processors list for details.

10. Data retention

Account data is retained for the life of your account plus 30 days after deletion. Tournament records may be anonymised rather than deleted at your request. Billing records are retained for 7 years for tax compliance.

Scheduling instructions you preview but do not run are deleted within the hour; a preview you did run is kept for 30 days so a disputed plan can be re-checked.

11. Your rights (GDPR)

You have the right to access, correct, or delete your personal data. You can export your data from Settings → Account → Export my data. To exercise other rights, email us at [email protected]. We respond within 30 days.

12. Cookies

We use essential session cookies plus, with your consent, PostHog analytics cookies. No advertising cookies. See our Cookie Policy.

13. Security

Data is encrypted in transit (TLS) and at rest. Sign-in is by a single-use emailed link or by Google. Access is controlled by row-level security policies at the database level. Staff access is logged and audited.

14. Changes

We will notify you by email of material changes to this policy at least 14 days in advance.

15. Contact

Privacy questions: [email protected]