Privacy Policy
Last updated: 2026
We collect minimal data necessary to operate the site, including account information, submitted content, and basic analytics. Contact form submissions are stored and emailed to our team for follow‑up.
We use Supabase for authentication and storage. See Supabase’s documentation for details on their data processing. You can request deletion of your account and related content by contacting us.
Our Scout checks selected public feeds and permitted social APIs for potential officiating incidents. Source links, limited excerpts and detection records are used for private editorial review. Where permitted, bounded excerpts may be processed by OpenAI for classification; Scout discoveries undergo independent validation before automatic publication. We do not use social data to profile people or infer their personal characteristics. Contact us about source-content removal requests.
Source media may load official X, YouTube or Vimeo embeds in your browser. Those providers receive connection and browser information and apply their own privacy policies. We use YouTube’s privacy-enhanced player and request do-not-track options for X and Vimeo where supported. Original source links remain available if an embed cannot load.
Questions about privacy? Reach us via the Contact page.
Voting without an account
A signed first-party cookie remembers your anonymous ballot for up to one year. We store a private hash of that random identity, your choice and its question version. To limit repeated voting, we use daily-changing hashes of network addresses and short-lived request counters; raw network addresses are not stored in the voting database. We do not fingerprint your browser. You can change or remove your current vote. If you sign in, we associate the ballot on the page you visit with your account; an existing account ballot takes precedence. Earlier question versions retain their original ballots. Clearing cookies can lose access to an anonymous ballot.
Automated publication and contributions
NuttyRefs can automatically research and publish supported officiating events. Provenance and citations identify automated content. Developer contact addresses and lead payloads remain private; safe agent names may appear on resulting incidents. We retain validation and correction history. Incident pages count views, source opens, accepted votes/comments and share actions using a session identifier hashed separately each day; we do not record raw IP addresses in these event counters. A shared per-post referral token and the referring site category help measure which public posts bring participation. The token identifies a post, not a person. The browser remembers it for the incident during the tab session. Raw engagement rows are retained for up to 31 days, then reduced to daily totals without visitor identifiers. Ballot history is retained separately as described above. X share clicks indicate intent, not proof that someone published a post.