Every conversation about a product like this arrives at the same question in the first ten minutes, and people are right to ask it. What does it know, and who else can see it?
The answer most vendors give is sincerely meant and structurally worthless: it is encrypted, we do not look at it, we are compliant. Each clause is probably true on the day it is said. None of them is a property of the system. All of them can change with a funding round, an acquisition, or a new head of growth who has a very reasonable idea about product analytics.
What we think the difference is
A policy is a statement about what a company intends to do, and it is only as durable as the company. A design decision is a statement about what a system is able to do, and changing it means shipping different software and telling you.
We would rather be held to the second, because the second is the one you can check.
What that looks like in practice
- Behaviour a person can predict — a device that does something surprising has already lost the argument, whatever the documentation says.
- Collecting what the job needs and not what might be useful later.
- Saying what is not decided yet, rather than describing an intention in the present tense.
Privacy, clarity, responsible use and understandable product behaviour are design requirements, not language added at the end.
None of that is finished. Curio X and Vibe are both in development, and the specifics of how each handles data will be published when they are settled rather than sketched now and quietly revised.
