Privacy Policy

Snapgame ("we", "us") lets you describe a mini-game idea, generates a self-contained HTML game from it, and gives you a link to share and play with friends. This policy explains what we collect when you use snapgame.co, why, and how it's handled.

You can create and share games without signing up. On your first visit we set a random, anonymous session cookie (sg_anon) — it contains no personal information, only a randomly generated identifier that owns the games you make until you sign in. It's HTTP-only and lasts one year.

Signing in is optional and is handled entirely by our authentication provider, Clerk. We never see or store your password. When you sign in, the games created under your anonymous session are linked to your account so they show up on your dashboard.

• Games you create — the title, the generated game spec, and the generated HTML file, so it can be served back at your shareable link.
• Play activity — aggregate counts of plays, completions, and shares per game. We do not build individual play-by-play profiles of who played what.
• Chat history with the game-building assistant — so you can pick up a conversation where you left off.
• A hashed form of your IP address — a one-way hash, not the address itself — used only to apply daily generation limits and prevent abuse.

What you type to describe a game, and the resulting spec, is sent to an AI model (via Vercel AI Gateway) to generate the game and to a sandboxed code-execution environment (Vercel Sandbox) to produce the final HTML file. We run an automated check on submitted descriptions to catch clearly disallowed content, but this is an automated filter, not human review — don't put anything in a game description or a game you wouldn't want generated or shared.

A published game is reachable only by its link — we don't publicly list or search-index individual games. Anyone with the link can open it, so don't share a link anywhere you wouldn't want the game seen.

To run Snapgame we use a small set of infrastructure providers, each processing only what's needed to do its job:

• Clerk — authentication, if you choose to sign in.
• Neon — the database that stores games, chat sessions, and rate-limit records.
• Vercel Blob — stores the generated HTML files.
• Vercel Sandbox & AI Gateway — run the AI generation that builds your game.
• Vercel Analytics — aggregate, privacy-respecting usage analytics for the site.

We don't sell your data, and we don't share it with anyone beyond what's needed to run the service above.

Snapgame does not currently process payments and does not collect payment information. If we introduce paid plans, this policy will be updated before any payment data is collected.

Snapgame is built for use by teachers, event organizers, and group leaders who create games for their students, players, or teams — but it is not directed at children, and playing a published game never requires an account or any personal information. If you're a teacher or parent using Snapgame with children, you are responsible for that use complying with your organization's policies. If you believe a child under 13 has created an account or provided us personal information directly, contact us and we'll remove it.

• Clearing the sg_anon cookie disconnects your browser from games you made anonymously (they aren't deleted).
• Signing in lets you see and manage everything tied to your account from your dashboard.
• You can request deletion of your account and associated games at any time — see Contact below.

We may update this policy as Snapgame changes. Material changes will be reflected by updating the date at the top of this page.

Questions about this policy or your data? Email hello@snapgame.co.