KnoBallKnoBall Intelligence
Version 1.3 · Effective August 29, 2026 · App Launch Privacy Update
KnoBall helps commissioners and league administrators organize league operations, connect authorized services, review evidence, analyze gameplay and league activity, and create decision-support reports. This policy explains the information KnoBall processes, how it is used, when it may be shared, how long it may be retained, and the controls available to users and authorized league administrators.
Deleting your account: use the in-app "Delete my account" control in the mobile app's account/profile area, or use the account deletion page on knoball.pro. Both paths permanently delete the same account.
This Privacy Policy applies to people who create or use a KnoBall account and to information processed through a league that has been connected to KnoBall by an authorized commissioner or league administrator. It applies to knoball.pro, the KnoBall web application, the KnoBall mobile application (including Android and other supported mobile platforms), and related KnoBall services and integrations (collectively, the "Service").
KnoBall accounts are available to people age 16 or older. Authority-bearing roles and permissions—including league ownership, administration, content publishing, evidence review, member management, and integration configuration—require the account holder to be at least 18 years old.
KnoBall may process email address, username, display name, gamertag, avatar or profile image, authentication identifiers, linked-service identifiers, account preferences, league memberships, roles, and related profile information.
KnoBall may process league identity, teams, rosters, members, schedules, results, standings, transactions, trades, draft information, rules, settings, commissioner procedures, advance schedules, role assignments, and other league configuration or history.
When an authorized commissioner or league administrator enables a Discord connection, KnoBall may process information from the specifically authorized server, channels, and time periods. Depending on the enabled feature, this may include message content, message metadata, attachments, user or role identifiers, and other information available to the authorized integration.
Discord access is configurable. An authorized administrator may select specific channels, a historical range, recurring or advance-to-advance collection, live monitoring of selected channels, or broader monitoring when deliberately enabled. Whole-server monitoring is not the default merely because the technology can support it.
KnoBall may process gameplay video, clips, screenshots, files, evidence notes, timestamps, source information, and other material intentionally submitted or authorized for a KnoBall workflow.
KnoBall may create reports, observations, summaries, classifications, confidence information, gameplay and tendency analysis, rule comparisons, scheduling or league-health signals, structured data, and commissioner-facing recommendations from authorized source information.
KnoBall may process security events, application logs, support communications, technical diagnostics, job status, processing metrics, usage and cost telemetry, IP address, app and operating-system version, device or browser type, network or connectivity information, timestamps, session and login records, crash or error information, security/activity logs, and similar information used to operate, troubleshoot, secure, and improve the reliability of the Service.
When paid features are enabled, KnoBall may process plan status, product or subscription identifiers, purchase or order identifiers, purchase tokens, subscription status, invoices, refunds, usage or premium-analysis balances, and payment-related identifiers supplied by the applicable payment provider, including Google Play Billing when used for an Android purchase. KnoBall does not need to store complete payment-card numbers when the payment provider handles them.
When you use the KnoBall mobile application, KnoBall may process additional information and request device permissions needed to provide the mobile features you choose to use. The mobile app follows the same authorization, use, sharing, retention, security, and deletion principles described throughout this Privacy Policy.
The mobile app may allow you to select, upload, or capture photos, screenshots, gameplay video, evidence, profile media, or other visual content. KnoBall processes photos and videos only when you choose a feature that requires them or intentionally submit that content. Uploaded media may be stored and processed as described in this policy, including through Cloudflare R2 and approved analysis services when needed for the requested function.
The app may request access to your device camera when you choose a feature that captures a photo, screenshot, video, evidence item, profile image, or other camera-based content. KnoBall does not access your camera solely because the app is installed. Camera access is controlled by the permission you grant through your device and can be changed in your device settings.
The app may request microphone access when you choose a feature that records audio or video with audio, or when you start an enabled real-time voice feature. Microphone audio is processed only for the feature you initiate. This may include the audio track of user-recorded video or live voice communication. KnoBall does not activate the microphone solely because the app is installed. Microphone access can be changed in your device settings.
The mobile app may process direct or group messages, community or forum posts, reports, moderation submissions, evidence notes, support communications, comments, images, attachments, files, and other content that you intentionally submit through KnoBall features. This may include content used for league operations, commissioner workflows, support, analysis, social/community features, or safety and moderation.
KnoBall uses Firebase Cloud Messaging (FCM) to deliver enabled mobile notifications such as league activity, commissioner actions, analysis or report status, scheduling information, account or security notices, trade or workflow updates, and other Service alerts.
To route push notifications to your device, the KnoBall app and Firebase may process a device-specific push token, app-instance identifier, or similar device identifier. These identifiers are shared with Firebase/Google as needed for push-notification routing and related delivery functionality. KnoBall does not use these push-routing identifiers to independently build advertising profiles or sell them to data brokers.
You may disable push notifications through KnoBall settings where available or through your device notification settings. Disabling notifications does not delete your KnoBall account or other information stored by the Service.
Camera, microphone, photo/media-library, and notification permissions are controlled through your device operating system. KnoBall requests permissions when they are needed for an enabled feature. You may deny or later revoke a permission in your device settings, although a feature that depends on that permission may stop working until access is restored.
KnoBall provides a native in-app "Delete my account" control under More. A user may use that control to request deletion of the KnoBall account and associated personal data. Users may also initiate deletion through the public account-deletion page at knoball.pro/account/delete. If an account currently owns a league, the league must first be transferred or deleted so ownership is resolved before account deletion can complete.
Deleting or uninstalling the mobile application from a device does not by itself delete the user's KnoBall account or server-stored data. When an account-deletion request is completed, KnoBall deletes or de-identifies applicable account and profile information and associated data, which may include applicable social/community records, user-submitted content, uploads, and stored push-routing associations, subject to identity verification and any limited information that must be retained for an active dispute, security or fraud prevention, legal compliance, accounting, platform integrity, or other legitimate record-preservation obligation described in this policy.
KnoBall currently stores primary application data and generated reports in MySQL. Uploaded video and media are stored through Cloudflare R2 object storage.
KnoBall currently uses Google Gemini as an AI processing provider. Gemini receives information necessary to perform the requested analysis. KnoBall generates analysis instructions from controlled product logic, selected analysis options, and the authorized evidence, rules, settings, and league context.
Google and Discord are currently available for authentication where a user chooses those sign-in methods.
KnoBall may add, remove, or replace service providers as the product develops. Material changes to data practices will be reflected in an updated version of this policy when appropriate.
KnoBall uses AI and other automated logic as decision-support technology. Users select structured analysis options, and KnoBall combines those selections with relevant authorized evidence, league rules, settings, and context to create controlled processing instructions.
AI analysis can be incomplete or wrong. KnoBall may identify, organize, summarize, compare, classify, flag, recommend, or draft. Final consequential league enforcement and discipline remain with the authorized human commissioner or league authority. See our Terms of Service for how AI output relates to final human decision-making.
Private identifiable customer or league content is used to provide the requested KnoBall service and is not automatically designated as permanent model-training data merely because it was processed. Any future deliberate use of such private content for training or a retained evaluation/gold set requires a separately approved permission basis appropriate to that use.
The commissioner or other authorized league administrator controls the league-level Discord connection. Before message-content analysis is enabled, KnoBall is designed to identify the connected server, authorized channels, historical range, capture mode, and enabled purposes.
Authorized Discord information may support scheduling and availability, advance readiness, evidence review, league history, communication patterns, unresolved obligations, notifications, workflow automation, and other enabled commissioner functions.
League administrators are responsible for selecting only the scope and permissions appropriate for their league and for providing appropriate notice to league members before selected Discord message content is processed for enabled league functions.
Supported Discord permissions may be changed or revoked. Revocation stops future collection through that authorization. Existing information is handled under the applicable retention and deletion rules.
KnoBall may provide information to service providers when necessary to operate an enabled feature, including hosting and storage, authentication, AI processing, payment processing, communications, customer support, analytics or reliability tooling, and mobile push-notification delivery. For mobile push notifications, KnoBall may share a device-specific push token, app-instance identifier, or similar routing identifier with Firebase Cloud Messaging/Google so an enabled notification can be delivered to the correct device. Service providers may process information only for the applicable service function and subject to their own legal and contractual obligations.
KnoBall does not sell customer data to data brokers or advertising networks.
KnoBall may disclose information when legally required, when reasonably necessary to protect KnoBall, its users, or the integrity of the service, or in connection with a legitimate corporate transaction subject to appropriate protections.
KnoBall retains information for the time reasonably necessary to provide the authorized feature, preserve useful league history, support an active review or dispute, maintain security and accounting records, or meet legal and platform obligations.
Different categories of information may have different retention periods. Raw source material does not necessarily need to be retained for as long as a final report, ruling, commissioner decision, or useful derived league-history record.
Raw Discord content should be retained only while reasonably needed for the authorized league feature, evidence or review need, or league-history function. New collection stops when the applicable authorization is revoked. Raw API data may be deleted when no longer needed for the stated function or when an authorized deletion request requires it.
Raw uploaded video is intended to expire 30 days after the related analysis or review is finalized, unless the video remains attached to an open dispute or case, is subject to a legal or platform preservation requirement, or an authorized commissioner deliberately marks it for continued evidence retention.
Final reports, commissioner decisions, and useful derived league history may be retained while the relevant league or account remains active or until an applicable authorized deletion request or other retention rule requires removal.
KnoBall does not currently operate a separate application-level backup or archive system intended to preserve a deleted copy of data removed from its active MySQL or Cloudflare R2 stores.
Users and authorized league administrators may request appropriate access to, correction of, or deletion of information associated with them or their league. Requests may be subject to identity, authority, security, legal, platform, dispute, or record-preservation requirements.
Authorized league administrators may also change or revoke supported integration permissions. Revoking an integration stops future collection through that authorization; information already collected is handled according to the applicable retention and deletion rule.
Privacy and data requests: users may use the in-app "Delete my account" control under More, the public account-deletion page at knoball.pro/account/delete, or contact privacy@knoball.pro.
KnoBall uses technical and administrative controls intended to protect its systems and information. No online service can guarantee absolute security.
KnoBall limits external-service access to the interfaces and permissions required for the enabled product function. Connected services do not receive unrestricted access to KnoBall private backend systems merely because an integration is enabled.
KnoBall accounts require a self-reported age of at least 16. Accounts belonging to 16- or 17-year-olds cannot exercise authority-bearing league or platform permissions. KnoBall is not designed as a child-directed account service.
Commissioners and administrators should not submit unnecessary personal information about minors. If KnoBall learns that a connected league includes children under age 13, message-content processing involving those children should be paused and the league routed for manual privacy review before intentional processing continues.
Third-party services remain subject to their own terms and privacy practices. KnoBall's use of connected-service information is also limited by the permissions, rights, and rules of the relevant service. Current or supported third-party functions may include Google and Discord authentication, Google Gemini AI processing, Cloudflare R2 media storage, and Firebase Cloud Messaging/Google for mobile push-notification routing. KnoBall may add, remove, or replace providers as the Service develops, and material changes to data practices will be reflected in an updated policy when appropriate.
A person submitting or connecting evidence or content should have authority to provide it for the requested KnoBall function. Permission to analyze content does not automatically grant unlimited rights to publish, monetize, redistribute, retain indefinitely, or use names, likenesses, trademarks, or copyrighted material for unrelated purposes.
Connection to or compatibility with a third-party platform does not by itself mean that KnoBall is affiliated with or endorsed by that platform.
KnoBall may update this policy as the Service, mobile or web features, connected services, providers, data practices, or legal and platform obligations change. The current version and effective date will be published with the policy. Material changes may be versioned and communicated appropriately, and KnoBall may require renewed acceptance when the nature of a change makes that appropriate.
KnoBall may maintain a record of the policy version accepted by a user, the accepting user or league, and the date and time of acceptance.
When community features are used, KnoBall may process member-directory information, usernames or gamertags, avatars, friend or connection requests, friend relationships, online or presence status, forum/community posts, direct or group messages, image or file attachments, blocked-user records, moderation reports and actions, and support tickets or related communications. KnoBall uses this information to operate community, messaging, safety, reporting, blocking, support, and moderation features.
When an authorized user enables a supported league, game-platform, import, webhook, or synchronization feature, KnoBall may process information made available through that connection. This may include Madden/EA franchise or league identifiers, teams, rosters, players, schedules, results, ratings, contracts, transactions, settings, synchronization metadata, and similar league-management information, to the extent supported and authorized.
On knoball.pro and the web application, KnoBall may use cookies, browser or local storage, session identifiers, and similar technologies for authentication, account sessions, security, preferences, feature operation, and enabled reliability or analytics functions. Where legally required, KnoBall will provide appropriate choices for non-essential technologies. Restricting or clearing these technologies may affect Service functionality.
KnoBall currently uses Firebase Cloud Messaging for mobile push routing. For this function, Firebase/Google may process a push token, app-instance or installation identifier, device/app information, IP address or related technical information needed for registration, routing, delivery, security, and service operation. If KnoBall materially expands Firebase or other mobile analytics, crash, performance, or configuration processing in a future release, KnoBall will update this policy and applicable platform disclosures as appropriate.
When a device registration is no longer needed or an account is deleted, KnoBall removes, deactivates, or disassociates its stored push-routing token or installation association as appropriate. Firebase/Google and other providers may retain provider-side technical records for limited periods under their own retention, backup, security, and deletion practices.
Video, image, evidence, and analysis workflows may create temporary or derived artifacts such as transcoded copies, extracted frames, thumbnails, previews, clips, manifests, hashes, metadata, or analysis references. These artifacts are retained according to the applicable processing, evidence, dispute, security, and derived-data retention needs and are not automatically treated as permanently retained raw source content.
Account deletion applies to applicable account/profile information and associated personal data, including applicable social/community data, user-submitted content, uploads, and stored push-routing associations. KnoBall may retain limited metadata, audit records, hashes, case or report identifiers, decision history, security records, accounting records, or de-identified/derived records when reasonably necessary for integrity, dispute history, fraud prevention, security, legal compliance, platform obligations, or other legitimate record-preservation purposes.
When KnoBall displays or links to third-party media, streams, websites, or embedded content, those third parties may receive ordinary connection and device information when a user opens or interacts with their content. Their handling of information is governed by their own privacy practices.
When Android paid features are enabled, Google Play Billing may process purchases. KnoBall may receive or store product identifiers, order or purchase identifiers, purchase tokens, subscription status, entitlement information, and related transaction metadata needed to provide and manage the purchased feature. Payment credentials are handled by the applicable payment provider.
KnoBall may send transactional, account, security, league, workflow, analysis-status, and other service communications. Where optional promotional or product communications are offered, users may opt out of marketing communications while still receiving essential transactional, account, security, or service messages.
KnoBall does not claim access to device capabilities or sensitive data merely because the app is installed. Device permissions and data categories are requested or processed when required for an enabled feature and as described in this policy. If future releases materially change those practices, KnoBall will update this policy and applicable platform disclosures.
KnoBall provides both an in-app account-deletion path and a public web-based method for initiating account and associated-data deletion:
The deletion process is designed to remove or de-identify applicable user data from active KnoBall systems, subject to the limited retention exceptions stated in this policy. Raw uploaded video follows the retention rule stated above, including the 30-day post-finalization expiration target unless an identified exception applies.
KnoBall Intelligence
Website: knoball.pro
Privacy and data requests: use the in-app "Delete my account" control under More, visit knoball.pro/account/delete, or email privacy@knoball.pro.
Legal entity name and mailing address will be added when the operating entity information is finalized for public legal notices.