Wouch
<- Back to the beginning

By the time you read this, you already know we would refuse thesethings. This chapter just names them clearly.

Emotional vulnerability is not a growth lever.

It would be trivial to build the opposite. Detect when someone is raw and serve them more - that is how much of the industry grows, and it works.

We will never use your emotional state to increase engagement. Concretely: no mechanic anywhere in Wouch is triggered by detecting that you are vulnerable. Distress is met with care, never with a prompt.

Awareness, not dependence, is the goal.

Platforms that create dependence are more profitable than platforms that create independence. We know the trade we are making.

Wouch is built to be a platform you graduate from, not one you are trapped in - and we measure ourselves accordingly. We deliberately do not track time-in-app as a success metric, because the version of success that metric rewards is the version we refuse.

The nervous system deserves design consideration

Most relational products manufacture small anxieties and then sell you the relief - the unanswered-message dread, the read receipt, the engineered urgency.

For someone with relational trauma, an unexpected interruption is not a nudge; it is a threat signal. So Wouch will never send push notifications designed to spike re-engagement. Every interaction is judged against one question: does this create safety, or does it create urgency?

Crisis is a responsibility, not a feature gap.

Most apps treat a user in crisis as an out-of-scope edge case. We treat it as the truest test of whether we mean any of this.

If you are struggling, Wouch is designed to recognise it and connect you with real, human help - not to keep you inside the product. What we will never do is hold someone in crisis for the sake of a session.

If you have read this far, you already know whether Wouch is for you.

Ask to be considered