Privacy

Last updated October 2026

What we store

Your display name, which track you practise, 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 practised. Your device also tells us how far its clock is from UTC, a number of minutes and not a location, so your practice day turns at your midnight rather than ours. 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.

If you choose a username, people on Hone can find you by it and send you a friend request, which you answer. Your friends see your username, your streak, your level, how many badges you have and whether you practised today; never your name, your email address or your answers. Invite a friend shares a link with your username in it and a signature that shows it came from you. Nothing is stored when you make one or when somebody opens it, and you hear about it only if they send you a request.

Hone Week

honeweek.com is the planner, on the same account. Your tasks, meaning their titles, days, times, steps, tags, notes, links and whether they are done, are kept on your profile while you are signed in, so they follow you to every device, and only on this device when you are not. Topics coming back for review are worked out from your practice record and are not stored twice.

Notifications work the same way in Hone Week and for the practice reminder in Account on honecoding and honejobs. If you turn them on for a device, your browser gives us an address at its push service, run by Apple, Google or Mozilla depending on the browser, and we keep that address on your profile, with the hour you chose and how far your device's clock is from UTC, including when it next changes for daylight saving, so the notification comes at your hour. A notification is sent as an empty wake-up: the push service never receives what your tasks say or what you practise. Your device asks us for that itself, with its own key, and writes the notification on the phone. A practice reminder comes at most once a day, at the hour you chose, and only on a day a topic comes back for review and you have not practised yet. Turning notifications off, or signing out on that device, removes the address.

If you make a calendar link in the account sheet, any calendar app you paste it into (Google, Apple, Outlook or another) fetches your dated tasks, with their notes and links, from us with that link, as often as the app chooses. The link is a key of its own: it cannot sign you in or change anything, we keep only a hash of it, and you can replace it or turn it off from the same sheet. Signing out everywhere turns it off too.

If you use Say it in Hone Week, your browser turns your voice into words with its own speech recognition, which in some browsers sends the sound to the browser's maker. Hone never receives the sound, only the words that land in the box.

The apps

honecoding, honejobs and Hone Week are also made as apps for Google Play and the App Store, under the names Hone: Daily Coding Practice, honejobs: Career Practice and Hone Week: Weekly Planner, and this section covers each one from the day it is listed. Each app is the same service as its website, with the same account and this same policy. The apps collect nothing of their own: no analytics, no crash reporting, no advertising, no tracking and no third-party SDKs. Google Play and the App Store handle the download under their own policies and show us only counts, such as how many people installed an app, never who you are.

The honecoding and honejobs apps are each a thin shell that shows the site. On Android that is Chrome itself; on an iPhone it is Apple's web view, where you sign in by email, using the link or the six-digit code that comes with it, because Google does not allow its sign-in inside an app's web view. These iPhone apps name themselves in the browser's usual identification (the user agent), and we use that only to leave the Google button out there.

Hone Week for iPhone

Hone Week on the iPhone is a native app, not a shell around the site. It uses the same account and the same tasks as honeweek.com.

Your tasks. Without an account, your tasks stay on the phone, and nothing about them is sent to us. If you sign in, each task outside a private list is sent to us and kept on your profile so it follows you to your other devices and to honeweek.com: its title, day, time, length, steps, the list it is filed under, how it repeats, a day you picked to work on it, its due date, note and link, when it was made and last changed, and whether it is done or marked important. When you remove a task, we are told it was removed, so it goes from your other devices too. In the app you sign in with your email address and a six-digit code we send you. The key that keeps you signed in is stored in the phone's secure storage, and we keep only a hash of it.

Private lists. While a list is marked private, this phone does not upload it. Tasks synced before you marked the list private, or before you moved them into it, stay in your account until you delete the account. A change still waiting to sync when you move a task into a private list is sent too. Mark the list private on each phone you use. Its tasks are also kept out of the copy in Reminders and Calendar, and out of Siri, Spotlight, widgets and notification text. Which lists are private is kept only on the phone, so we never learn that either.

Photos of a plan. If you pick a photo or paste a screenshot of a plan, the words in it are read on the phone by Apple's Vision framework. The image and its text are not sent to us or to anyone else. Only the tasks you choose to add from it are kept, like any other task.

Recently let go. A task you remove is kept on the phone for 30 days so you can bring it back. That copy stays on the phone and is not uploaded.

