Last updated August 20, 2026.
Summary
Code to Play is privacy-first. You can install the extension, write code, unlock plays, and play games with no account and no network. The website, GitHub sign-in, and optional analytics exist so you can manage Pro and see a breakdown in the browser — not to watch you type.
Questions: support@code-to-play.com. Related: Legal and Refund Policy.
What stays in your editor
By default, meaningful line counts, plays remaining, unlock progress, high scores, and play counts live only in the editor (VS Code, Cursor, or another compatible host). We do not receive your source code, file paths, or keystrokes.
Signing in from the activity bar does not upload those totals. Free play keeps working if you never create an account.
Account data
If you sign in on the website or from the extension, we use GitHub OAuth. We store the GitHub account id, display name, email, and avatar so we can show your dashboard and link the editor to the same account. The extension keeps a session token in the editor’s secret storage.
GitHub’s own handling of your GitHub account is described in GitHub’s privacy statement.
Optional analytics
Progress monitoring is off by default. If you turn it on at Analytics and the editor is signed in, the extension may upload a snapshot: lifetime lines, lines by file extension, plays remaining, unlock progress, and per-game play counts and high scores.
A snapshot is sent after a play or unlock, shortly after you write while games are still locked, when you sign in from the editor, or at most every 15 minutes while signed in. It is not sent on each keystroke. This account stores one snapshot; each upload replaces the last. Turn the switch off to stop uploads and delete the snapshot here. Local stats in the editor are not deleted.
Payments
Paid Pro and play-space checkouts are processed by Polar, which acts as merchant of record. Polar receives the billing details needed to charge you, remit tax, and send receipts. See Polar’s privacy policy. We store whether your account has Pro and play-space entitlements so the extension and dashboard can unlock the right features.
Cookies and sessions
The website uses a session cookie after you sign in so we can keep you logged in on this device. We do not use advertising cookies or sell personal data.
How long we keep data, and how to delete it
Account records last while the account exists. An analytics snapshot lasts until you opt out or we delete the account. Email support@code-to-play.com to ask us to delete your account and server-side snapshot. That does not wipe local editor storage; you can reset or uninstall the extension yourself.
Changes
If this policy changes in a material way, we will update the date at the top of this page. Continued use of the site after that date means you have seen the new version.
Bugs or privacy concerns: support@code-to-play.com or GitHub Issues.