Privacy policy

1. Who this policy covers

This policy covers the IKOT website, organizer accounts, public player views, and optional messaging notifications. IKOT provides tools for Clubs and organizers to manage open-play sessions. Your Club or organizer also decides what participant information to enter and how to run its sessions. Contact them about roster details or results they supplied; contact the IKOT team about the service or a privacy request.

2. Information we handle

• Accounts and Clubs: email address, display name, protected password credentials, Club profile and contact details, venue information, and account or membership permissions.
• Open play: participant display names, play levels, check-in and queue state, court assignments, match results, session history, and linked player profiles where used. An organizer may enter these details for you.
• Support: the name, email address, and message you submit when contacting us.
• Service operation: authentication and player-pass identifiers, timestamps, request and error information, and records needed to secure the service and diagnose failures.
• Optional integrations: Messenger, Telegram, or Discord account identifiers, browser push addresses and keys, connection events, and delivery records described below, or linked DUPR identity, ratings, and reporting records when you use DUPR features.

3. How information is used

We use this information to provide account access, run sessions and fair court rotations, show queue and match information, maintain results, send requested service messages, respond to support requests, and protect the service from misuse. Optional integrations use the information needed to provide the feature you choose.

4. Public information and service providers

Public session links and Club leaderboards can be viewed without signing in. Participant display names, play levels or ratings, queue positions, court assignments, and results may be visible there. Share player-pass links only with their intended player: a pass grants access to that participant's session actions.

A Club that has held an open play has a public Club page that search engines may index. It shows the Club name, logo, city and region, when and where the Club usually plays, upcoming and recent open plays, standings with the top player display names, and the website and social links the Club saved. A Club's contact email, phone number, and internal profile details are not shown. A Club owner can hide the Club page, standings, and link previews at any time in Club Settings.

Hosting and email providers process information needed to operate IKOT. Meta, Telegram, and Discord process conversations, account authorization, and alerts when you connect the corresponding channel. Your browser's push service delivers encrypted phone notifications when you turn them on. DUPR processes identity, rating, and match information when its integration is used. Information may also be disclosed where required by law or necessary to address abuse or protect service security. Third-party services handle information under their own policies, and may process it outside your country.

5. Messenger notifications

Messenger alerts are optional. To connect, claim your session player pass, request a one-time Messenger code, and send it to the configured Facebook Page. This links the sender to one participant for that open-play session. You can use the player view without connecting Messenger.

IKOT receives incoming Page message events from Meta. It uses the Page-scoped sender ID, Page ID, message ID, message text needed to recognize an enrollment code, and event times to connect your subscription, prevent duplicate processing, and determine whether alerts can be sent. Enrollment codes are stored as hashes. Subscription records, incoming-event processing records, and outgoing notification content, delivery status, and retry records are stored to operate the feature.

To deliver an alert, IKOT sends Meta your Page-scoped recipient ID and the notification text, which may include your session, game, court, and player details. Connecting Messenger does not grant IKOT access to your Facebook password, friends list, or private conversations outside the connected Page. These alerts concern your open-play session.

The connection ends with the session. Alerts are sent only within the standard 24-hour window after you message the Page. You can select Turn off alerts in the session's Messenger alerts card, send STOP to the connected Page, or select Cancel setup before connecting. Pending work is cancelled when you disconnect, but a message already being sent may still arrive. Disconnecting does not erase stored records or messages already delivered to Meta.

Meta also handles your information under its Privacy Policy (opens in a new tab).

6. Telegram notifications

Telegram alerts are optional. On an active Classic board, you may select a named participant, open an expiring IKOT bot link, and tap Start. This follows that participant for alerts; it does not prove that you are the participant or grant control over their queue position or results. A claimed player pass and one-time manual code remain available as an alternative.

IKOT receives bot updates from Telegram and uses the Telegram user and chat identifiers, update and message identifiers, message text needed to recognize an enrollment code or bot start, and event times to connect your subscription and prevent duplicate processing. IKOT stores short-lived setup records, subscription, incoming-event, outgoing notification, delivery-status, and retry records. Alerts sent to Telegram may include the followed player's name, session, game, court, and queue details.

The browser that completes setup receives notification-only management access. It can switch that Telegram subscription to another named participant or turn it off, but cannot use this access for check-in, player commands, or score confirmation. You can select Turn off alerts in the Telegram alerts card, or Cancel setup before connecting. The connection ends with the session. Disconnecting cancels pending IKOT delivery work but does not erase stored records or messages already delivered to Telegram. Telegram handles your information under its Privacy Policy (opens in a new tab).

7. Discord notifications

Discord alerts are optional. On an active Classic board, you may select a named participant and authorize IKOT through Discord. IKOT uses the authorization response to follow that participant for alerts; it does not prove you are the participant or grant control over their queue position or results. A claimed player pass remains an alternative setup path. A Discord server membership and direct-message settings that allow the IKOT bot to contact you are required for delivery. Discord authorization requests identity access only.