Face ID. If you turn on the lock, the app asks the phone to check your face, your fingerprint or your passcode before it opens. The phone does that check. We never receive it.

Calendar and Reminders. Only if you allow them. Your calendar events and your reminders are shown beside your tasks and stay on the phone; we never receive them. If you change or tick off one of them in the app, the change is made in your calendar or in Reminders on the phone. If you turn on the link, the app keeps a copy of your tasks in a list called Hone Week in Reminders, and your timed tasks in a calendar called Hone Week, and ticking one off in Reminders or with Siri marks it done in the app. If you import your reminders, you choose which ones to add, and each becomes an ordinary task, which is sent to us like any other task if you are signed in.

Notifications. The app does not use push notifications. Reminders are set on the phone itself, so no notification address is sent to us.

Suggestions on the phone. On iPhones that support it, a few optional suggestions, such as a small first step for a heavy task, are written by Apple's model on the phone. What you write is not sent to us or to anyone else for this. Questions you ask about your week, and the spoken brief of your day, are worked out and spoken on the phone the same way. The app uses no other model and no other company's service for any of it.

Siri and Shortcuts. If you ask Siri or Shortcuts to add or check off a task, the app does it with your signed-in account, and we receive the task the same way as from the app. If you ask Siri what is on today, the app gets your tasks from your account and hands Siri the titles of what is due and how many slipped, so Siri can say or show them. What you say to Siri, and what Siri says back, is handled by Apple under its own policy.

What the app sends us. Your sign-in, your tasks outside private lists while you are signed in, and a request to delete your account if you make one. Like any request on the internet, each one carries standard information such as your IP address, which our hosting providers may log. If you use shared lists, the app also sends what you do on them, described under Shared lists below. Apart from that, at most once a day the app asks the App Store's public listing whether a newer version is out. That request goes to Apple and carries no account and none of your tasks. Test versions from TestFlight make the same check against our website instead. The app has no analytics, no crash reporting and no advertising. In the app, Delete account is under Settings; it deletes the account and what is kept for it on our side, apart from the few things listed under Deleting your account below, and clears the tasks from the phone. Deleting your account is described below and covers the app too.

Shared lists

If you share a list, we store its name, its tasks with their days and times, the name you choose for shared lists, when each person joined, who added each task, and who checked off each one, so everyone on the list sees the same thing. This is the only content we hold for other people to see. A private list cannot be shared. Each shared list also carries a number that goes up whenever something on it changes, so a phone with the list open can ask every 15 seconds or so whether there is anything new. That number says nothing about who changed what, and we keep no record of which phone asked.

Activity. For 30 days we keep a line for each change made on a shared list: who made it (the name they had on the list at the time), what kind of change it was (added, changed, checked off, unchecked, deleted, joined, left or was removed), which task, which part of it changed (its words, its day, its time, or whether it is done), and when. We do not keep what a task said, before or after: Activity shows a task's words as they are on the list now, and a deleted task as "a task". Everyone on the list can see Activity. A line older than 30 days is never shown, and is deleted the next time a change is recorded or Activity is opened on any shared list. A list keeps at most its newest 300 lines.

When you leave a list, or the owner removes you, your name comes off the list, off what you checked off, off the tasks you added and off every line in Activity; tasks you added stay for the others. Any invite link you made stops working. If the owner turns on "Let people on this list invite others", each person's invite link is tied to them, and the owner, and the person whose link it was, can see who joined with it. When the owner makes a new link or turns that off, every link the others made stops working. If the owner hands the list to someone else, every invite link stops, and the new owner decides who joins next. A list holds up to 20 people and 500 tasks that aren't done.

When the owner stops sharing a list, or deletes their account, the list, its Activity and every plan on it are deleted for everyone. Invite codes stop working after 7 days, or sooner if the owner makes a new link; we keep only a scrambled form of each code, and drop it 30 days after its 7 days are up. A deleted task's text is wiped from our servers at once. People on the list see the name you choose for shared lists, never your email or account id.

The rules. Before you share a list or join one, you agree to the rules for shared lists. We keep which version of the rules you agreed to, and when, on your account, so a new phone or a reinstall does not ask you again. We ask again only when the rules change.

