How we use your data
Last updated: October 4, 2026
The short version
We help you build Commander decks from cards you already own. To do that we store your card bulk, the decks you save, and minimal account information. We don’t sell your data, we don’t share it with advertisers, and we delete the account data we control on request, subject to the retention periods below. This page explains exactly what we collect, where it lives, and who else can see it.
What we collect
- Account information. When you sign in we receive your email address and a stable user ID from your chosen sign-in provider (Google, Discord, Facebook, or email). If you sign in with a third party, our authentication provider may also retain the display name and profile-picture URL that provider includes in the sign-in profile.
- Your card bulk. The list of Magic: The Gathering cards you upload, paste, or otherwise add to your bulk inside the app.
- Saved decks and deck-building activity. Decks you generate or save, and the commander you currently have selected.
- Pod Mode activity. If you host or join a Pod, we store the table name you choose, the deck summaries you share, game lineups and results, short postgame reviews, and any Pod Dial swap modules you save. A game can retain separate reactions from each participating player plus the final consensus or host-resolved result. We do not send the full decklist you paste into Pod Mode to the room service. Other people with the room code can see the table name, shared deck summaries, aggregate review progress, and results intended for the table; private Pod Dial modules are returned only to the player who created them.
- Billing information. If you subscribe or buy deck credits, our payment processor (Stripe) collects your payment details directly. We never see your full card number. We keep a record of your Stripe customer ID and your current subscription / credit balance so the app knows what you’re entitled to.
- Operational data. Standard server logs (timestamps, IP addresses, user-agent strings) and basic usage events tied to your account ID so we can debug issues and measure feature performance.
If you sign in with Google
Google shares three things with us: your email address, your name and your profile picture. We ask for nothing else. We never see your Gmail, contacts, files or any other Google data.
We use your email to create your account, sign you in, send you emails about your account and match your purchases to you. Your name and picture stay with your account record at our sign-in provider.
This data is stored in Supabase with the rest of your account. It is shared only with the services listed under “Where your data lives” below and only for the jobs described there. Your email goes to Stripe when you buy something and to Mixpanel to link your sessions. TikTok gets a one-way hash of it, never the readable address. We never sell it.
You can delete it at any time on our data deletion page.
What we don’t collect
- Full payment card numbers or CVCs (Stripe holds those).
- Your phone number or government ID. A prize winner may provide a shipping address as described below.
- Your data from other apps or websites you use.
- More data than we need to run the app. The cookies the app itself sets are first-party session cookies that keep you logged in; the analytics and advertising tools we use are described below.
Giveaway entries and prize delivery
When you enter a giveaway, we collect your name, email, state, eligibility acknowledgment, accepted rules version, and entry status. Verified eligible subscribers may also have their account and qualifying payment associated with the entry. Free entry does not require a purchase or account and does not subscribe you to marketing.
Transactional email is sent through Resend. Private entry links and a first-party, HttpOnly cookie let you view your entry. A campaign dismissal is stored on your device and, if signed in, with your account. We use Cloudflare Turnstile to check for automated submissions. We store campaign-specific keyed hashes of network information and a random first-party browser identifier to detect possible repeat entries. We also compare supported email aliases, names, and winner delivery details. Shared-network and shared-browser matches are review signals, not automatic disqualification. These security signals are accessible only to authorized administrators.
Selected winners may provide a card choice and shipping address, or a town or store for local delivery. Matt and authorized administrators use these details to verify eligibility and deliver the prize. Shipping providers receive only delivery information they need. Entry and delivery information is stored in Supabase and is not publicly listed.
If a campaign offers an optional community-deck bonus, we link your verified account to your giveaway entry and retain the submitted deck snapshot, explanation, accepted rules version, and review decision. Your chosen display name, shared deck, and explanation are public; your giveaway email and private bulk are not. Bonus participation does not subscribe you to marketing.
We retain giveaway records to administer the promotion, fulfill prizes, resolve disputes, and satisfy applicable recordkeeping requirements. Contact us to request access, correction, or deletion; records needed for those purposes may be retained. The Official Rules describe any winner-list disclosure.
Where your data lives and who we share it with
We use a small set of service providers to run the app. Each one only sees the data it needs to do its job:
- Supabase: our database and authentication provider. Stores your account, bulk, decks, Pod Mode activity, and entitlement records. Hosted on Supabase’s infrastructure.
- Vercel: hosts the application and processes API requests. Standard server logs pass through Vercel.
- Stripe: processes payments and subscription billing. We send Stripe your email and your internal user ID so renewals can be reconciled. Stripe holds the actual payment-method data under their own privacy policy.
- OpenAI: when you generate a deck, the cards eligible for the build (a filtered subset of your bulk) are sent to OpenAI to produce a deck list. We do not include your name, email, or any other identifying account data in those requests.
- Scryfall, EDHREC, Commander Spellbook, and Archidekt: public Magic: The Gathering data sources we query for card information, archetype themes, and combo lists. These requests are read-only and do not send any of your personal data.
- Google / Discord / Facebook: only the provider you choose at sign-in. They tell us who you are; we tell them nothing else.
- Google Analytics: measures aggregate usage (pageviews and in-app events such as builds and pricing views) so we can see what works. It is not sent your name, email, bulk, or decks.
- TikTok: we run the TikTok Pixel on our pages for advertising measurement. It records pageviews and key events (sign-ups, deck generations, checkouts, and purchases) and sets TikTok cookies and identifiers in your browser. To match those events to ads you may have seen, we also send TikTok a one-way SHA-256 hash of your email address and your user ID, never your email in readable form, and never your bulk or decks. TikTok’s use of this data is governed by their own privacy policy.
- Mixpanel: our product-analytics and session-replay provider. Mixpanel records a replay of how you interact with the app — the pages you visit and where you click, scroll, and navigate — so we can diagnose problems and improve the product. These recordings mask all on-screen text and every form input by default, so a recording shows layout and interactions but never the actual characters you type (such as your email or a magic-link) or rendered account details. When you sign in we associate your recorded sessions and product events with your user ID and email so we can support your account. Mixpanel is not sent your cardbulk contents, full payment details, or readable form inputs. Mixpanel’s use of this data is governed by their own privacy policy. You can prevent session-replay recording with browser privacy tools or extensions that block analytics scripts; doing so does not affect your ability to use the app.
- Cloudflare Turnstile: a bot-protection challenge we run on sign-in and other abuse-sensitive forms to keep automated abuse off the service. To tell humans from bots it collects technical signals from your browser and may set a Cloudflare cookie. It is not sent your name, email,bulk, or decks. Cloudflare’s use of this data is governed by their own privacy policy.
We do not sell your personal information, and we do not share it with data brokers. Aside from the analytics and advertising measurement described above, we do not share it with any party not listed here. If we ever add a new service that touches your data, we’ll update this page first.
Local storage in your browser
To make the app responsive, your browser caches a few things locally: your card bulk (so the deck builder doesn’t have to re-fetch on every page), the most recently generated deck (for 24 hours), your selected commander, and a random Pod seat token plus rotating recovery code that lets you return to the same guest seat. Full lists imported for Pod Mode are encrypted with a key stored by your browser and saved in IndexedDB on that device so local analysis and Pod Dial can resume without putting the list in the room payload. Clearing browser storage removes the key, seat recovery information, and these local cache copies. Server-side bulk, deck-summary, and Pod data is handled as described above.
How long we keep your data
We keep your account, bulk, saved decks, and Pods you host for as long as your account exists. Pod activity submitted to somebody else’s room remains with that room unless you ask us to remove it. Server logs and operational telemetry are retained for up to 90 days. Session replays and product-analytics events held in Mixpanel are retained according to our Mixpanel data-retention settings. Stripe retains billing records for longer per their own legal requirements; we don’t control that retention.
Your rights
You can, at any time:
- Access your data. The app displays yourbulk, saved decks, and account status. Email us if you want a broader, machine-readable export.
- Correct your data. Card bulk libraries and saved decks are editable in the app.
- Delete your account. Use our data deletion page to request removal of your account, bulk, decks, and Pod Mode activity connected to you, and entitlement records, or email us at the address below. Billing history may survive in Stripe for legal/tax reasons.
- Cancel your subscription. You can cancel at any time from your Stripe customer portal; the subscription remains active through the end of the current billing period.
Children
The app is not directed at children under 13 and we do not knowingly collect information from anyone under 13. If you believe a child has signed up, contact us and we’ll remove the account.
Security
All traffic between your browser and our servers uses HTTPS. Data at rest is stored in Supabase, which encrypts data on disk. We configure row-level security so signed-in users can access only their own bulk, deck, and entitlement records through the database APIs.
Changes to this policy
If we change anything material about how we handle your data, we’ll update the “Last updated” date at the top of this page and, for significant changes, give existing users notice by email.
Contact
Questions, deletion requests, or anything else about this policy: matt@builtfrombulk.com.