Privacy Policy

• To create and secure accounts, authenticate users, maintain sessions, and enforce account and team permissions.
• To provide teams, games, statistics, media, chat, notes, sharing, notifications, support, and subscription-based access.
• To process images, video, and audio; produce transcripts and structured sports data; generate coaching insights, highlights, and avatars; and return results to users.
• To screen covered user-generated text and media for prohibited or unsafe content before it is saved or published, and temporarily prevent submission when screening cannot be completed.
• To operate, troubleshoot, measure, and improve the Service and communicate about accounts, support requests, and material changes.
• To detect fraud, abuse, security incidents, repeated violations, and ban evasion, and comply with legal obligations.
• To review reports, protect minors and other users, restrict or remove prohibited content, enforce restrictions or bans, review appeals, and document moderator decisions.

We do not sell personal information or use it for third-party targeted advertising.

• Hosting and Storage: Amazon Web Services stores and processes application content and generated results — S3 holds uploaded and generated media and raw processing files, and Lambda runs image, video, and transcript processing steps. Heroku (Salesforce) hosts the application server, its database, and its backups. Google Firebase hosts the website. A managed Redis instance holds cached values, background-job payloads, and real-time chat delivery in transit; it is working storage, not a system of record, and its contents are transient.
• Authentication and Platform Services: Apple and Google provide sign-in services. Apple also provides iOS platform and push-delivery services, and Google provides Android platform services and Firebase Cloud Messaging push delivery.
• Payments: Stripe processes website subscriptions and payment information.
• AI, Safety Screening, and Transcription: Contracted service providers receive the user content and limited contextual data needed to perform automated safety screening, transcription, extraction, generation, and other supported AI features. Today those providers are OpenRouter (an AI gateway that may route a request to model providers such as OpenAI, Google, and MiniMax) and ElevenLabs (speech-to-text). OpenRouter chat-completions requests from NextPlay, including AWS Lambda processing, are sent with a setting that asks providers not to collect the content for training or storage, where that setting is available. These providers may use subprocessors to deliver their services. Vendors in this category may change; we update this policy when our processing practices materially change. Section 4 explains our automated processing and training practices.
• Notifications: Expo, Apple Push Notification service on iOS, and Google Firebase Cloud Messaging on Android process push tokens, notification payloads, and delivery results.
• Analytics and Diagnostics: Amplitude processes the web analytics and account attributes described above. Sentry processes production server diagnostics and request context.
• Public or User-Directed Sharing: Content set to public, unlisted, team, code, or link visibility is disclosed according to the selected setting. Public and unlisted team and game pages show a site-generated pseudonym instead of a player's real name by default. If a player profile is set to Team visibility, the profile display name and avatar may appear in team contexts, including public team pages.
• Legal and Safety: We may disclose information in response to valid legal process or when reasonably necessary to protect rights and safety, address child exploitation or credible imminent harm, or comply with law. We do not disclose a reporter's identity to the reported user.
• Business Transfers: Information may be disclosed as part of a merger, financing, acquisition, reorganization, bankruptcy, or sale of assets, subject to this policy and applicable law.

The categories above describe the production service providers that may receive personal information from NextPlay. We require service providers that receive personal information to use it only to deliver their services and to maintain privacy and security protections consistent with this policy and applicable law. Processing may occur in the United States or other countries where a provider or its subprocessors operate. Vendors within a category may change as our Service evolves; we update this policy when our processing practices materially change.

NextPlay uses automated systems to screen user-generated content for prohibited or unsafe material, transcribe audio, extract sports information, validate or generate images, and create insights and highlights. These systems may send the content and limited context needed for the applicable function to the service providers described in Section 3. Automated results can be inaccurate; review generated results before relying on or publishing them.

