PyRaspPrivacy policy
_Last updated: 15 October 2026_
PyRasp is run by Cyber Naskar, an individual developer based in India. This page says what PyRasp keeps about you, why, and what you can do about it. If anything here is unclear, write to help@pyrasp.com.
The short version: PyRasp keeps what it needs to run your account and show what you build. It has no ads, no third-party trackers and no tracking cookies, and it never sells your data. You can download everything it holds about you, or delete your account, from Edit profile at any time.
Who can use PyRasp
You need to be 13 or older to make an account. Anyone can use Try it without an account: it keeps your edits only in your own browser. If we learn that an account belongs to someone under 13, we delete it. A parent or teacher who thinks this has happened can write to help@pyrasp.com.
What PyRasp keeps, and why
Your account
- Username and display name. Needed to sign in and to show who made what. Both are public.
- Email address (optional). Private: never shown to anyone else. It is used to confirm the address is yours, to send a password reset link when you ask for one, and to tell you when your password or email changes. Nothing else: no newsletters, no marketing.
- Password. Stored only as a salted scrypt hash; nobody, including us, can read it.
- Sign in with GitHub. If you use it, PyRasp receives your GitHub account number, name, username and verified email address, and nothing from your repositories.
- Sessions. A single cookie keeps you signed in for up to 30 days. Each session also records how your browser describes itself (for example "Chrome on Windows"), so you can tell your devices apart. This cookie is strictly necessary for signing in; PyRasp uses no other cookies.
What you make
- Projects and code: your circuits, programs, components, Lab boards, revision history and sensor recordings. These are private unless you share them.
- What you share on purpose: community posts, comments and likes, public components, shared project links, and your public profile at
/u/<username>, which shows your name, when you joined, and your contest results, practice progress, posts and public components. - Contest entries: your daily attempts and submitted code, so they can be judged and ranked. Leaderboards show your name and score.
- Location (optional): if you press "Use my location" in a Lab project's environment settings, the approximate position is saved with that project to drive its simulated weather. You can type any place instead. Weather is looked up by our server from Open-Meteo using the position rounded to about 10 km, so your own address is never sent to them.
- Bug reports: what you write, any screenshots you attach, and details your browser adds (the page, browser, screen size, theme and recent errors), so the problem can be reproduced.
How the site is used
PyRasp counts pages and actions (such as running a build or passing a test) to learn what works. There are no cookies and no third-party analytics for this. A visitor is counted with a code made from their network address and browser, mixed with a secret that changes every day and is then thrown away, so nobody can be followed from one day to the next and the address itself is never stored. When you're signed in, these counts are linked to your account. If your browser sends _Global Privacy Control_ or _Do Not Track_, nothing is counted at all.
Network addresses
PyRasp does not store your IP address. The server uses it briefly to limit how fast requests can come in (against abuse) and to make the daily visitor code above. Request logs record what was asked for, never who asked.
In your browser
Some things stay only in your browser's local storage and never reach PyRasp: the code you edit in the sandbox and on Try it before you save it, and settings such as the light or dark theme.
Who else handles your data
PyRasp uses a few services to run. Each handles only what it needs to do its job for PyRasp:
| Service | What for | What it handles |
|---|---|---|
| Cloudflare | Delivers the site, protects it from attacks, stores bug report screenshots (R2) | All traffic passes through it, including your IP address; bug report screenshots |
| Hetzner | Hosts the server and database, in Nuremberg, Germany | Everything stored on the server |
| Zoho ZeptoMail | Sends account emails | Your email address and the email itself |
| GitHub | Only if you choose "Continue with GitHub" | The sign-in itself, under GitHub's own privacy policy |
| Open-Meteo | Weather for Lab projects | A position rounded to about 10 km, sent by our server, not your browser |
PyRasp does not sell, rent or share your personal data with anyone else, and does not use it for advertising. It would only disclose data if required by law.
How long it's kept
- Your account and what you make: until you delete them, or your account.
- Email records: the list of emails sent to you is kept for 30 days. Links in them are cleared from our records as soon as the email is sent.
- Usage counts: about 13 months, then deleted.
- Backups: the database is backed up daily and the 14 newest backups are kept, so something you delete is gone from backups within about two weeks.
- Server logs: rotated automatically and kept only briefly; they contain no IP addresses.
Your choices and rights
- See and download your data. Edit profile → Download my data gives you one file with everything PyRasp stores about your account: your profile, projects and their full code history, components, contest entries, posts, comments, bug reports with screenshots, and your usage counts. Passwords and session secrets are left out.
- Correct it. Change your name, username or email in Edit profile.
- Delete it. Delete individual projects, posts, comments and components at any time. Edit profile → Delete account removes your account and everything you made, straight away. Your community posts and comments stay so that conversations still make sense, but they are shown as "Deleted user" and are no longer linked to you. If you don't want them kept, delete them before you delete your account.
- Ask. For anything else (a question, a correction, an objection, or a request under your local privacy law), write to help@pyrasp.com. You'll get an answer within 30 days.
Depending on where you live (for example in the EU, the UK or California), you may have further rights under your local law, and you can complain to your data protection authority.
Security
Connections are encrypted (HTTPS). Passwords are hashed, reset and confirmation links are stored only as hashes and expire, and the code the judge runs is isolated from the rest of the server with no internet access. No system is perfectly secure; if a breach ever affects your data, you'll be told.
Changes
If this policy changes, the new version is posted here with a new date. A change that affects how your existing data is used will also be announced on the site before it takes effect.