Why I Don't Store Anything

The Decision People Assume Was Hard

Every time I explain how Unheavy works, I get the same reaction. "Wait — so you don't save anything? Nothing at all?" And when I confirm, people usually follow up with one of two things: either "that's actually really cool" or "but how do you improve the product without data?"

I want to address both. Because storing nothing was the easiest product decision I made — and the one I'm most confident about.

What You're Actually Asking People to Do

Think about what happens when someone opens a journaling app to write something hard. They're not writing a grocery list. They're writing the thing they can't say out loud. The thought at 2am that's making their chest tight. The anger they feel toward someone they love. The fear they haven't admitted to themselves yet.

Now imagine that thought is being stored. Synced to a server. Kept in a database. Potentially backed up. Possibly included in aggregate analytics, even if anonymized.

Most people don't consciously think about this. But I think they feel it. And I think it's one reason they start journaling apps and abandon them. The act of writing becomes a performance, even when the audience is just a server farm somewhere.

Storage Changes What You Write

This is the most underappreciated design problem in this category. When you know something is being kept, your brain starts editing before your fingers move. You pick softer words. You leave out the parts you're most ashamed of. You write for a reader — even when that reader is future-you — instead of writing to get it out.

James Pennebaker's research on expressive writing found that the therapeutic effect came from uninhibited disclosure. Not curated disclosure. Not edited disclosure. The relief came from saying the thing you hadn't said, without filtering it. (His foundational work on this, starting in the 1980s, has been replicated across dozens of studies — and the key variable is consistently whether people feel free to write without censorship.)

Storage puts the filter back in.

When Unheavy deletes your words the moment they're destroyed, there's genuinely nobody who will ever read them. Including me. Including any algorithm. That's what lets people write the actual thing instead of a version of it.

The "But How Do You Improve?" Question

Fair question. The honest answer: product intuition, direct conversations with users, and observing what people say about the problem — not what they write in the app.

I don't need to know what someone wrote to know if the product worked. I can ask: did you feel lighter? Did the destruction feel satisfying? Was the drift long enough? That feedback doesn't require storing private thoughts. It requires talking to people.

The assumption buried in the "how do you improve without data" question is that behavioral data is the only useful kind. It isn't. It's the laziest kind, because it lets you avoid actually talking to users. You can optimize engagement metrics indefinitely without ever asking whether the product helped.

The Economics of Storing Nothing

Here's a practical note: storing nothing costs almost nothing.

• No storage infrastructure for a database of sensitive personal thoughts.
• No security audits or breach liability.
• No GDPR/CCPA compliance overhead for personal content.
• No engineering time building data export or deletion flows.
• No feature requests to 'see my history' that I'd have to decline.

The zero-storage model isn't just ethically clean — it's operationally simple. Every architectural decision in Unheavy flows from the same principle: the app exists for the moment you use it, and then it's done.

Why This Connects to Pricing

The no-storage decision is related to the one-time purchase decision. A subscription model creates a misalignment I couldn't resolve. If I'm charging you monthly, I need you to keep coming back. Which means I need to build features that bring you back. Which means I'm optimizing for retention.

And retention-focused thinking is almost always the enemy of a product whose whole purpose is completion. The WRITE → DESTROY → DRIFT loop is designed to end. You do it, you feel lighter, you close the app. That's success. A subscription would quietly push me to make the app stickier, to extend sessions, to find reasons to send push notifications.

I didn't want that pressure. So I removed it.

What I Gave Up

To be honest: there are real things I can't do because of this decision. I can't show you a history of what you've released. I can't build an insights feature that notices patterns over time. I can't offer a "look how far you've come" moment. Some of those might be genuinely useful products.

But they're different products. They're built for reflection, not release. And the world has plenty of those already.

UNHEAVY is built around a specific need: the need to be done with something. Not to analyze it. Not to carry it forward in an archive. To put it down.

Storing nothing is how you build for that.