Security

How your data is handled.

What TodoHen does to look after your account and your tasks, stated plainly, including what it does not do.

Your password

  • Your password is never stored. The server keeps a hash of it made with scrypt, and a random salt that is different for every account.
  • A password must be at least 8 characters.
  • The apps do not keep your password either. After you sign in, they hold a sign-in token instead.
  • Changing it, in Settings › Account, asks for the password you have now, and for a code too if two-step sign-in is on. It signs out every other device.
  • If you forget it, Forgot password? on the sign-in page sends a link to your email address, if the address has been confirmed or the account is less than a week old. The link works once, and for one hour, and choosing a new password with it signs out every device. The page answers the same whether or not an account has that address, so it tells nobody who has one.
  • Wrong passwords are slowed down. They are counted by the network address they come from: after more than ten for one account from one address in ten minutes, the next from that address are refused for ten minutes. After more than a hundred for one account from anywhere in ten minutes, every sign-in to it is refused for ten minutes.

Two-step sign-in

  • You can ask for a second step when you sign in: after your password, a six-digit code from an authenticator app on your phone. It is turned on in Settings › Account, works the same on the web and in every app, and is part of every plan.
  • The codes are the kind authenticator apps make (time-based, a new one every 30 seconds). The server accepts each code once, and after five wrong ones it refuses sign-in to that account from the same network address for five minutes.
  • With it come ten recovery codes, each good for one sign-in in place of a code if you lose your phone. They are shown once, when you turn it on.
  • The key behind the codes is stored encrypted (AES-256-GCM), under a key of the server’s own that is not in the database. Recovery codes are stored as hashes.
  • It covers every sign-in with a password, and a password chosen by an emailed link does not get round it: the code is still asked for.
  • It does not cover a device that is already signed in, which stays signed in when you turn it on, though the last step offers to sign out everywhere else. And it does not cover API tokens, which are made by someone signed in and act without a code.

Your email address

  • The message that welcomes you carries a link that confirms the address is yours. An account works before that, but it cannot buy a plan until the address is confirmed.
  • Changing the address takes your password and a link sent to the new address. The address changes when the link is followed, and the old address is told.
  • The server sends messages about your account and nothing else: confirming an address, a password link, a change to how you sign in or to your plan. Nothing is sent to sell anything.

Staying signed in

  • Signing in gives the device a long random token. The server stores only a SHA-256 hash of it, so the token cannot be read back out of the database.
  • The token is kept in the Keychain on the iPhone and the Mac, in the app’s private storage on Android, and in the browser’s storage for the site on the web.
  • Signing out revokes that token on the server.
  • API tokens, which begin cad_, are kept the same way and shown to you once. They are not signed out with your devices, and they cannot change your password, your email address or two-step sign-in. More about API tokens

In transit

The apps and your browser talk to todohen.illbytes.com over HTTPS, so what travels between your device and the server is encrypted on the way.

On the server

  • To sync, the server stores your tasks and the other things you make: lists, tags, filters, habits, countdowns, focus sessions, templates and the addresses of calendars you subscribe to. Attachments are stored as files.
  • Every request is checked against the account that is signed in. You receive your own records and those of lists that have been shared with you, and nothing else.
  • An attachment is fetched by its identifier, a random id that is given out only inside the task it belongs to, and only to someone who is signed in.
  • A file no task refers to any more is deleted from the server without being asked, a few minutes after the task lets go of it.
  • When the server fetches a subscribed calendar on the web app’s behalf, it goes only to addresses on the public internet, never to its own network, and passes on only what reads as a calendar.

TodoHen is not end-to-end encrypted. Your tasks are stored on the server in a form the server can read. That is what lets it sync them, share the lists you choose to share, and answer the API.

Paying for a plan

  • A plan is paid for on Stripe’s own page. The server sends your browser there and is told the outcome by Stripe: it never sees your card, and stores nothing of it.
  • The server believes Stripe, not the browser. A plan changes only on a message from Stripe whose signature is right.
  • What the server keeps is which plan you are on, and the ids Stripe gives your customer record and your subscription.

The website and the web app

  • Every page is sent with a Content Security Policy that lets it load scripts, styles, fonts and pictures only from todohen.illbytes.com. There are no third-party scripts, no analytics and no adverts to load.
  • The pages cannot be shown inside a frame on another site, and they send no referrer when you follow a link out.
  • The web app never puts the text of a task into the page as markup, so a task cannot carry a script.
  • The web app keeps a copy of your tasks in the browser so that it opens at once. Signing out removes that copy.
  • The web app has no lock of its own, because a browser cannot lock a page the way the apps lock themselves. On a computer you share, sign out when you finish.

On your device

  • The phone and Mac apps can lock themselves behind a four-digit PIN, with Face ID, Touch ID or a fingerprint as a quicker way in. The PIN is never stored: the app keeps a SHA-256 hash of it with a random salt, on that device only.
  • While a PIN is set, the app locks when it starts and when it leaves the screen. On the iPhone its contents are hidden in the app switcher; the Mac app also locks when the Mac sleeps or its screen is locked.
  • The lock keeps someone holding your unlocked phone out of TodoHen. It does not encrypt the app’s data, it does not limit the number of attempts, and it does not hide notifications or the widget.
  • When you import from another app, the file is read on your device. TodoHen does not ask for your password to the other service.

What TodoHen does not do

  • There is no end-to-end encryption.
  • There is no button to delete an account yet. To have an account and its data deleted, write to [email protected] from the address of the account.
  • A forgotten app-lock PIN cannot be recovered.

Reporting a problem

If you have found a weakness in TodoHen, write to [email protected] with what you found and how to reproduce it. Please give us time to fix it before telling anyone else.