Privacy policy
Last updated October 26, 2026
This page describes what Make My Jeopardy stores, who processes it, and what never reaches our servers.
The short version
- You can build and host a board without an account. We never ask who you are.
- Signing in uses Google (or an email link). We learn your email address — there is no password for us to store.
- Payment cards go to Stripe and never touch our servers.
- No ads, no selling data, no advertising trackers. We count page views to see whether anyone is using the site, without a cookie and without following you anywhere else.
Boards you build
A board is the content you write: categories, clues, answers, Final Jeopardy, and any media you attach. Boards are unlisted by default — reachable only through their links, never listed publicly or submitted to search engines. A password-protected board stores only a hash of its password. A private board can be opened only by the signed-in account that owns it.
Media you attach to clues is stored with an unguessable URL, but anyone who has that URL can fetch the file — treat clue images and audio as public once a game has been played.
Playing a game
Players never create accounts. Joining a game means choosing a display name; that name, the score attached to it, and the order of buzzes are stored for the session and shown to everyone in the same game — that’s the scoreboard doing its job. Nothing links a display name to a real identity unless the player types one.
Accounts
An account exists only if you sign in, which is needed only for the dashboard and Pro. Sign-in runs through Google or an emailed link; either way we store your email address, your plan, and — once you’ve been to checkout — Stripe’s identifiers for your customer record and subscription. We never see or store a password.
Messages you send us
The form on the contact page keeps what you write, the email address you leave for a reply if you leave one, and your account if you were signed in. It stays in our own database and is used to answer you and decide what to build next — nothing else.
Payments
Checkout and billing are Stripe. Card numbers go directly to them and never touch our servers; what we keep is the subscription’s status and renewal date. Stripe’s own privacy policy is at stripe.com/privacy.
AI clue writing
Pro accounts can ask an AI to draft clues: Anthropic’s Claude API, or Google’s Gemini API when Claude is unavailable. Generating a whole board sends what you typed to describe it — the category names, or the topic — along with the difficulty and audience; rewriting a single clue sends that clue and its answer. Either way nothing is sent until you press the button, and nothing beyond what that request needs — but don’t put anything secret in a clue you’re about to ask an AI to rewrite.
Cookies and counting
Two cookies of our own. The session cookie keeps you signed in, and is set only when you sign in. The other is set only when you arrive by one of our own links that names where it was posted, such as a link in a Pinterest pin or a video description: it holds that one word (“pinterest”, say) for a week, so that if you make a board we can tell which of our posts led to it. It holds no identifier, and it goes nowhere but back to this site. We set nothing for advertising, and nothing we run can recognise you on another site. Our hosting providers keep standard server logs — IP address, request path — briefly, for security and operations.
We do count page views, using Vercel Web Analytics. It records the page, the referring site, and rough device and country information, and it deliberately does the counting without a cookie and without storing an identifier on your device — so it can tell that a page was loaded, but not that it was you, and not what you did before or after visiting. It runs on every page including the presenter view and players’ phones. It is there to answer whether anyone is using this at all, which is the only question we ask of it.
The exception is the presenter’s screen during Final Jeopardy, which plays the theme by embedding it from YouTube so the rights holder gets the view rather than us hosting a copy. That embed is Google’s, and it may set its own cookies on the machine running the presenter view — never on a player’s phone, which loads no such embed.
Who processes data
Supabase stores the database, auth and uploaded media (on AWS, US region). Vercel hosts the site and counts the page views described above. Stripe handles payments. Anthropic handles AI generation. Google handles sign-in, the Gemini requests that stand in when Claude can’t answer, and YouTube the Final Jeopardy theme on the presenter’s screen. Each processes data only to provide the service.
Retention and deletion
Boards stay until you delete them. To delete your account and everything attached to it, email support@makemyjeopardy.com from the address you signed in with, and we’ll confirm when it’s done.
Changes
If this policy changes materially we’ll update the date above and say so on the site, not just quietly edit history.
Contact
Questions about any of this: email support@makemyjeopardy.com.