Privacy

Last updated September 2026

What we store

Your display name, which track you practice, how you answered the "where are you starting from" question, your answers, every version of the code you run including drafts you have not finished, which challenges you solved and which ones you asked the coach about, the hints you were given, and when you practiced. Each profile also has a short internal id we generate for you; you never type it and you never see it.

If you sign in, we store your email address, and for Google sign-in the account identifier Google gives us. Each device you sign in on gets a random key, and we store only a hash of it, never the key itself. We count how many coach questions you ask each day so the daily limit can be enforced.

Cookies and local storage

We set no cookies of our own. Your browser keeps your profile id, device key, chosen track and sound setting in local storage so the site works. Google Sign-In sets its own cookies when you use it, and its script is loaded only when you tap Continue with Google, never before.

Code that runs in your browser

The editor and the code runtimes (Python, SQL and TypeScript run inside your browser, not on a server) are open-source libraries. The runtimes are served through honecoding.com. The editor's modules load from esm.sh, a public module host, only once the editor is on your screen; it receives the same standard request data any web server does. Nothing you type is sent to either.

How long we keep it

Your profile and code history are kept until you ask us to delete them. Sign-in links are deleted once they are used or expired.

What we do not do

We do not sell your data, run ads, or share your answers or code with anyone for marketing. We only have your email if you signed in with email or with Google. We use it to sign you in, and to send a daily reminder only if you turn that on yourself.

The coach

When you ask the coach, we send the part of your code you selected, the rest of the file, the challenge you are working on, any failing test output, your track, a rough skill level, and the hints you were already given on this challenge. That is what it needs in order to give a hint instead of an answer. Do not paste secrets or personal data into the editor.

Who else sees your data

The company whose model powers the coach, for hints. Google, if you use Google Sign-In, to verify it. Vercel, Turso and Cloudflare, who host the site, the database and the DNS, and who may log standard request data such as IP address and browser type.

Seeing or deleting your data

Email hello@honecoding.com from the address you signed in with and we will send you a copy of your record or delete it. If you never gave us an email, sign out on the device: the profile has no way to identify you, and a display name is not enough for us to safely delete anyone's record.