1. Information the service handles
Registered accounts include an email address, display name and a password stored using one-way password hashing, not as readable plaintext. Members may also provide league names, team names, team mottos, messages, lineup selections, draft queues, roster changes, trades and other fantasy-league activity.
1A. Advertising inquiries
If you contact us about advertising, we store your business name, contact name, email, optional website, placement preference, budget range and message to evaluate and reply to the request. A one-way keyed digest of the request IP is used for anti-spam throttling. We do not sell this contact information to third parties.
2. Technical records
The web server may retain connection information, including IP addresses, requested pages and timestamps, for operations, security and troubleshooting. The application uses session cookies and request-verification tokens to operate login and protect account activity.
2A. Website analytics
We use Google Analytics 4 to understand visits, page popularity and site performance. Google Analytics may use cookies and process browser, device, approximate-location and website-interaction information. We do not intentionally send account email addresses, page query strings or identifying private-league URLs to Google Analytics. You can control cookies in your browser or use Google's Analytics opt-out browser add-on. See Google's privacy information for details about its processing.
3. Why the information is used
Account information is used to authenticate users and associate their actions with the leagues they join. League information is used to power private competition features, transactions, standings, archival records and commissioner audit logs. Technical records support security and site reliability.
4. Access within private leagues
League members can view other managers' display names, team profiles, league messages and competition data within leagues they belong to. Commissioner audit and administrative features are restricted. Email addresses and password hashes are not part of league exports.
5. External services and payments
The current release does not process payment-card transactions or share payment details with a processor. A real-time NFL provider is not connected. Delayed weekly statistics from nflverse open releases may be used to calculate fantasy points in leagues that select the real-data pool. Future integrations require an updated notice where relevant.
6. Retention, exports and account controls
League rosters, standings, transaction histories and season archives may be retained to preserve competition history. Some league data can be exported through the manager and analytics screens. Self-service account deletion is not yet available in the demonstration build; this must be addressed before commercial launch.
7. Security and limitations
Authentication uses hashed passwords, anti-forgery tokens, restricted private-league access and login throttling. No internet service can guarantee absolute security. Do not publish private information in league messages or team mottos.
8. Privacy-law review
Before a paid public release, the operator should identify its legal entity, contact point, data retention practices, applicable U.S. state privacy rights and any international obligations. This draft should be checked against actual operations by qualified counsel.