League Intelligence uses the minimum account and fantasy-league data needed to operate private, league-aware tools. It does not sell league data and does not request write access to Sleeper.
Google supplies a verified email address and basic display identity during sign-in. League Intelligence stores an internal account record and uses its own secure, HTTP-only session; Google tokens, credentials, and passwords are not placed in league datasets.
When a league is connected, the service reads the provider's league settings, scoring, account names, rosters, completed transactions, picks, drafts, and season history needed to operate that league workspace. Completed transactions are kept as tenant-local market history; there is no separate pilot enrollment step.
Saved trade drafts, GM workspace state, watchlists, preferences, and uploaded constitutions or history files are stored so your work survives between sessions. Exact Trade Lab routes and your stated intent or outcome are a separate, optional account-and-league-scoped ledger; the controls in Trade Lab explain its retention and let you pause or delete it. Historical Trade Pulse responses remain private; no new questions or responses are collected.
As people use the service, it records a limited set of first-party events such as opening Market, completing an analysis, saving a plan, or choosing a usefulness rating. These records use an opaque account hash, league scope, event name, and timestamp; they do not contain the offer's routed assets. Product events are retained for up to 90 days.
Roster, scoring, pick ownership, and completed transaction history are used inside the selected league. Transactions with preserved pre-trade price evidence can inform tenant-local market evaluation; incomplete history remains descriptive. Local price changes stay shadow-only until the published out-of-time release gates pass.
Minimized Market events measure whether managers reach and use an analysis. They support service-quality measurement and future evaluation; they do not train player or pick prices. A usefulness rating is recorded only when the manager chooses a rating.
We process league data to provide the workspace and use limited first-party measurement to maintain and improve the service under the lawful basis that applies to each purpose. Site use is not treated as blanket legal consent. Manager-authored intent and usefulness labels are voluntary; they are never inferred from another manager's actions.
Historical Trade Pulse answers are not delivered to other managers and do not affect league market prices or acceptance estimates. Exact Trade Lab routes and statements remain separate from completed-trade evidence, are never treated as another manager's response, and do not train released prices.
Operational logs, hashed rate-limit identifiers, sync status, and tenant audit events help prevent abuse and diagnose failures without placing emails or provider account IDs in dashboard payloads.
Structured account and league records are stored in a tenant-scoped database. Snapshots and approved uploads use private object storage. Every protected request rechecks the signed-in account and league membership.
Managers receive their own roster-scoped tools. Commissioners can see aggregate operational health and league administration, but the admin endpoint does not return member emails, raw provider user IDs, credentials, or raw manager feedback.
Authentication, hosting, storage, fantasy data, and external football data depend on their respective providers. Each provider processes the limited information needed to supply its service under its own terms.
Account settings can download your memberships, preferences, saved work, proposals, bounded product-event history, and other account-scoped records as JSON. Other managers’ private responses are excluded.
You can leave a league or permanently delete your account from Account settings. Account-scoped private work, product events, and historical Trade Pulse responses linked to your account are removed. Older survey rows from the original league did not store an account link and require an owner-assisted identity check before deletion. Shared league history can remain for other active members.
Operational records are retained only as needed for security, recovery, abuse prevention, and product integrity. No internet service can promise perfect security, so the service uses layered access checks, encrypted transport, private bindings, and recoverable snapshots.