Automated safety screening. Covered user-generated text — team names, player display names, media descriptions, and chat messages — is checked before it is saved. A check may reject content that appears to violate our rules, permit it, or temporarily prevent submission and ask you to try again when screening is unavailable. Text screening is required for those fields and cannot be disabled. Photos and videos are processed after upload: descriptions are screened as text; video may be sampled for automated review; image-file screening depends on a configured media provider and may quarantine, allow, or fail closed depending on configuration.

Training. Xphere LLC does not train or fine-tune any AI model on your content, and we do not sell, license, or otherwise supply your content to anyone as training data. Service providers that assist with automated processing handle content under their terms and our account configuration or agreement with them, and may use subprocessors to deliver their services.

Choices. You can avoid optional AI and voice processing by not using those features. Safety screening is part of submitting covered user-generated content; if you do not want that content processed for safety, do not submit it. You may continue using portions of the Service that do not require that content.

Children under 13 may not create NextPlay accounts. The age gate deletes an account that self-reports as under 13. A parent or authorized guardian who is 13 or older may create their own account and manage a Guardian Profile containing a child's sports information (a private player identity on the guardian's account, not a login for the child). The person creating the Guardian Profile represents that they are the child's parent or are otherwise authorized to provide the child's information and directs us to collect and use it as described in this policy.

Roster entries without a Guardian Profile. Coaches and team administrators can create under-13 roster entries without a Guardian Profile. New roster players default to under-13 unless the coach or administrator marks otherwise, including when a roster is entered manually or imported from an image. That default roster path is how most child sports information is collected. Authorized team users who submit that information represent they have the consent described in the Terms of Service. We do not treat authorized team-submitted child data as unauthorized collection, and we do not delete it solely because it is not attached to a Guardian Profile.

Information about children. Depending on what the guardian, coach, or other authorized team user provides, child information may include the child's name or pseudonym, under-13 status, avatar or photo, team and roster relationships, games, schedules, positions, statistics, events, notes, media, reactions, and the safety information described in Section 1. A Guardian Profile stays private and cannot use the Private, Code, or Team player-profile sharing settings in Section 1. Games and teams the child is on can still be Private, Unlisted, or Public. Public and unlisted team and game pages may show a site-generated pseudonym, under-13 status, statistics, media that follows the game, and a parent/guardian claim prompt. Coaches and authorized team administrators can see roster names alongside those pseudonyms. We use this information to provide and protect the sports features requested by the guardian and authorized team users, and disclose it to the providers and authorized users described in Sections 3 and 5. We do not condition participation on providing more child information than is reasonably necessary for the selected feature.

Guardian controls. A parent or authorized guardian may review or correct a child's Guardian Profile in the Service, delete content where controls are available, or contact us to request access to or deletion of the child's information or to stop further collection or use. We verify the requester's identity and authority before granting access or acting on a request. Deletion is subject to the narrow safety, legal, shared-content, provider, and backup limitations in Section 7.

If we learn that a child under 13 independently created an account or otherwise provided personal information without the required authority, we will take reasonable steps to delete it. Authorized coach or team-administrator roster entries are not treated as unauthorized. Contact us immediately if you believe a child submitted information without authority or that a roster entry was created without the required consent.

We keep each category only as long as the criterion below is met, and we delete, de-identify, or aggregate it once that criterion no longer applies. Where a category has no fixed clock, the stated criterion is the retention rule.