IKOT uses your Discord user ID to identify the connected account and stores the private DM channel ID used to deliver alerts. It also handles authorization and callback events, event times, and records needed to protect the connection, plus subscription, outgoing notification, delivery-status, retry, and short-lived setup records. The temporary Discord access token is discarded or revoked after linking and is not kept as the delivery credential. Alerts sent to Discord may include the followed player's name, session, game, court, and queue details. IKOT never asks you to enter your Discord password in IKOT.

The browser that completes setup receives notification-only management access. It can switch that Discord subscription to another named participant or turn it off, but cannot use this access for check-in, player commands, or score confirmation. You can select Turn off alerts in the Discord alerts card, or Cancel setup while authorization is pending. The connection ends with the session. Disconnecting cancels pending IKOT delivery work but does not erase stored records or messages already delivered to Discord. Discord handles your information under its Privacy Policy (opens in a new tab).

8. Phone notifications

Phone notifications are optional browser push alerts. On an active Classic board, you may select a named participant and allow notifications. Your browser then creates a push address and encryption keys with its push service (for example Google, Mozilla, Apple, or Microsoft), and IKOT stores that address and those keys to send alerts. IKOT does not receive your phone number or account details. Following a participant does not prove you are that participant or grant control over their queue position or results.

Alerts are encrypted before IKOT hands them to your browser's push service. They may include the followed player's name, session, game, court, and queue details. IKOT also keeps subscription, outgoing notification, delivery-status, and retry records. On iPhone and iPad, notifications require adding IKOT to the Home Screen and opening it from there.

The browser that turns on phone notifications receives notification-only management access. It can switch the alerts to another named participant or turn them off, but cannot use this access for check-in, player commands, or score confirmation. Select Turn off phone notifications to stop alerts and delete the stored push address and keys. IKOT also deletes them when the push service reports the address is no longer valid, and alerts stop when the session ends. You can also block notifications for IKOT in your browser settings.

Optional Sound and vibration and Keep screen on settings for an open Player View are saved only in that browser and are not sent to IKOT.

9. Cookies and browser storage

IKOT uses an authentication cookie for organizer sign-in and browser storage to remember player-pass access, a selected player, pending messaging setup, notification-only management access, and related session access. Messaging setup uses a short-lived protected cookie plus browser-only setup values; completed Telegram, Discord, and phone notification subscriptions use separate per-provider access from the player pass. Phone notifications also register a service worker that only displays alerts. Clearing cookies can sign you out or interrupt pending setup; clearing browser storage can remove player-pass or notification-management access on that device. Neither action deletes server records or disconnects a messaging channel. Never share a device's player pass with someone who should not control that participant.

To understand how people find IKOT, public pages such as the home page, Club pages, and live player views send an anonymous page visit to our own self-hosted analytics. It sets no cookies and stores nothing in your browser. It records the page path (live session links are shortened so the session is not identified), the referring website, campaign tags in the link, and general browser, device, and approximate location (country and city). Your IP address is used only to derive those details and is not stored. Organizer, account, and admin screens are not tracked this way, and browsers that send Do Not Track or Global Privacy Control are not counted.

IKOT also keeps its own counts of how the service is used. When a live player view or Club page is opened, or results are shared, we record that it happened, for which session or Club, whether it came from a printed QR code, and how results were shared. These counts are not linked to a player, account, or device; your IP address is used only briefly to avoid counting the same device twice in a day and is not stored. When you create an organizer account, we keep the campaign tags and referring website of the visit that brought you to IKOT with your account, so we can see which channels lead to Clubs that run sessions. Browsers that send Do Not Track or Global Privacy Control send none of this.

10. Retention and security

Ending a session or expiring an enrollment code does not automatically erase session, subscription, or delivery history. Records support results, reliable delivery, security, and support. Retention depends on the record and its purpose; there is no single automatic deletion period for all records. Backups may retain copies after changes to live records.

IKOT uses access controls, protected credentials, and validation of player passes and incoming provider signatures and authorization callbacks. No internet service can guarantee absolute security.

11. Data deletion and your choices

To request access, correction, or deletion of your IKOT information, including messaging subscription and delivery data, email support@fastikot.com with the subject IKOT privacy request. For deletion, say whether you want your account, session participant information, messaging connection data, or all associated information reviewed for deletion.

Include the email associated with your account, if any, and enough context to locate the record, such as the Club, session link or date, and participant display name. For messaging-only requests, identify the provider and session you connected to. Do not send passwords, access tokens, or enrollment codes. We may ask you to verify control of the account or connection before changing records.

Your available rights depend on applicable law. Some information may need to be retained for legal obligations, security, or the rights of others in shared match history; we will explain any limits when responding. An IKOT deletion request does not delete your Facebook, Telegram, or Discord account, or those providers' copies of conversations. Manage those through the corresponding provider.

12. Contact and policy changes

The IKOT team handles service privacy questions at support@fastikot.com. You can also use our contact page. We update this page when our practices change and revise the date above.