YOUR INFORMATION. YOUR CHOICES.
Privacy Policy
Here’s what we collect, why we use it, and how you stay in control when you join the league.
Effective October 19, 2026 · Version 2026-10-19.3
1. Who we are and what this covers
Matchup League operates the Matchup League website and app. This policy covers player accounts, league features, our promotional website and privacy requests. The team operating Matchup League is responsible for the information described here. Contact us through the privacy-request form, including if you cannot log in.
This notice explains our current beta features. It does not cover independent websites, app stores or services you visit through external links. Those services have their own policies.
2. Information we collect
- Signup and account access
- Your email, US phone number, birthday and password, a generated account ID, account timestamps and security records. Passwords are stored as hashes, not readable passwords. Session tokens are also stored as hashes. Legacy backup-code hashes may remain stored but can no longer be used. Your birthday is stored separately from your public profile and is used to calculate age and age group. Phone numbers are login identifiers; SMS verification and recovery are available only when a text-delivery service is connected. Recovery challenge records include an account reference, phone number, provider verification ID, attempts and expiry time; we do not store SMS codes. For new signups we record the age group calculated from your birthday, policy, terms and safety versions, acknowledgment time and, for teens, your statement that you have parent or guardian permission. We also record later agreement acceptances, additional teen-profile permission declarations and safety acknowledgments when arranging or starting a matchup. These are self-reported statements, not identity verification or verified parental consent.
- Your player profile and preferences
- Your display name, age, city and state or region, sport, playing role, optional playing level, batting and throwing hand and a short bio; optional fastball velocity, private ZIP code and preferred cage; an optional uploaded profile photo; availability, travel radius and privacy choices. New accounts provide a birthday, which stays private while the calculated age appears on eligible player profiles. Older accounts may still use a previously provided age until a birthday is added. We do not verify birthdays against identity documents.
- Optional device location and photos
- If you choose “Use current area,” the app or browser obtains a foreground location reading and rounds latitude and longitude to one decimal place before sending it to our server. The server stores that approximate area when you save it. We do not collect background location. Adding a ZIP sets your local search area without device-location access. Photos you choose to upload are stored for your profile. Our standard photo editor crops and resizes photos; do not assume all uploaded files have had every piece of embedded metadata removed. Text, photos or meeting venues you provide can reveal a more specific location.
- League and community activity
- Friend requests, friendships, blocks, reviewed Premium video captions, likes, automatic results and Premium announcements, matchup participants, private availability and schedule revisions, validated public facilities, rules, scores, confirmations, disputes, corrections, ratings, notifications, reports and support requests. Historical text posts, comments and matchup messages remain stored but are disabled and excluded from ordinary app access.
- Privacy requests
- The request category, message, reply, status and timestamps, plus a hash of your private request code. Include only the details needed for the request. The form does not require your email, and it does not send email replies.
- Safety reports and moderation
- Report category, content identifiers or URLs, description, signature, authority statement and attestation where requested, status, review deadline, moderator reply, timestamps and a hash of the private request code. Copyright reports may include contact details you provide. Authorized moderators can review every Community publication and submitted video across friends lists and Community privacy settings, inspect reported content, record verified author references, approve or remove publications, moderate profiles, and restrict accounts. We store moderation decisions, reasons, appeals and assigned permissions. Password-based moderators re-enter their password for short-lived moderator access. We store the reason and timing of account restrictions. Basic automated text screening blocks a small set of explicit threats or solicitations; it does not review every image or detect every harmful message.
- Technical and security information
- Session records, notification subscription endpoints and encryption keys if you enable web push, and request information needed to deliver and secure the service. Requests expose an IP address to hosting infrastructure; our application uses hashed IP or identifier-based keys with counters and expiry times to limit abuse. Error logs may contain a request path and error details. Hosting providers also process network and device/browser request information.
- Earlier accounts
- If you use the supported sign-in path for an older ChatGPT-linked account, the hosting identity service provides an account identifier, email and display name. Ordinary email or phone plus password signup does not require a ChatGPT account.
3. Why we use your information
- Create and secure accounts, let you sign in and help with recovery.
- Build your player profile and recommend opponents using factors such as sport, role, age group, level, area, ratings and availability.
- Schedule matchups, record and confirm results, calculate pitcher and hitter ratings and maintain consistent league history.
- Show eligible friends’ activity, support conversations and deliver notifications you enable.
- Handle disputes, reports, privacy requests and support; investigate abuse and protect the service.
- Improve the rating model using league results and aggregate performance patterns.
Recommendations and ratings are generated from player information and recorded results. They are estimates, not verified measures of ability or recruiting decisions. Incorrect scores can be disputed through the matchup.
Public videos and feed order
When video features are enabled, choosing “Public videos” with player discovery on lets approved videos appear to signed-in players outside your friends, including other age groups. Existing friends-only and private choices are preserved. Friends appear first in Community, followed by videos from players whose relevant rating is within approximately 2.11 points on the 1–20 scale, then other public videos. Within the similar-rating group, closer ratings come first; recency orders the other groups. Unrated players use the starting estimate of 9.44 / 20. Blocking, moderation removal, and the privacy of attached matchup scorecards still apply. This setting does not make confirmed matchup results public.
Dismissing a matchup alert saves a preference on this device for your signed-in account so the same alert stays hidden after refresh. The invitation remains in Matchups. Clearing device storage or signing out can clear that local preference.
Featured community updates
Players may choose “Friends + Featured eligibility.” If that player keeps discovery on and reaches the displayed rating, rated-matchup and accepted-friend thresholds, one recent update may be shown to signed-in players outside the player’s circle in a limited Featured section. Friends-only and private posts do not qualify. Featured visibility can cross age groups, and blocks and account restrictions continue to apply. Confirmed matchup results are not placed in Featured.
4. Who can see your information
Player discovery and leaderboards. New profiles start with “Appear in player search” on. Eligible players can see your name, age, city/region, photo, bio, sport, role, level, playing details and ratings. An explicit search matching your name can show your discoverable profile to signed-in players in other age groups. Browsing without a name match and global leaderboards continue to separate players under 18 from adults. Suggested matchups can cross age groups and use compatible roles, similar pitching/hitting ratings and travel preferences. Distances are shown in approximate five-mile bands. Your birthday, ZIP, email, phone and preferred-cage field are not included in public player profiles.
Friends and shared activity. Friend requests can be sent and accepted across age groups. Accepted friends can see posts shared with friends. For nonparticipants, confirmed match results appear in the friends’ feed only when both participants allow result sharing; that audience can include friends of either participant. Participants can still view their own shared results even if result sharing is off. Comments and reactions follow the visibility of the underlying activity, so an opponent’s eligible friends may also see them. Nonparticipants do not receive the match’s venue, rules or private notes through those result-feed records.
Matchup participants. Participants can see private structured availability, meeting details and the scorecard. Matchup messaging, comments, replies and standalone text posts are disabled. While a matchup is accepted and being planned, each participant can see the other’s preferred cage to help agree on a venue; that field is not included in search cards or friends’ result feeds. Conversations are stored on our servers and are not end-to-end encrypted.
Turning off discovery hides your profile from search, recommendations and global leaderboards. It does not hide your profile from existing eligible friends, shared-result or comment audiences, or erase existing friendships, messages, comments or shared match history. Friends-only monthly standings may still include you. Information someone already received remains outside this setting.
Blocking and age groups. Blocking prevents new connections and matchup conversations with that player, removes the friendship, and cancels requested or accepted sessions. It does not erase shared score history or automatically cancel a session already marked live; use the session’s cancel action separately. When a birthday moves someone into the adult group, the teen/adult grouping continues to apply to general browsing and global leaderboards, but does not prevent matchup invitations or play across age groups; friendships and friends-only updates remain available across age groups; discoverable name-search profiles remain available across age groups; historical participant score records remain.
The operating team. Authorized operators can access stored information as needed to run the service. Moderators can review reports, relevant league activity and support or privacy requests. Other users may save or share content they can view; we cannot control their screenshots or copies.
We may disclose relevant information when required by applicable law or a valid legal request, or when reasonably necessary to address fraud, abuse or threats to safety. We do not sell personal information or share it with advertising networks for cross-site targeted advertising. The current app has no advertising or third-party marketing analytics integration.
5. Providers that help operate the service
The service is hosted through OpenAI Sites and uses Cloudflare Workers, database and object-storage infrastructure for application requests, records and photos. These providers process information to host, secure and operate the service. Their infrastructure may process information outside your state or country; this beta does not offer a specific data-residency choice.
If you enable web push, your browser or operating-system push service, such as Apple, Google or Mozilla, processes a subscription endpoint and encrypted notification delivery. Our push payloads use generic notices rather than the text of your private conversations. Delivery also depends on your device settings. Native push registration is not currently enabled in the mobile beta.
Email and text delivery are not currently connected. The app supports Resend for verification and password-reset emails, and Twilio Verify for phone verification and verification codes when configured. Text recovery requires a previously verified account phone number; email recovery sends a link to the account email. Enabled delivery sends the relevant email address or phone number and account-service message or verification request to that provider. The recovery screen shows which methods are available.
ZIP-based search. If you add a ZIP code, our server sends that code alone to Zippopotam.us, which uses GeoNames postal data. We use the returned city, state and area to help find nearby players. Your ZIP stays in your private profile; other players see city and state, not your ZIP or stored coordinates. The area is rounded to a 0.1° grid, so distances are estimates rather than driving distances. You can leave ZIP blank and use city and state, or remove the ZIP in Edit profile.
Cage and facility autocomplete. As you type a facility search of at least three characters, we send the search text and, in home-cage setup, the city and state you entered to Photon, operated by komoot, to search OpenStreetMap place data. We do not attach your account ID, birthday, contact fields or device coordinates to that request. Anything you type in the search text is sent, so do not enter private contact details there. Results are reused for up to five minutes. Expired query text and results are cleared on a later search, cache eviction or worker shutdown; five minutes is not a guaranteed deletion deadline. We also supplement results with a small catalog of facility details from operators’ public websites. Facility links open OpenStreetMap or the operator’s website in a separate page.
6. Cookies, offline storage and device permissions
We use an essential, first-party sign-in cookie with a seven-day validity period. It is marked Secure and HttpOnly. Browser storage holds session/logout markers, cached app files, and data needed for offline play. Offline data can include your profile, settings and ratings, active matchup and opponent details, venue, rules, scores and unsynced scoring drafts. The app rejects older cached snapshots after seven days; that does not automatically erase the files from your device.
Logging out or deleting your account attempts to clear account data from the current device. Other devices can retain cached copies until they reconnect, log out or have their storage cleared; switching accounts can leave user-specific unsynced drafts. Use device storage controls and log out on shared devices. Clearing local storage can permanently remove unsynced at-bats.
Location access, camera or selected-photo access, and device notifications are optional and requested when you use those features. You can deny or revoke permission through your browser or device settings. Revoking a permission does not by itself delete previously saved information; remove your approximate area or photo in the app as well.
We do not use cross-site advertising trackers, and do not change essential service behavior in response to a browser “Do Not Track” signal. The promotional website has no custom advertising or analytics tracking integration; its host still receives the technical information needed to serve pages.
7. How long we keep information and what deletion means
Account, profile and league information generally remains while your account exists, unless you remove it or an operator removes it. We do not currently have a universal automatic deletion period for all stored records. Security tokens expire and cannot be used after expiry. During request-triggered maintenance, we remove expired sessions, email-action tokens, SMS recovery challenges and rate-limit records in bounded batches. Cleanup depends on application activity and is not guaranteed to happen at the exact expiry time.
You can delete your account in Account settings. This removes your profile, birthday, credentials, verified-phone record, recovery challenges, sign-in sessions, policy acknowledgments, agreement history, guardian declarations, account restrictions, preferences, direct rating record, friendships, blocks, authored posts, comments, reactions and messages, and associated account notifications, reports and support requests. It cancels active matchups and queues your stored profile photo for deletion; failed photo deletions are retried.
Some records remain. Shared confirmed or cancelled match history retains results, confirmations and numerical rating snapshots so other players’ histories remain consistent. Your account ID is replaced with a different random removed-player reference in each affected match and its event records; the application does not keep a mapping from those replacement references to your account. Event actions and times remain while details are cleared. Match venue, rules and notes are cleared or replaced. Conversations and feed comments or reactions attached to affected shared matches are removed. Older deleted-account histories are unlinked through bounded background maintenance as the app is used. We retain a restricted deleted-account ID and deletion timestamp to prevent an older sign-in from recreating the deleted account, plus any pending photo-cleanup record until cleanup succeeds. Copies other people made may remain.
These retained references are not guaranteed to be anonymous: an opponent may still associate a past result with you. Hosting backups and operational logs are subject to provider retention and may not disappear immediately when application records are deleted.
Public privacy and safety requests are separate from accounts and remain until the requester uses their request code to delete the request, or an authorized operator deletes it. Independently submitted safety reports can include evidence or verified account references needed to handle the concern; deleting a player account does not erase someone else’s report. Deleting a privacy request does not delete an account, and deleting an account does not automatically delete a separate privacy or safety request. Keep your request code if you want to read or remove that request later.
8. Your choices and privacy requests
In your profile and account settings you can correct profile details, turn off discovery or result sharing, choose feed privacy, remove your saved approximate location, change your phone login identifier, manage notifications, block players and delete your account. You can edit your display name and other editable profile fields; contact support or submit a privacy correction request if your saved birthday is wrong. You can change email when email delivery is connected. Export your information to download or copy the account information held by the application, excluding security secrets and unrelated private records. Account-deletion instructions are available without logging in.
Use Safety reporting for harmful content, child-safety concerns, copyright complaints or nonconsensual intimate imagery. It works without an account and uses a separate private code for replies. Do not upload or send copies of harmful imagery; identify the content with its link or reference.
Use the privacy-request form for questions or requests to access, correct or delete information, obtain a copy, or raise a concern about a child. You can use it without an account. Save the private code shown after submission and return to check for a reply; no email is sent. Anyone with that code can read or delete that request, so keep it private.
Depending on where you live and the laws that apply, you may have additional rights concerning access, correction, deletion, portability or objections to processing. Tell us what you want to request and your jurisdiction if relevant. We may need to verify your identity or authority through an authenticated account or another appropriate method before disclosing or changing account information. An unauthenticated request alone does not authorize account deletion or release of another person’s data. Never send your password or verification code. Some shared records or legally required records may be retained as explained above. You may also raise a concern with the privacy regulator in your jurisdiction.
9. Young players
Matchup League is intended for players age 13 and older. New signup asks for a birthday before enabling contact fields. The server also rejects registration when the supplied birthday gives an age below 13. Players whose birthday gives an age of 13–17 must state that they have a parent or guardian’s permission. Teen profile setup also requires a permission declaration if one is not already recorded. These are self-reported checks; they are not verified parental consent or identity verification.
We do not knowingly permit children under 13 to create accounts. If you believe a child under 13 has provided information, use the privacy-request form and choose the child-privacy category so we can investigate and remove information as appropriate. Parents and guardians can also ask questions there without creating a player account. Friendships require the recipient to accept a request and can cross age groups. Matchup invitations and play can cross age groups. Profile ages are self-reported and do not verify a person’s real age. Discoverable player profiles may be found by name across age groups. Young players should arrange in-person sessions with adult supervision.
10. Security, updates and contact
We use HTTPS, hashed passwords, limited access controls and abuse limits to protect information. No service or device can be guaranteed completely secure. Keep your password and privacy-request code private, use a unique password and report suspected unauthorized account access through Help & support.
Changes in version 2026-10-19.3: added the optional Friends + Featured eligibility setting and explained when one recent update may be shown outside a player’s friend circle. Existing visibility settings are unchanged; friends-only posts and confirmed matchup results remain outside Featured.
We will post revisions on this page with a new effective date and describe material changes when we introduce them. Where additional notice or permission is required, we will provide it. A signup acknowledgment records the version shown at that time; it does not grant permission for unrelated future uses or replace optional device permissions.
For privacy questions, requests or concerns, contact the Matchup League team. For scoring, sign-in or other product issues, visit Help & support.
Moderator review and retention
Community privacy settings control other players’ access; they do not prevent authorized moderator review. Hiding or removing a Community result does not change its underlying scorecard or rating. Removed Community publications are eligible for restoration for 30 days, then are purged during subsequent service activity. Private original videos remain in the uploader’s library until separately deleted. Underlying score history follows the ordinary account-retention rules. Moderation decision records are retained for 12 months, with older records removed during subsequent service activity; scorecard decision history remains with the matchup. Appeals are retained while the account exists. Pilot monitoring records an account’s latest activity time and short categories and times of server failures for 30 days, without copying passwords, tokens, post bodies or payment details into incident records.
Community review and retained history
Only approved Premium videos with captions up to 200 characters, automatic dual-confirmed matchup results, and automatic Premium activation announcements appear in Community. Likes and unlikes are available; user-to-user messaging, comments, replies and text posts are disabled. Historical messages and comments remain stored for existing account-rights, reporting and authorized review processes; this update does not bulk-delete them.
When you submit a clip for publication, the complete uploaded video and its audio, visible text, title and caption may be sent to Google’s Gemini API as the configured review provider. Only submit media with permission from the people shown. Pending, uncertain and rejected submissions remain private to the uploader and authorized reviewers. Review status, caption revisions, appeals and decisions are recorded. Provider processing may temporarily retain a file under the provider’s applicable terms. You may request owner review or revise a submission. AI and human review reduce risk and can make mistakes; approval is not a safety guarantee.
New matchup plans use dates and a facility selected through type-ahead search, without a start/end time or duration. Both participants must confirm the same date-and-place proposal. Previously saved timed schedules retain their details until replaced by a proposal both players confirm. Availability, prior selections and proposal revisions stay on the server for the participants. A pending reschedule does not replace a confirmed schedule until both confirm. Scheduling does not reserve a facility. Account export includes authored historical messages, comments, video-review status and participant scheduling records. Existing account-deletion controls remain available.