Block. Anyone on a list can block a person on it, the owner included. We keep who you blocked, the name they had on the list when you did, and when, so you can see them in Settings and unblock. Blocking hides that person's tasks and name from you, takes you off any list they own, and stops either of you inviting the other. They are not told. If you own the list, blocking is the same as Remove: they come off the list and cannot come back with the old link. Unblocking does not put anyone back on a list. Deleting your account deletes the blocks you made and the blocks made against you.

Reports. If you report a list, a person on it, a task or a plan, we keep the report: which list, what it was about, the reason you picked, any note you write, whether the owner of the list made it, and when. The note is kept as free text, up to 500 characters. The moment you report, the task or plan, or that person's tasks, are hidden from you. They are hidden from everyone on the list once two different people have reported the same thing, or once the owner has. Nobody on the list is told who reported. The report and your note are kept so they can be reviewed. Deleting your account deletes the reports you made.

What we can do. We can delete a task, remove a person from a list and keep them off it, or turn off sharing for an account. When sharing is turned off for an account, it cannot create, join or open a shared list, and everyone else stops seeing its tasks and name. Each of these is written to a log with the time, which report it was for and who did it. The log holds ids and reason codes, never what anyone wrote.

Plans

A plan you save stays on your phone. If you add one to a shared list, we store its name and its items: each item's words, its day or date, its time and how long it takes, its time zone if it has one, and its notes if you choose to include them. We also store who added each item and a version number. Each time the plan changes we keep who changed it and how many items changed, never the earlier items, so people who saved their own copy can see something like "Updated by Sam: 3 changes". Everyone on the list can see the plan. The person who added it, or the owner, can change it or take it off. It is deleted when it is taken off the list, when the list stops being shared, or when the person who added it deletes their account. If they only leave the list, the plan stays for the others and no longer shows who added it.

Cookies and local storage

We set no cookies of our own. This device keeps your profile id, device key, chosen track and sound setting in local storage so Hone works. If you tap Not now on the line that offers the app, it also keeps the day you did, so the line stays away for 30 days. If you open a friend's invite link, it keeps that link for up to a week, until you answer it or sign out. 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 on your device

The editor and the code runtimes (Python, SQL and TypeScript run on your device, not on a server) are third-party libraries. The runtimes are served through honecoding.com. The editor's modules load from 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 delete your account. Sign-in links and codes are deleted within a day of being used or expiring. When an app sends an answer or a solve again because the connection dropped, we keep our first reply for a day so it counts once; the reply holds nothing that is not already in your practice record, and it is deleted after the day or with your account.

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. An optional weekly note about your week stays off unless you turn it on.

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. Resend, which sends our emails, such as your sign-in link and code, so it handles your email address and the message. Our hosting, database and DNS providers, who keep Hone running and may log standard request data such as IP address and browser type. If you turn Hone Week notifications or the practice reminder on, the push service of your browser (Apple, Google or Mozilla), which receives an empty wake-up for your device and nothing else.

Deleting your account

Open Account and choose Delete my account, in an app or on a site, or use the page at /account/delete on any of the three sites. It deletes your account on all three at once: your practice record and answers, streak, levels, badges and certificates; your name, email address and username; your friends, requests and cheers, on your friends' lists too; your calendar; every version of code you ran; notification addresses, reminder and weekly note settings; and sign-in links and codes still waiting. If you cannot sign in, email hello@honecoding.com from the address on the account and we delete it for you. If you never gave us an email, delete it from the device that made it: nothing else can show that the record is yours, and a display name is not enough for us to safely delete anyone's record.

A deleted account leaves the live database at once. Copies kept only to recover from a failure (the database host's restore history, and the backups we download before a risky change) can still hold it for up to 30 days, until they are replaced or deleted. They are never used to bring a deleted account back: if a restore ever returned one, the restore deletes it again. We keep the account's internal number marked as used, so it is never given to anybody else; that mark says nothing about you. Tasks you added to someone else's shared list stay there for the others, without your name. Some safety records about shared lists can stay: reports other people made, and the moderation log, which records reports, blocks and the actions we took by ids and reason codes. They refer to accounts by internal ids, and a report keeps the note its writer typed.

Seeing your data

Email hello@honecoding.com from the address you signed in with and we will send you a copy of your record.

Children

Accounts are for people 13 and over. The page for children at /kids needs no account: it sends us nothing about the child and stores nothing with us, and the puzzle a child reached is kept only in that browser.