Somewhere, right now, a list of email addresses and passwords from a site you used years ago is probably being tried on the login pages of other sites. Nobody broke into those other sites. They did not need to. People reuse passwords, so a key stolen from one door often opens many.
The usual advice is to make better keys: longer, stranger, a different one for every door. It is good advice that almost nobody follows everywhere. A more useful question for the people who build the doors is simpler. Why is there a key at all?
A password is a secret two parties have to keep
A password only works because two copies of it exist: one in your head and one, in some form, on a server. You have to keep yours from being guessed, written on a sticky note or typed into a convincing fake page. The company has to keep its copy from leaking. Either side can fail, and when the company fails, it fails for everyone at once.
Careful services do not store the password itself. They store a hash, a one-way scramble that can check a password without revealing it. That helps a great deal. But a hash of a short or common password can still be cracked by guessing, offline, at enormous speed, once the file is out. So a breach of a well-run service still turns into working passwords for its weakest ones, and through reuse, into working passwords somewhere else.
This is not one company’s failure. It is what you get when the thing that proves who you are is a reusable secret, chosen by a person, stored by a server, and valid forever until someone changes it.
Remove the thing worth stealing
There is another way to prove who you are: show that you can read a message sent to an address you control, right now. Do that at every sign-in and there is no lasting secret: nothing to remember, nothing to guard, nothing for a breach to hand out.
That is the trade a one-time code makes. The code is good for one sign-in. A code you used yesterday is worthless today, so there is no reason to steal it and nothing to reuse elsewhere. A password protects the door by being hard to guess. A one-time code protects it by not lasting.
The same logic applies to the token that keeps you signed in after the code. If a server stores that token as is, anyone who reads the database can copy it and walk in as you. Store only a fingerprint of it, and the database holds something that can recognize the token but cannot become it.
How Wave signs you in
Wave Wellness has no passwords. You enter your email address and the app sends you a one-time code; that is the whole sign-in. As the privacy policy puts it, there is no password to lose.
Behind that, the design follows the same rule: keep nothing that would be useful to a thief.
- Sign-in codes and session tokens are stored only as salted hashes. The salt means two identical codes never produce the same stored value, so nothing in the table can be matched against a precomputed list.
- Every access to your record is written to an append-only log, so access can be added to the history but not quietly erased from it.
- Your data is stored in the US on Cloudflare, whose infrastructure is certified to SOC 2 Type II, ISO 27001 and FedRAMP, and it is encrypted in transit and at rest.
None of this is a feature you see. The sign-in screen asks for one thing; the security is in what the system declines to keep.
It also fits the rest of the product. Wave holds things people care about: Wave Age, your lab sheets, your sleep, a private journal. It never sells, shares, licenses or discloses any of it, and it carries no trackers or analytics SDK. A promise like that is only as good as the door in front of it. A password database would be the weakest part of the building, so there isn’t one.
What a code cannot protect
Be clear about the limits, because moving the key does not make it disappear.
Your inbox becomes the key. Anyone who can read your email can sign in as you, so the security of your Wave account is now the security of your email account. Give that inbox a strong, unique password and turn on its own two-step sign-in. That one account protects every service that sends codes to it.
A code can still be talked out of you. Someone posing as support may ask you to read it back. Nobody with a legitimate reason will ever ask for it, and a code you did not request is one to ignore.
An emailed code is also not the strongest form of sign-in there is. Methods that tie sign-in to a physical device resist fake pages better. What the code does well is narrower and very practical: it removes the reusable secret, which is the thing that turns one company’s breach into everyone’s problem.
And an append-only log does not stop anything on its own. It makes access visible after the fact, which is what makes the rules checkable.
The best security is often subtraction. Every secret a system stores is a secret it can lose. So the next time a new app asks you to create a password, it is worth asking why it needs one. Sometimes the safest key is the one nobody ever made.
Wave Wellness is free on the App Store and Google Play. Download it and see how your record is kept today.



