Privacy Policy

This policy covers people who sign in to LessonPlay at lessonplay.space and build games in the studio — typically teachers and other educators.

It does not require anything from students. A published game is a self-contained page shared as a link; playing one needs no account, and we collect no name, email, or score from the person playing it.

• Account details. When you sign up we receive your email address, and — if you use Google sign-in — your name and profile picture from your Google account. We never receive your Google password.
• What you create. The messages you send in the studio, the files you upload as reference material, and the games generated from them.
• Published games. Each time you publish, we store that version's source and its built page, plus a small record of when it was published and the label you gave it.
• Technical logs. Our hosting and database providers record standard request data — IP address, browser type, timestamps — to run and secure the service.

We do not collect payment details, because the beta is free. We do not buy data about you, and we do not run advertising or third-party tracking scripts.

To run the product and nothing more: to authenticate you, to keep your conversations and games available across sessions, to build and preview what you ask for, and to diagnose failures when something breaks. We do not sell your data or share it for advertising.

LessonPlay is built on third-party infrastructure. These providers process your data only to deliver the service:

• Clerk — accounts, sign-in, and sessions.
• Vercel — application hosting, and the AI Gateway that routes prompts to the model.
• Neon — the Postgres database holding your conversations and publish records.
• Cloudflare R2 — storage for uploaded files and published game bundles.
• Daytona — the isolated sandboxes where your game is built and tested.
• The AI model provider behind your session — receives your prompts and any files you attach in order to generate a response.

This one matters, so it is stated plainly. Files you upload and games you publish are stored at long, randomly-generated web addresses. Those addresses are not listed, indexed, or guessable — but they are not password-protected either. Anyone who has the link can open the file or play the game.

That is what makes a game shareable with a class in one link. It also means you should not upload anything you would not be comfortable having a link to — in particular, do not upload documents containing students' personal information.

What you type in the studio, and any file you attach, is sent to an AI model provider to produce a response. Your conversation history is stored so the assistant has context on later turns. Treat the studio as you would any cloud document: do not paste personal data about identifiable students into it.

LessonPlay accounts are for educators and adults. The service is not directed at children, and you should not create an account for a child or on a child's behalf. Because playing a published game requires no account and collects nothing, students can use what you build without ever giving us data.

If you believe a child has created an account, write to us and we will delete it.

We use cookies set by Clerk to keep you signed in — these are necessary for the service to function. Your browser also stores small preferences locally, such as your light or dark theme choice. There are no advertising or analytics cookies.

Your account, conversations, and published games are kept while your account is active, so that you can come back to a game months later. When you ask us to delete your account we remove your conversations, uploads, and published games. Backups and provider logs may retain copies for a short period before they age out.

You can ask us to show you what we hold about you, correct it, delete it, or send you a copy. Email rishabhsingh30july@gmail.com from the address on your account and we will act on it. Deleting your account removes your content — there is no undo, so export anything you want to keep first.

Traffic is encrypted in transit, your data sits behind authenticated access scoped to your account, and generated code runs in isolated sandboxes rather than on our servers. No service can promise perfect security, and this one is in beta — please do not store anything irreplaceable here without your own copy.

LessonPlay is early and changing quickly, so this policy will change too. We will update the date at the top whenever it does, and material changes will be announced in the product.

Questions about privacy, or a deletion request: rishabhsingh30july@gmail.com. See also our Terms of Service.