Privacy policy

Overload (overload.design) is operated by Joel, India. This page says what we store about you, why, who else sees it, and how to have it removed. It is written to meet India's Digital Personal Data Protection Act 2023 and the EU's GDPR; where they ask for the same thing in different words, we do the stricter one.

What we store

• Account: your email address, a hash of your password (never the password), a public handle, and when the account was created.
• Play: every run you record: the build, its result and score, and how the build changed during the run. Saved builds. Which lessons you have finished and which walkthroughs you have seen.
• How the product is used: which pages and levels you open, when you start and finish runs, which report tabs you read, when a wire is refused, when you share. Stored in our own database, tied to your account when you are signed in and to a random id in your browser when you are not. No advertising identifiers, no cross-site tracking.
• Feedback: what you write in the feedback box and which page you were on.
• Technical: server logs with your IP address and request path, kept for 30 days for security and rate limiting.

Why

To run the game (a score has to belong to someone), to rank the leaderboard, to show a run you chose to share, to make the lessons better by seeing where people stop, to answer feedback, and to keep the service up. We do not sell data, and we do not show advertising.

What is public

Your handle, your best score per level on the leaderboard, and any run whose link you share (the numbers and the shape of the build: which components and wires, not your endpoints, tables or layout). Your email address is never shown.

Who else sees data

• Resend (email delivery) receives your email address when we send a password-reset message.
• xAI (a language model) may receive the paths and descriptions of the API endpoints you type on a level, so they can be matched to the level's features, and the anonymised numbers of a run to write the review paragraph. It does not receive your email, handle or account id.
• Our hosting provider stores the database and serves the site.

Cookies and browser storage

One cookie, sd_session, keeps you signed in. It is essential and is not used for anything else. Browser storage holds your guest progress before you sign up, interface preferences, and the random id used to count visits. There are no third-party cookies.

Your rights

You can see and correct your handle and password on the account page. You can delete your account there; that removes the account, every run, saved build and lesson record, and detaches any feedback you sent. To ask for a copy of your data, or for anything else, write to privacy@overload.design. We answer within 30 days. If you are in the EU you may also complain to your data protection authority.

Children

Overload is for people aged 16 and over. If you believe a younger person has an account, tell us and we will remove it.

Changes

If this policy changes in a way that matters, the date above moves and signed-in players see a notice on their next visit.