Why the privacy boundaries are the product

It is tempting to think of privacy as a setting, a checkbox somewhere in an account menu. We think that is exactly backwards. For a product where a coach, a parent, and a clinician might all see some of your data, the boundaries between what each of them can see are not a feature bolted onto the product. They are the product.

Here is the concrete version. If you are an athlete, your coach can see your physical readiness, whether you are recovered enough to train hard today. Your coach cannot see your mood, your stress, or anything you wrote about how you are feeling. That is not because we ask coaches nicely to look away. It is because the system does not give them a path to that data at all.

If you are a teenager, your parent can see whether you are sleeping and recovering. They structurally cannot see your mental-health screening data. A parent deserves to know if their kid is running themselves into the ground. A teenager deserves a private place to be honest. Both of those can be true at once, but only if the boundary is enforced by the software, not by a promise.

We built it this way because a promise is not worth much. Settings get changed. Policies get quietly updated. The only privacy you can actually trust is the kind that is impossible to violate, because the data was never reachable in the first place.

So when people ask what makes Salus different, the honest answer is not any single screen. It is that four different people can look at one person's data and each see only what they should. That is hard to build, and it is the whole point.