Cookie Policy

All three are set by us, on this domain, and all of them exist to make signing in work. Under the ePrivacy rules they are strictly necessary, which is why we do not ask permission for them — without them there is no account, and without an account there is no course.

Each is marked HttpOnly where it can be, restricted to this site with SameSite, and sent only over HTTPS in production.

These are not cookies. They live in your browser’s own storage, are written only as a direct result of something you did on the page — choosing a setting, or typing in the playground — and are never sent to our servers:

• theme — Light, dark or follow-your-system, so the site does not flash the wrong one.
• pylearn:font-size — The text size you chose, applied before the page paints.
• pylearn:playground-draft — Whatever you last typed in the playground, so a reload — or a trip through the signup form — does not lose it. Kept for that tab only, cleared when you close it, and never transmitted.

The Python runtime is also cached by your browser after its first download, the same way any large file on any site is. That is the browser’s own cache doing its job, and clearing it simply means the next lesson downloads the runtime again.

PyLearn advertises on Facebook and Instagram, Google. To know whether that is worth doing we need to see that an ad led to a sign-up rather than guess, and the only mechanism either platform offers for it is their tag — a small script that gives your browser a random id, stores it in a cookie on this domain, and reports a handful of events back. What each one stores is below.

Which way round that works depends on where you are, because the law does. In the UK, the EEA and Switzerland nothing loads until you press Allow — until then the scripts are not on the page at all and no request reaches either company. Everywhere else, including the United States, they load and you are told plainly, with the off switch in the same notice: US privacy law gives you the right to stop it rather than the right to be asked first. Either way the decision sticks, it is remembered in your browser and never sent to us, and turning it off is one click on this page at any time.

What we send is the fact of a page view and, if you buy, that a purchase happened and what it was worth. Not your name, not your email, not your code. What Meta and Google each do with that afterwards is governed by their policies rather than ours.

None, in the sense that matters: nothing on this site sets a cookie on someone else’s domain. The tags above are Meta and Google’s own scripts, but every cookie they write is first-party, on pylearnapp.com.

If you go through checkout, Stripe or PayPal set their own cookies on their own pages — that happens on their domain, under their policies, and is how card payments are made safely everywhere.

Every browser lets you block or delete cookies, and you are welcome to. Blocking the three above signs you out and keeps you signed out; the marketing pages, the pricing page and this one will still read perfectly well.

What we do with the data behind the session is in the Privacy Policy. Anything unclear here, write to support@pylearnapp.com and we will explain — or fix the page.