What we deliberately don’t collect
A practical inventory of the advertising and behavioral data Haven is designed to avoid collecting.
Absence can be a feature
Many privacy policies begin with a long inventory of information a service gathers. Haven’s design begins with a shorter question: what can the product work without?
Haven is not designed around advertising identifiers, cross-site tracking, a social graph, or a behavioral profile sold to marketers. Your reflections should not become raw material for targeting you somewhere else.
Collect less, expose less
Every stored field creates responsibility. It can be leaked, misused, retained too long, or interpreted without context. Data minimization reduces those risks more reliably than a broad promise to protect an ever-growing archive.
Some operational data is still necessary to run an account, process a subscription, prevent abuse, and provide AI replies. Trust requires naming those necessities clearly instead of calling the whole experience anonymous.
A standard for future decisions
The useful test is not whether more data could improve a metric. It is whether collecting it is necessary for the person using Haven. If the answer is no, the default should be not to collect it.