← MTG Trackers

Privacy

MTG Trackers collects the information visitors choose to submit through tracker forms, including serial number, source links, evidence images, notes, prices, dates, and optional finder names.

Submitted reports are stored for admin review. Approved details may become public on tracker pages when they help document a discovered serialized card. Avoid submitting private contact details, addresses, payment details, or anything you do not want reviewed by site admins.

The site uses Vercel hosting, Vercel Analytics, Vercel Speed Insights, and Upstash Redis or Vercel KV to run the app, store tracker data, and understand basic site performance.

New evidence files are stored privately in Vercel Blob. Public access requires successful safety checks and admin approval. Uploads are re-encoded to remove embedded metadata; information visible in the image itself remains. Removing an attachment from an unsent form does not delete the stored file. Contact the site to request file removal. Older externally hosted evidence, where present, is controlled by its hosting provider.

When configured, Cloudmersive receives sanitized image files for malware checks, Azure AI Content Safety receives image derivatives for sexual-content screening, and Google Web Risk receives submitted source URLs for threat checks. Cloudflare Turnstile processes verification and browser signals to reduce automated abuse. Submit only evidence you have permission to share with these services and site admins. Safety checks reduce risk but do not establish a card's authenticity.

Marketplace affiliate clicks and promoted discovery visits may be counted with tracker, source, campaign, card, serial, and page-path context so admins can understand which public pages and promotion channels are useful. These counters do not create visitor accounts or store payment information.

Admin authentication uses a secure session cookie. The public tracker submit flow uses temporary report permissions and IP-based rate limits to reduce spam and protect the review queue. Automatic file retention and deletion are not yet implemented; removal requests are handled through the contact page.

To request a correction or removal of submitted tracker data, use the contact options on the contact page and include enough context for an admin to identify the report.