Privacy Policy

Your XP, streaks, badges, and lesson progress are stored in your browser’s local storage, on your device. Code you write in lessons and the playground also runs entirely in your browser. None of this is sent to us unless you sign in and choose to sync.

Signing in is optional. If you create an account, authentication and progress sync are handled by Supabase, our backend provider: we store your email address (or the identity from Google sign-in) and a copy of your learning progress so it can follow you across devices. The session that keeps you signed in lives in cookies. We do not sell or share this data, and we collect nothing beyond what sync needs.

Contact, feedback, and problem reports are relayed to us by email. A submission includes only what you type into the form, plus the page it was sent from. Providing your name or email in those forms is optional — leave them blank and the message still reaches us, we just cannot reply.

Here is everything Whetcode keeps in your browser:

• Progress data — XP, streaks, badges, and completed lessons, in local storage.
• Your preferences — your theme choice and your cookie-banner answer, in local storage.
• A sign-in session — only if you sign in: cookies that keep you authenticated with Supabase.

When you first visit, a consent banner asks how you would like to proceed, and the answer itself is remembered locally so we only ask once. Whetcode runs no ad trackers and nothing that follows you to other sites. We do use Vercel Web Analytics to count page views — described in the next section — which sets no cookies at all, so there is still nothing cookie-related for you to switch off.

To clear everything, delete this site’s data in your browser’s settings (usually under Privacy, then Site data). Note that clearing storage also erases local progress that has not been synced to an account.

Local data: clear the site’s browser storage as described above — it is gone immediately, and we never had a copy. Account data: sign in and stop using the account, then ask us via the contact page to delete it; we will remove your account and synced progress from Supabase.

To know which lessons are being used and which are being abandoned, we count page views with Vercel Web Analytics. To know whether pages are actually loading quickly for you, we also measure page speed with Vercel Speed Insights. Both are deliberately the least invasive options we could find:

• No cookies. Nothing is stored on your device for this, so it cannot follow you to any other website.
• No personal data. Visitors are counted using a hash derived from the request, which is discarded after 24 hours. It cannot be traced back to you, and it is not linked to your account if you have one.
• What is recorded: the page URL, the referring site, approximate location (country and region, from the request — never GPS), device type, browser, and operating system.

Speed Insights is narrower still: it reads standard performance timings the browser already measures (how long the page took to render and respond) and reports them with the route, country, device, browser and connection type. It stores no visitor identifier at all, not even a hash, so its measurements cannot be grouped into a session or linked back to anyone.

The code you write never goes near either of them. It runs in your browser and is never sent to any measurement service. If you would rather not be measured at all, any standard content blocker will stop both, and the site works exactly the same with them blocked.

Whetcode is free until November 30, 2026, and collects no payment information during that time. When subscriptions launch, payments will be handled by a dedicated payment processor — card details will go directly to that processor and will never be stored on Whetcode’s servers. This policy will be updated with the processor’s name and details before any payment is taken.

This is a content matter rather than a privacy one, but it belongs in any honest disclosure: Whetcode’s learning content is generated with the assistance of AI and reviewed for quality, and errors are possible. The full statement lives in our Terms of Use. Nothing you type into lessons or the playground is used to train AI models.

If what we store or how we store it changes, this page will be updated and the “Last updated” date revised. Material changes — say, adopting a tool that did set cookies or collect personal data — would also be reflected in the consent banner before taking effect.

Questions about your data? Reach us through the contact page.