Privacy

This is a practice and interview platform. It stores the least it can while still showing you your own progress. Everything below describes what the running system actually does.

Administrators of this instance can read the code you submit. Do not paste passwords, API keys or other confidential material into the editor.

Who runs this site

codeblocks.studio, reachable at admin.codeblocks.studio@gmail.com or through the contact page. Anything described below as a choice — including what leaves this instance — is ours.

What we store

• Email address — your sign-in identity, and where a password reset would be sent.
• Password hash — a bcrypt hash. The password itself is never stored and cannot be recovered from the hash.
• Display name — shown on the public ranking.
• Role and creation time — whether you are a member, an author or an administrator, and when the account was made.

That is the whole account record. There is no date of birth, no location, no phone number and no employer.

What we store about your work

• Source code — the code you send on every Run and every Submit, kept so your submission history is readable later.
• Verdicts — the result of each submission, with the CPU time and peak memory measured in the sandbox.
• Per-test results — which cases passed and which did not.
• Solve statistics — which problems you have solved, used for your dashboard and the public ranking.
• Design answers — for system-design problems, the saved diagram document and any notes you wrote alongside it.

Administrator access to the code above exists for problem authoring and abuse handling, not for general browsing.

Cookies

There is one cookie, and it only keeps you signed in between visits. No script on the page can read it, and it is not sent on requests coming from other sites. Signing out invalidates it.

No cookie here is used for advertising, measurement or cross-site tracking, because there is none of that.

Network addresses

Your network address is used to rate limit sign-ups, sign-in attempts and code submissions. Those counters are short-lived and expire on their own; they are not attached to your account and are not kept as a history. Server and edge logs may record request addresses for operational reasons.

What leaves this instance

Nothing you write — code or a design answer — leaves this instance. Two things about your account can, and both are things you did on purpose.

• GitHub sign-in — used only to authenticate you. If you use it, GitHub tells us the identity you consented to share.
• Email delivery — over SMTP, used only to send account emails such as a password reset.

There is no advertising network, no analytics or product-measurement tracker, and no session-replay tool. Your data is not sold, rented or shared for marketing, and it is not used to train anything.

Retention and deletion

Your account and your work are kept while the account exists, because both exist to be shown back to you. A signed-in session ends when you sign out and expires on its own if you do not. Rate-limit counters expire in minutes or hours. Compiled artefacts from judging are cached briefly and then discarded.

Ask, and your account and everything attached to it is removed. There is no self-service export yet; if you want a copy of your submissions before deletion, say so in the same request. Use the contact page or email admin.codeblocks.studio@gmail.com.

Changes

If what is stored changes, this page changes with it and the date above moves.