Last updated: 22 November 2026
PySprint is a Python trainer. You read a task, write code and check it in your browser. This page says plainly what the site keeps and what it does not.
The site works in full: lessons open and code is checked. Nothing is written to your device beyond the two cookies described below, and no counter is loaded. No account is created unless you sign up.
Code runs in a separate part of your browser (a web worker with the Python runtime Pyodide, downloaded from a public CDN). Only the results of the checks travel back to the page.
If you allow "Your code", the draft is kept in this browser's local storage, one entry per lesson and language. It never leaves your device. "Reset code" deletes that lesson's draft.
PySprint sets three cookies of its own, and only two of them carry a choice you made:
| Cookie | What it remembers | Kept for |
|---|---|---|
consent |
Remembers whether the site may keep your code and language. Holds only "yes" or "no". | 1 year |
consent-analytics |
Remembers whether visits may be counted. Holds only "yes" or "no". | 1 year |
locale |
Remembers the language you picked. Set only with your permission. | 1 year |
The site session cookie that protects forms is technical and stores no personal data.
An account is optional: the lessons work without it. When you sign up, the site stores your name and e-mail address. The password is stored only as a scrambled (hashed) value that nobody, including the site, can read back.
A new profile can be signed in to only after the e-mail address is confirmed by a letter with a link. At that point the address is marked as confirmed; nothing else about your visits is stored.
If you forget the password, the site sends a similar letter with a link that lets you choose a new one; the link works for an hour and only once. Without permission to keep something in this browser, a new password could not sign you in, so that page explains how to allow it instead.
A profile that never confirmed its address holds no password: it can only be entered through a letter with a link to choose one.
When you are signed in, the lessons you have started or finished and the code drafts you left in them are kept on the server, tied to your account, so they follow you to any device. That is what the account is for.
A visitor without an account keeps the same progress in their own browser, one record per lesson, and nothing of it reaches the server.
Signing out leaves the progress on the account for the next visit; it is deleted with the account.
If you allow "Visit statistics", the site uses the Yandex.Metrika counter to learn which lessons are read and where the site breaks. Yandex sets its own cookies for this and processes the data under its own terms.
Decline it and the counter script is not loaded at all — not a single request is made to it.
No account unless you ask for one, and none is needed to read the lessons.
Your e-mail address is used only for the confirmation letter and the site's notices — never for advertising, and never shown to anyone.
No advertising cookies, no cross-site tracking, no sale of data.
The code you write in a lesson is shown to no one. Without an account it never leaves the browser; with an account it is kept on the server for your own progress, as described above.
Open this page again and use the consent form below: untick a box and save, or press "Reject all". Refusing also deletes what an earlier visit left in this browser.
A visitor in the European Union or the United Kingdom may ask which of their data is held and ask for its deletion or correction. Almost all of it exists only in your own browser and disappears when you clear its storage; the rest is Yandex statistics. Write to the address below and we will answer.
For anything about this policy, write to the site owner through the contacts on pysprint.com.
Your choice is saved in this browser.