Reading the register…
Department 05
MarketMute holds data that people want left alone. The model is therefore built on separation: what may move freely is kept apart from what must never leave the system.
Organizational intelligence and private personal data are stored and handled apart. A response built from material above the boundary can never be topped up with material from below it.
| Level | Content | Mobility |
|---|---|---|
| L0 | Public company data — material that's already open. | Free to use anywhere in the product. |
| L1 | Organizational intelligence: patterns and aggregates about senders, not about people. | Usable in analysis and classification. |
| L2 | Private personal data, isolated at row level per person. | Never leaves the system via an API response. |
A lookup that answers yes or no about an identifier could in principle be used to map out who's in the register. That's why the rate is limited and scanning patterns are throttled — see department 03. Responses also don't distinguish between “doesn't exist” and “has no suppression,” which makes enumeration considerably less valuable.
Report it directly to security@marketmute.com and describe how the flaw can be reproduced. Don't publish details before it's fixed.