• Account records: Retained while your account exists. Deleting your account removes the primary user record and in-scope account content from active systems immediately, subject to the exceptions below.
• Sports data, media, chat, notes, and sharing records: Retained while the account or the related team or game is active, because the data belongs to a shared team history other members still rely on. Removed when you delete it, when the owning team or game is deleted, or when it falls within a deleted account's deletion graph. That graph includes teams and games you created, even if other people were members.
• Raw voice and live-reporting audio: Retained after transcription while the related team, game, or account is active, so a transcript can be re-derived or corrected. Raw processing files sit in object storage separately from account records, so deleting them can require a separate cleanup — contact us if you need a specific raw file removed.
• Transcripts and extracted actions: Retained on the same basis as the game or note they belong to, because they are the reviewable record of that game.
• Server, request, and security logs: Retained for the period our hosting platform's log retention provides, and beyond that only where a specific security incident, abuse investigation, or legal obligation requires it. These logs are not used to build user profiles.
• Diagnostics (Sentry): Retained for the retention window configured in our Sentry account and deleted on that schedule. We keep error data only long enough to diagnose and fix the fault it records.
• Web product analytics (Amplitude): Retained for the retention window configured in our Amplitude account. Analytics apply to the website only; the mobile apps do not include the Amplitude SDK.
• Push tokens: Retained while the device stays registered. Signing out of the mobile app unregisters the token. A token that Expo reports as permanently unregistered is marked failed and is no longer used for delivery. Tokens are deleted when the account is deleted. Turning notifications off in iOS Settings or Android system settings stops system delivery; the stored token may remain until the app unregisters it, a later delivery fails, or the account is deleted.
• Payment and subscription records: Retained as long as tax, accounting, billing, chargeback, and fraud-prevention obligations require — a period set by law rather than by us, and typically measured in years after the transaction. Stripe retains its own records under its own policy.
• Safety reports, evidence metadata, enforcement actions, appeals, and audit events: Retained after content or account deletion while reasonably needed for safety, appeal review, fraud and ban-evasion prevention, disputes, or legal compliance. Records establishing a permanent ban or relating to child-safety matters are kept as long as the safety purpose lasts, because deleting them would let the banned conduct resume. Access is limited to authorized moderation personnel.
• Deletion and cleanup records: A restricted retry record is kept until provider and attachment cleanup succeeds, then removed. It contains only what the cleanup needs and no user foreign key.
• Backups: Disaster-recovery backups follow our hosting provider's backup lifecycle and are overwritten or expire on that rolling schedule. Deleted information may persist in a backup until it expires, and backups are restored only for disaster recovery, never to reinstate individually deleted data.

If a legal hold, an open dispute, or an active safety investigation applies, we retain the affected information until that matter closes, and then apply the criteria above.

What account deletion actually does

You can permanently delete your account from the iOS or Android app. The website does not currently include a self-serve delete control; email support@nextplay.team and we will delete the account after we verify your identity. Deletion is immediate and cannot be undone. Specifically:

• Your account and content: The primary user record and the account content within its deletion graph are removed from active systems in a single transaction. The Service confirms deletion only after that removal completes.
• Registered devices: Push device registrations are deleted, and your device stops receiving notifications.
• Stored files: Owned avatar, chat-image, and game-media objects are detached, and their original and generated variants are staged for removal from object storage. Because that cleanup runs against an external storage provider, it may continue through a restricted retry record until it succeeds.
• Public and shared content: Content you own that was shared publicly, by link, by code, or with a team is removed when it falls within your account's deletion graph. Share links to it stop resolving.
• Content involving other users: Content owned by another user does not disappear because you deleted your account. A top-level chat message of yours may remain as an identity-free thread tombstone where deleting it would destroy other people's replies; the tombstone carries no name, no identifier, and none of your original text. Teams and games you created are removed, including for other members. Copies other users independently saved or exported are outside our control.
• Apple and Stripe: Where applicable, we revoke the Apple sign-in token and de-link or delete the connected Stripe customer record. Stripe still retains its own transaction history under the payment-record criterion above, because tax and accounting law requires it.
• Provider copies: Content already sent to an AI or transcription provider to fulfill a request you made is handled under that provider's retention terms. We do not hold a copy on your behalf after deletion, and we cannot compel a third-party provider's independent retention schedule.
• Backups: Deleted information may remain in disaster-recovery backups until those backups expire on the rolling schedule described above. We do not restore a backup to reinstate deleted data.
• Safety and legal records: The limited safety, audit, payment, backup, legal-hold, and cleanup-retry records described above may remain, for the reasons and durations stated.

Contact us at the address below if you need help deleting a specific item, a raw processing file, or information held under a Guardian Profile.

