Privacy

What Bezen stores, who else sees it, and how to take it back.

Last updated 7 September 2026

The short version

Bezen stores your account, the answers you submit, and the grades they get. Your answers are sent to an AI model provider to be graded — that is the product. Nothing is sold, and there is no advertising or third-party tracking anywhere in the app. You can download everything or delete your account at any time, without asking anybody.

What is stored

  • Your account — name, email address, and either a password or the fact that you signed in with Google. Passwords are stored only as a bcrypt hash; nobody, including us, can read the original.
  • Your work — the code, designs and written rationale you submit, and the drafts autosaved while you are still working.
  • Your results — scores, the AI’s written feedback, which tests passed, how long an attempt took, and how many hints you opened.
  • Your saved problems and your per-problem progress.
  • Your highlights and notes on Learn pages. Only you can see them.
  • Product analytics — a row each time you view a problem, start practising, submit, or save a problem. These record which problem and when. They do not record your name, your email, your IP address or your answers.

There is no advertising network, no session recording, no fingerprinting and no third-party analytics script on any page.

Who else sees it

  • An AI model provider (currently Anthropic). When you submit, the problem statement, its rubric and your answer are sent to the model to be graded, and the grade comes back. Anthropic states that data sent through its API is not used to train its models by default. This is the one place your answers leave our systems, and it is not optional — it is how grading works.
  • Our host and database provider. They store the data on our behalf and do not use it for anything else.
  • A public CDN (jsDelivr). The Python runtime and the code editor are downloaded from it when you open a coding problem, so it sees your IP address and browser, the same as any file you download from the web. Your code is never sent there — it runs in your own browser.
  • An email provider, for account emails such as a password reset link. Only your address and the message itself are sent.
  • A scheduling provider, and only if you choose to book a one-to-one session. Opening the booking sends your name, your email address and a short summary of your readiness and weakest topics, so the session can start from something specific. Nothing is sent unless you click the button.

Beyond that, nothing is shared, sold, or handed to anybody — except where we are legally required to, which has not happened.

Where your code runs

Code you write in a coding problem runs inside your own browser, in a sandboxed Python runtime. It is not uploaded to a server to execute. What we receive is the code you submit and the results it produced.

Cookies

One cookie: your session. It holds a signed token identifying your account, cannot be read by JavaScript, and lasts 30 days or until you log out. There are no advertising, marketing or analytics cookies, so there is no cookie banner to dismiss — there is nothing to consent to.

How long it is kept

For as long as your account exists. Delete the account and your profile, submissions, drafts, progress, saved problems, highlights and notes are removed from the database immediately — not flagged as deleted, actually removed.

The one exception is the analytics rows described above. They are kept, but the link to your account is severed, so what remains is “somebody attempted this problem on this date” with no way back to you. They contain nothing personal to begin with.

What you can do

  • Take it with you. Download a full JSON export — every answer, grade, draft, bookmark, highlight, note and analytics row held against your account.
  • Correct it. Change your name on the profile page.
  • End it. Delete the account yourself, in the app, immediately. You do not have to email anyone and wait.

Security

Passwords are hashed with bcrypt. Sessions are signed tokens in cookies that JavaScript cannot read. Everything travels over HTTPS. Requests to the expensive paths are rate limited. That said, Bezen is a young product — treat it as you would any small service, and do not put anything confidential into an answer.

Children

Bezen is built for working and aspiring engineers and is not intended for anyone under 16. We do not knowingly hold data belonging to a child; if you believe we do, write to us and it will be removed.

Changes

If this policy changes in substance, the date at the top changes with it. A change that materially affects what is stored or who sees it will be announced in the app rather than made quietly.

Questions about any of this? Write to ani@bezen.in. Back to Bezen