SKIP TO CONTENT
369 Hertz

← RECORD 004 / WRITING & REFERENCE BUILDSESSAY 005

PRIVACY UX · AUGUST 2025 · 2 MIN READ

What a privacy-respecting dashboard refuses to show

Restraint as an interface property. The metrics a dashboard should refuse to compute, and how to size the refusal.

Analytics dashboards are usually judged by what they can show. We’ve started judging them by what they refuse to. Every metric on a screen is a metric someone can be compelled to produce, by subpoena, breach, or acquisition. The cheapest way to protect data is to have designed the surface that never computed it.

01 · REFUSAL AS ARCHITECTURE

Refusal has to be structural to count. A per-user activity view that is merely hidden behind a permission still exists. A dashboard that aggregates before storage (the individual row is never written) cannot leak what it never held. The interface is the honest expression of that architecture: cohort floors on every chart, no drill-down past the point where a person becomes identifiable.

02 · SELLING RESTRAINT

The hard part is defending this in a roadmap meeting against "but we could know." The argument that wins is about liability, not ethics: every question the dashboard cannot answer is a question the company cannot be forced to answer either.

03 · SIZING THE FLOOR

Take a product with 1,400 weekly active users that wants usage charts with three filters: six regions, three plans, and week. The cohort floor looks like one decision: suppress any segment smaller than k. In practice you make two decisions: the size of k, and where you enforce k.

Set k at 20 and enforce the floor after every filter, not once against the base population. In this grid the average cell holds 78 users and the smallest holds 4. A floor of 5 suppresses almost nothing and protects almost nothing, because the floor exists for the corner cells, and here the corners are single digits. At 20, roughly a tenth of the cells render below the floor. The suppressed tenth is the visible cost of the guarantee, and your team sees the cost on screen.

Suppression also spreads. A row showing five of six cells plus its own total hides nothing, because subtraction recovers the sixth cell. So when one cell drops below the floor, the dashboard suppresses the smallest sibling cell as well. Both render as BELOW FLOOR · k=20, a labelled state in the muted tone: the argument from redaction as a first-class state, applied to a chart.

FILED UNDERPRIVACY UXPRACTICE

Reading this against a problem you have right now?

START A CONVERSATION A 30-minute call, no deck. Short form; a reply within two business days.