Depending on where you live, you may have rights to access, know about, correct, delete, or receive a copy of personal information; object to or restrict certain processing; withdraw consent; or appeal a privacy-request decision. We do not discriminate for exercising applicable privacy rights.

Withdrawing consent and revoking permissions. In short: you can update account and visibility settings in the Service, permanently delete your account from the mobile app or by contacting us, revoke camera/photo/microphone/notification permissions in iOS Settings or Android system settings, and manage website cookies or local storage through your browser. Every optional collection in Section 1.E can be switched off, and each one is switched off in a specific place:

• Camera, photo library, and microphone: revoke in iOS Settings → NextPlay, or in Android Settings → Apps → NextPlay → Permissions. The app can no longer capture or upload new media or audio. Revoking permission does not delete media you already uploaded — delete that content in the Service, or delete your account.
• Notifications: turn off in iOS Settings → NextPlay → Notifications, or in Android Settings → Apps → NextPlay → Notifications, to stop system delivery to that device. Signing out of the mobile app unregisters the push token with NextPlay. There is no in-app notification-off control.
• AI, voice, and safety-screened features: stop using optional AI or voice features to avoid new processing for those features. Safety screening is required when you submit covered user-generated content as described in Section 4; to avoid that processing, do not submit the covered content.
• Sharing and visibility: change a game or player-profile visibility setting at any time. Game media follows the game. Making something private stops new access; it cannot retrieve what someone already saw or saved.
• Website cookies and local storage: manage or clear them through your browser. Website analytics apply only to the website.
• Your whole account: delete it in the iOS or Android app, or email support@nextplay.team from the website, as described in Section 7.

Withdrawing consent applies going forward and does not undo processing that already, lawfully, occurred. Withdrawing a permission the Service needs for a feature disables that feature, not the rest of the Service.

Making a request. You can update available account and visibility settings yourself. For any other privacy request — access, correction, deletion, a copy of your information, objection or restriction, or an appeal of a privacy decision — contact us at the address below. We may need to verify your identity, or your authority over a child's Guardian Profile, before completing a request, and we will say so if we do.

U.S. state privacy rights. Where applicable, you may ask us to confirm whether we process your personal information; access, correct, delete, or obtain a portable copy of it; and appeal our response. You may use an authorized agent where applicable, but we may ask for proof of the agent's authority and may verify your identity directly. We do not sell personal information for money, share it for cross-context behavioral advertising, use it for targeted advertising, or profile users to make decisions that produce legal or similarly significant effects. We therefore do not offer opt-outs for activities we do not perform. We use sensitive information, including account credentials and information concerning children, only to provide, secure, and protect the Service and for other purposes permitted without a right to limit under applicable law.

Browser signals. Because we do not sell or share personal information for targeted advertising, Global Privacy Control and Do Not Track signals do not change how we process information. We do not track users across unaffiliated services for targeted advertising.

How we respond. Describe the right you want to exercise and the account or child profile involved. We will confirm receipt and respond within the period required by applicable law. If we deny a request, we will explain why and, where applicable, how to appeal or contact the relevant regulator. We may deny or limit a request where an exception applies, including where we cannot verify the requester, must protect another person's rights, or must retain information for security or legal compliance.

If privacy law in your location requires a legal basis, we process information as necessary to perform our contract with you and provide requested features; for our legitimate interests in operating, securing, improving, and enforcing the Service, balanced against your rights; to comply with law and protect vital interests; and with consent where required, such as for optional device permissions. Where we rely on consent, you may withdraw it as described in Section 9. Where we rely on legitimate interests, you may object by contacting us.

Information may be processed and maintained outside your state, province, or country, primarily in the United States. Where required, we use legally recognized transfer mechanisms and safeguards. Contact us to ask about the safeguard applicable to a transfer or to request a copy where the law provides that right.

If you are in the European Economic Area or United Kingdom, you may lodge a complaint with the data-protection authority where you live or work, although we encourage you to contact us first so we can try to resolve the concern.