Notes · from the person building Mneva
The exit is the product.
You learn what a piece of software really thinks of you at the exact moment you try to leave it.
Everything before that moment is courtship. The onboarding is warm, the empty states are encouraging, the upgrade page is beautifully designed. Then one day you decide to go — and the product you have been trusting with your words shows you its actual face. The cancel button that needs three screens. The retention offer that arrives mid-goodbye. The deletion that is really a deactivation, quietly reversible, quietly kept.
For most software this is merely annoying. For software that holds memory — your promises, your worries, the sentence you only said once, at midnight, to a machine — it is disqualifying. A memory product that makes leaving hard has misunderstood what it is holding. It is not holding engagement metrics. It is holding you.
So Mneva's position is that deletion deserves the same design effort as any headline feature, and the shape it takes is specific: a manifest, then a destruction, then a receipt. First you see, in plain counts, what would go — so consent to delete is as informed as consent to keep. Then it goes. Then you get back a record of what was destroyed — counts, never content — so the ending is something you can hold in your hand rather than take on faith.
The same rule governs the smaller exits. Cancelling a subscription must stop future charges, full stop, with the steps published on the Billing page rather than discovered in a support queue. Withdrawing consent for the sensitive things you have shared must be as easy as giving it — that one is not a design preference, it is Article 7(3) of the GDPR, and it is honoured inside the product, not in the small print. And where a step is still handled by a person rather than a button — some are, and the Privacy page says exactly which — the page says so plainly instead of dressing an inbox up as automation.
There is an honest limit, and it belongs in this essay rather than in a footnote: deletion has edges. Where a provider processed a message, that provider's own retention window applies to its logs, and Mneva's pages name that boundary instead of claiming an erasure that does not reach it. A receipt that overstates what was destroyed would be worse than no receipt at all.
Why build this way, when every growth playbook says friction at the exit is free revenue? Because a door you know you can walk out of is the only kind of room you can relax in. The people Mneva is for — people carrying real things — will not put those things down in a room with a sticky door. The easy exit is not generosity. It is what makes the staying mean something.