Privacy Policy

Anonymous device identifier. When you first visit, we set an mf_uid cookie so your browser can build and keep a ranking history without an account.

Account information. If you create an account, our authentication provider, Clerk, handles your email address and profile details. When you sign in, your anonymous comparison history is migrated onto your account so nothing is lost.

Comparisons. Every head-to-head pick you make — which dish won, which lost, and when — is stored and tied to your anonymous or account identity. This is the core dataset that powers the leaderboards, and we keep it because deleting or summarizing it would break the rankings built on it.

Content you submit. Dish photos you upload are stored with Supabase Storage. Dish name suggestions and restaurant reports are stored with your submission.

Site analytics. Restaurant pages record first-party events — page views, impressions, and clicks to a restaurant’s website or map listing — tagged with your anonymous visitor id. This powers the business dashboards restaurant owners see for their own claimed page. We filter out known bot traffic before it’s recorded.

To run the comparisons that build dish leaderboards and Crave Scores, to keep your ranking history attached to you across sessions and devices, to show restaurant owners how their page is performing, to investigate and remediate fraudulent or manipulated voting, and to operate and improve the site generally.

We send transactional emails tied to your account, such as sign-in and security notices — these are part of operating an account and aren’t a marketing choice.

We may also send marketing email, like a monthly roundup of Las Vegas dish rankings. We only send marketing email to people who’ve opted in, every marketing email includes a one-click unsubscribe link, and unsubscribing never affects your account or your rankings.

We don’t sell your data to third parties. We do use a small set of service providers to run the site, each handling only the data needed for its job:

• Clerk — account authentication and profile data, for signed-in users.
• Supabase — storage for dish photos you upload.
• Vercel — hosting and infrastructure for the site itself.
• Google Maps — restaurant location and place lookups.

A claimed restaurant’s owner can see aggregate analytics for their own page (views, clicks) through the business portal — never your individual identity or ranking history.

If you delete your account, we remove your personal identity from our systems. Your comparisons themselves may be retained in de-identified form, because the leaderboards other users see are built from the full history of comparisons and removing that history would misrepresent rankings that other people relied on. What’s retained is stripped of anything that identifies you personally.

The mf_uid cookie is essential to how the site works — it’s how anonymous ranking history is kept without an account. Clerk sets its own cookies for signed-in sessions when you have an account.

We may update this policy as the product changes. When we do, we’ll update the effective date at the top of this page.

Questions about this policy or your data? Use the feedback button on the site to reach us.