Privacy choices
How MTGO Spectator handles optional analytics and advertising.
No account is required
The public beta reads reporting data from the MTGO Spectator service. It does not require an account and does not send database credentials to your browser.
Analytics and advertising
Google Analytics 4 may measure page views only after you allow Analytics. Google AdSense may request contextual, non-personalized in-page banner ads only after you allow Advertising. Full-screen, anchor, side-rail, overlay, and personalized formats are disabled.
No Google Analytics or AdSense script is loaded before the relevant choice. Rejecting optional services leaves the reporting website fully usable.
Account and submission data
Accounts use the MTGO player name already present in Challenge records. Passwords are stored only as one-way hashes, and website sessions are stored only as token verifiers. Account, login, upload, and protected deck pages do not load Google Analytics or AdSense.
Deck uploads are parsed without retaining the raw file. Normalized card rows, a content hash, the selected archetype, and metadata-only lifecycle records are stored. Uploaded card lists are visible only to eligible participants in that Challenge; accepted archetypes may immediately affect public aggregate reports.
Deleting an account removes its sessions, submissions, uploaded cards, and contribution grants. Exact player names remain in historical Challenge results because they are source tournament records.
Storage and withdrawal
Your selection is stored in this browser as a strictly necessary preference. You can change or withdraw it at any time. Withdrawal reloads the page without optional Google scripts and removes accessible Google Analytics cookies for this site.
Google processes optional analytics and advertising data under its published policies. Review Google’s Privacy Policy and how Google uses information from partner sites.