← Back to First & Metrics

Privacy

F&M collects limited pseudonymous product-usage events to understand how the product is used and to improve it.

Some stored field and schema names still begin with fcc_ — fcc_product_event, fcc_decision_ledger, and the keys this site writes in your browser. Fantasy Command Center was this product's working name, and those identifiers were left alone deliberately: renaming them would break compatibility with records that already exist and with settings already saved in your browser. They are the same product described here, not another service.

This page describes F&M's product-usage telemetry specifically. It is not a description of everything the application handles: F&M obviously reads your league, roster and player data from your fantasy provider in order to work at all. Where a statement below applies only to telemetry, it says so.

Pseudonymous, not anonymous

Two references in each event are replaced with a keyed hash before they are stored — your league reference and a per-visit reference. The key stays on the server and is never sent to your browser.

That makes them pseudonymous, not anonymous. The same league produces the same hash each time, which is deliberate: it is what allows F&M to see that a situation recurred rather than treating every observation as unrelated. We do not describe this telemetry as anonymous, because it is not.

What is recorded

• which F&M surface was displayed
• the state of a decision result — whether there was something to do, nothing to do, or whether F&M could not analyse it and why
• whether the reasoning behind a recommendation was opened
• how many alternatives were shown alongside it
• how long an analysis took, and whether the data shown was current
• the product settings in force at the time, such as the point threshold a recommendation had to clear
• a pseudonymous league reference, a pseudonymous per-visit reference, the season, the week, and which build of F&M produced the event

Every field is a fixed name from a published list. An event containing anything else is rejected rather than stored.

What F&M's telemetry does not store

• No provider credentials. An event containing anything that looks like a credential — a cookie, a token, an ESPN espn_s2 or SWID value — is rejected whole. It is not redacted and partially kept, because a partially-kept record is still a record nobody intended to create.
• No raw league identifier. It is hashed before storage.
• No free text. There is no comment box and no message field in the telemetry schema.
• No raw provider responses. A failure is recorded as a category — "the request timed out" — never as the response body, a URL, or an error trace.
• No player-by-player roster dump.
• No cookies and no browser storage. The per-visit reference lives in memory only and is gone when you close or reload the page. F&M's telemetry sets no cookie and writes nothing to local storage.
• No fingerprinting, no session replay, no screen or keystroke recording, and no advertising identifiers.
• No IP address is stored. Your network address is used transiently by our host to answer the request and, in hashed form, to limit abuse of the collection endpoint. It is not written into the telemetry record.

Settings kept in your browser

Separately from telemetry, the app remembers a few preferences in your browser's local storage so it works the way you left it: your Sleeper username, your colour theme, any ESPN league IDs you added, and — if you entered them — your ESPN cookies.

These stay on your device. They are not telemetry, they are never sent to F&M's collection endpoint, and none of them appears in any stored event. The ESPN cookies are sent only to this site's own proxy, inside a POST body, in order to read your ESPN league on your behalf. Clearing your browser storage removes all of them.

The decision ledger

F&M has an optional research mode, off unless you turn it on in Settings. With it on, each decision card gains a Log decision button. Pressing it saves a snapshot of that decision — what F&M recommended, the projected impact, the evidence behind it and the alternatives it considered — so the decision can be evaluated later against what actually happened.

• It is stored only in your browser. The ledger lives in this browser's local storage under its own key. It is never uploaded, not on a schedule and not in the background.
• It is not telemetry. It does not reach F&M's collection endpoint, shares no fields with the product events described above, and is not part of any beta analysis.
• It leaves your device only when you export it. Export writes a file to your own downloads when you press the button. Nothing else moves it.
• Nothing is logged automatically. Viewing a recommendation records nothing here — only pressing the button does.
• It stores no credentials. A record containing anything that looks like a cookie or token is rejected outright rather than saved, and your raw league ID is replaced with a reference that means nothing outside this browser.
• You can delete it. Settings has a Clear ledger control, and clearing your browser storage removes it too.

What telemetry is used for — and what it is not

It does not affect your recommendations. Telemetry is written after a recommendation has already been produced and displayed. It is never an input to F&M's lineup, waiver or trade analysis, and a telemetry failure cannot change what F&M advises.

F&M cannot tell whether you acted on a recommendation. F&M never writes to your fantasy platform — it makes no claims, no adds, no drops, no lineup changes and no trades. It can record that you opened the reasoning behind a suggestion. It has no way to know whether you then made that move in Sleeper or ESPN, and it does not try to infer it.

Feedback you send us

Some builds of F&M show a Send feedback link in the footer. It is an ordinary link to the F&M owner's own contact address — it opens your mail client or a page you can see. Clicking it sends nothing. Nothing is submitted, and nothing about your session is attached.

• It is separate from telemetry. Feedback you write is not stored with the events described above, is not linked to your pseudonymous league or visit reference, and does not enter the telemetry schema. The schema still has no free-text field of any kind.
• Nothing is attached to it automatically. No league or roster data, no provider response, no ESPN cookies or tokens, no application state, no error trace, no screenshot. Whatever you type is the whole message, and you can read all of it before you send it.
• What we then hold is what you sent us. If you write to us by email, we have your email address and your message, in the same way as any other email. We use it to answer you and to fix what you told us about.

If a build has no such link, the beta's feedback channel is simply the invitation you received — replying to it reaches the same person.

Where it is stored

Events are sent to F&M's own collection endpoint and stored in a private repository controlled by F&M. They are not sold, not shared with advertisers, and not sent to a third-party analytics product.

F&M is served by Cloudflare, which processes the network request itself, and the telemetry archive is hosted on GitHub. Your fantasy data comes from Sleeper or ESPN as applicable, and player market values from FantasyCalc.

Retention

F&M is a small beta and does not currently enforce an automatic retention or deletion schedule for these events. We would rather say that plainly than name a period we do not actually apply.

If you would like the pseudonymous events associated with your league removed, contact the F&M owner and we will remove them.

Changes

If what F&M collects changes materially, this page changes with it. The date at the top is the last update.

This page describes what F&M actually does. It is a factual disclosure for a beta product, and it does not by itself constitute a claim of compliance with any particular privacy regulation.

← Back to First & Metrics