Privacy and data handling
Your draft data stays close to the draft.
Draft Omen is a local application. This page describes what it reads, what it stores, and when it reaches out for public card or draft data.
Local Arena and draft data
Draft Omen reads the local MTG Arena Player.log when Detailed Logs are enabled. The application uses the account identity it finds in that log to keep drafts for separate Arena accounts from being mixed together. Draft state and draft details are processed on the local computer.
Live TUI and plain-watch sessions also write an append-only JSONL audit record for each draft at:
~/.draftomen/audit/drafts/<account-id>/<draft-id>.jsonl
Audit records can include offered packs, pool snapshots, rating sources, scoring configuration, candidate calculations, splash and mana reasoning, the visible recommendation, and the card chosen. They are local evidence for later investigation; they are not sent to this website. Draft Omen does not upload audit logs or automatically delete them. Offline replay, deck building, and benchmarking do not write audit records.
Public data requests and local caches
When local data is unavailable or a refresh is requested, the application can make third-party requests or downloads to 17Lands for draft ratings, color-pair context, and public draft data; Scryfall for card metadata and images; and MTGJSON for set metadata used in card mapping.
Downloaded ratings, card metadata, images, and their request/cache metadata are kept in the application's local data directory so the tool can reuse them and avoid unnecessary requests. The app does not send its local audit history to those services as an audit upload. Each third party has its own terms and privacy practices; Draft Omen does not control them.
This website
This site is a static collection of pages and local assets. No site analytics, advertising trackers, account cookies, or preference cookies are enabled here. The download and repository buttons link to GitHub, and external data-service links above lead to their respective sites; those destinations may handle requests under their own policies.
Questions or corrections
For a privacy question or a data-handling issue, please open a GitHub Issue. Include only details you are comfortable sharing publicly.