Effective date: September 10, 2026
About Tournament OS
Tournament OS is developed and operated by KRPA Designs LLC. It helps adult organizers create and manage badminton tournaments, including singles and doubles events, league and knockout structures, players and teams, match schedules and order, scoring, standings, tournament progression and results.
Core tournament management uses tournament data stored locally on the organizer's Android device. Optional account and cloud features are used when an organizer chooses Tournament OS cloud sharing, public tournament publishing or umpire collaboration.
Account information
If you create or sign in to an optional Tournament OS cloud account, Tournament OS may process your email address, Supabase user/account identifier, authentication credentials through Supabase Auth, authentication and refresh tokens, session-expiry information and other authentication information required to maintain the signed-in cloud session.
Tournament information
Tournament OS may process tournament names, player display names, team names and membership, event type and format, tournament dates and optional times, groups, rounds, match identifiers and order, game and match scores, match status, standings, qualification information, knockout brackets and progression, result-correction reasons, final results and champion information.
Core tournament information remains local unless you intentionally use a feature that sends applicable tournament information to Tournament OS cloud services, such as cloud sharing, public publishing or umpire collaboration.
Voice and microphone access
Tournament OS may request microphone access when you choose the voice-input control during assisted tournament setup.
On Android, Tournament OS uses the Android speech-recognition system through the expo-speech-recognition library to convert speech to text. Tournament OS does not force on-device recognition and does not select one fixed speech-recognition provider. Depending on the Android device, installed or default recognition service and device settings, speech recognition may occur on the device or the configured speech-recognition provider may process microphone audio over a network connection.
On many Android devices, the configured recognition service may be provided by Google. Other compatible recognition services may also be selected by the device or user.
Tournament OS does not enable persistent audio recording through the speech-recognition library and does not intentionally save raw microphone recordings to Tournament OS storage. Tournament OS receives the recognition result as text and places the transcript into the tournament-description field so you can review or edit it before submitting it.
Assisted tournament creation
When you submit a typed tournament description or a transcript created from voice input, Tournament OS may send the submitted text off the Android device to the Tournament OS setup-interpreter service hosted using Supabase Edge Functions.
The interpretation service returns proposed structured setup information such as tournament name, singles or doubles, tournament format, number of teams, date or time when those details can be interpreted from the organizer's description.
The interpreted result is only a proposal. It does not directly create authoritative match results, change tournament rules or override tournament state. The organizer reviews the interpreted setup and explicitly chooses whether to create a tournament draft. Tournament OS's deterministic application logic remains responsible for validating supported tournament structure and state.
KRPA Designs LLC does not intentionally store the assisted-setup description or interpretation response as a separate Tournament OS cloud database record. When the organizer chooses to create a draft, the resulting structured tournament information becomes Tournament OS tournament data.
Local device storage
Core Tournament OS tournament information is stored locally on the Android device using SQLite. This can include tournament configuration, players and teams, schedules, matches, scores, results, standings and other tournament state.
When you sign in to Tournament OS cloud features, account/session information needed to maintain the cloud session is also stored on the device. Deleting a Tournament OS cloud account does not automatically remove independent local tournament data stored on the Android device.
Cloud tournament sharing
When an organizer enables cloud sharing, Tournament OS sends the information required for that shared tournament to its Supabase-backed cloud service. This can include organizer user identifier, tournament identifier and public identifier, tournament name, event type and format, tournament date and optional time, team names, groups, rounds, match structure and order, game scores, match status, winners, standings, qualification and progression information, bracket/champion information, state versions and update timestamps.
Public tournament pages
When an organizer intentionally publishes a tournament, Tournament OS creates a public tournament snapshot intended for spectator viewing without a spectator account.
The published snapshot can contain tournament and team names, tournament status, tournament date or optional time, groups and rounds, current, upcoming and completed matches, game and match scores, standings, bracket progression, champion information and update timestamps. Anyone able to access the public tournament page or public link may be able to view that published information.
Organizers should avoid entering sensitive personal information into fields that will be published. Disabling public sharing prevents Tournament OS from continuing to expose the active public snapshot, but Tournament OS cannot recall information another person has already copied, captured or independently shared.
Umpire invitations and score entry
Tournament OS supports authenticated umpire invitations and cloud-based score submissions. An invitation may include tournament identifiers, an optional invited email address, protected invitation-token information, invitation status, organizer and accepted-user identifiers, membership role and status, and related timestamps.
An authenticated umpire may submit tournament and match identifiers, partial or completed game scores, command type, expected result version, optional correction reason, processing status, validation or rejection information and processing timestamps.
Umpire submissions do not directly overwrite authoritative tournament state. They are submitted as score commands. Tournament OS's deterministic tournament engine validates the proposed change before accepted results and downstream tournament state are applied.
Service providers
Supabase
Supabase provides Tournament OS cloud authentication, PostgreSQL database services, secured data APIs, Edge Functions and realtime infrastructure used for optional cloud sharing, public snapshots, umpire collaboration, account deletion and assisted tournament setup.
Android speech-recognition services
The Android speech-recognition service configured on your device processes voice input when you invoke microphone input. The provider and whether processing occurs on-device or over a network can vary depending on the Android device and system configuration.
Vercel
Vercel hosts tournament-os.app and related public web resources. Hosting infrastructure may process standard network information such as IP addresses, browser/request information and timestamps as necessary to deliver, secure and operate the website.
Google Play and Android
Tournament OS is distributed through Google Play and runs on Android. Google Play, Android, device manufacturers and related platform services may process technical, diagnostic or account information according to their own terms and privacy practices.
Advertising, analytics and tracking
The final Tournament OS V2 application dependency set reviewed for this policy does not include a third-party advertising SDK, behavioral-advertising SDK, dedicated product-analytics SDK or dedicated third-party crash-reporting SDK.
Tournament OS does not sell account, tournament or participant information for advertising. Infrastructure providers may create operational, diagnostic and security logs required to operate their services.
Identifiers and technical information
Cloud features may process identifiers required to provide those features, including the Supabase user/account identifier, account email, authentication/session tokens, tournament and match identifiers, public tournament identifiers, membership and invitation identifiers, score-command identifiers and state/version identifiers.
Assisted tournament setup may also transmit the device's local date and timezone. The reviewed Tournament OS V2 implementation does not intentionally request an Android advertising identifier or hardware-specific device identifier for these features.
Data transmission and security
Tournament OS uses HTTPS/TLS for supported network communications between the Android application, tournament-os.app and Tournament OS cloud services. Authentication tokens and Supabase access-control rules are used to restrict protected cloud information to permitted users.
Public tournament snapshots are intentionally accessible when the organizer enables public sharing and should not contain information the organizer expects to remain private. No electronic storage or transmission method can be guaranteed to be completely secure.
Data sharing
KRPA Designs LLC does not sell Tournament OS account, tournament or participant information.
Information may be processed or disclosed to infrastructure and service providers when necessary to operate Tournament OS; publicly when an organizer intentionally enables public tournament sharing; to authenticated tournament participants such as invited umpires when access is granted; when required by applicable law or valid legal process; or where reasonably necessary to protect Tournament OS, its users or others from security threats, fraud, abuse or unlawful activity.
Data retention
Local tournament data remains on the Android device until removed through available Tournament OS controls or Android application-data controls. Tournament OS includes a Delete draft control for draft tournaments. All locally stored Tournament OS application data can also be removed through Android app-storage/data controls or by uninstalling the app, subject to Android backup and restore behavior.
Cloud account and shared tournament records are generally retained while needed to provide the account and sharing functionality and until the applicable account or cloud tournament is deleted.
KRPA Designs LLC does not currently define a fixed product-level retention period for all infrastructure, security or backup logs. Infrastructure providers may retain operational or security information according to their service-retention practices and applicable legal requirements.
Account and cloud-data deletion
Tournament OS provides an authenticated in-app deletion control through the Cloud account screen. Account-deletion information and an external deletion-request method are also available at the public Tournament OS account-deletion page.
Deleting the authenticated cloud account deletes the Supabase Auth user. Current Tournament OS database relationships also delete tournaments owned by that account and the associated shared matches, public tournament snapshots, tournament memberships, umpire invitations, score commands and tournament command/audit records belonging to those tournaments.
If the deleted user participated in another organizer's tournament, that organizer's tournament is not deleted. The user's membership and directly account-linked score-command records are removed. Supported direct user-ID references on retained records are cleared. Validated tournament results may remain as part of the tournament owner's event history.
An umpire invitation may contain a separate invitee email address that is not automatically removed by the current authentication-user deletion cascade when the invitation belongs to another organizer. To request removal of that address, contact admin@krpadesigns.com.
Deleting the cloud account does not automatically remove local-only tournament data stored on the Android device.
Children and intended audience
Tournament OS is intended for adults, and the Google Play target audience for this release is 18 and over. Tournament OS is not designed as a child-directed account service.
Organizers may enter participant display names while managing tournaments. Organizers should avoid entering unnecessary sensitive information about minors and should use particular care before publishing participant or team information to a public tournament page.
Changes to this Privacy Policy
KRPA Designs LLC may update this Privacy Policy when Tournament OS changes its features, service providers or data practices. The effective date will be updated when material changes are made.
Contact
KRPA Designs LLC
Email: admin@krpadesigns.com
Tournament OS: https://tournament-os.app