Why I Chose Not to Add Password Reset to an Offline Vault App

I saw somebody on Reddit this morning basically arguing that a vault app without password recovery is not very useful.

I understand why people feel that way. We have all been trained by modern software to expect a reset link, an email, a backup code, some kind of escape hatch. If you forget a password, the system is supposed to help you. That is just normal now.

But that expectation starts to break down when the whole point of the app is that it is not built around accounts, cloud services, or somebody else holding onto part of the trust model for you.

That was one of the design choices behind Vaelri Vault™. No account. No cloud dependency. No server somewhere keeping tabs on you. And once you make those choices, password reset stops being some harmless convenience feature and starts becoming a contradiction you have to explain away.

Because what exactly is doing the resetting? That is the part people tend to skip over.

In a normal app, password recovery works because the company knows who you are, or at least knows enough to offer another route back in. Maybe that means email. Maybe it means text message. Maybe it means some recovery workflow tied to an account. Whatever the mechanism is, there is another path.

That is fine for a lot of software. It makes perfect sense for banking, shopping, social media, cloud storage, and all the other systems people use every day.

But if I am building an offline vault app, I do not really want there to be "another path."

I do not want a side door. I do not want a hidden little asterisk where the marketing says your files are under your control, but in practice there is still some recovery mechanism floating around in the background that has to be trusted too.

To me, that changes the product.

It might make it friendlier. It might make it easier to live with. It might even make it a better fit for a lot of people. But it is not the same trust model anymore.

And that is really what this comes down to.

People hear "no password reset" and think missing feature. I hear "password reset" and think, okay, what extra system are we adding, and who is responsible for securing it?

Because recovery is not magic. Recovery is access. It is just access through a second route. Maybe that route is well designed. Maybe it is encrypted. Maybe it is only there for emergencies. But it is still another route, and if your whole pitch is local-only control, that matters.

Now, none of this means people who want password recovery are wrong.

Honestly, for a lot of users, they are making the practical choice. Plenty of people would rather accept a little more dependency in exchange for a safety net. I get that. Most people are not trying to make some philosophical point about trust boundaries. They just do not want to lose their files because they had a bad week and forgot a password.

That is reasonable.

But I do think there is a difference between saying "this tradeoff is not for me" and saying "this kind of app is not useful."

For some users, the lack of password reset is exactly the point.

They do not want their encrypted files tied to an email address. They do not want account recovery. They do not want to depend on a server being there later. They do not want the company behind the app to have any role at all in whether access can be restored.

They want the responsibility, even though responsibility is annoying.

And that is the part modern software has trained people to dislike. Responsibility is not a fun feature. There is no warm fuzzy UX around it. There is just the reality that if you are serious about local-only encryption, some conveniences go away.

That does not make the app broken. It just means the design is honest about what it is.

I would rather be upfront and say, if you forget the password, there may be no way back in, than pretend there is some perfectly safe recovery flow that does not change the basic trust model.

There probably are ways to build softer edges around this. Backup keys, recovery files, other systems. But every one of those comes with its own tradeoffs, and I did not want to quietly smuggle those tradeoffs into a product whose whole point was keeping things on-device and under the user's control.

So no, I do not think a vault app without password recovery is useless.

I think it is a specific kind of tool, built for people who care more about control than convenience, and who understand that those two things do not always get along.

I wrote a more plain-English version of that tradeoff here: When There Is No Password Reset