Privacy-first product design

Technology · 2026-05-25 · 8 min read

By Arjun Mehta, Engineering & product

The strongest privacy control is not collecting the data. Everything after that is damage limitation.

Data you never collected cannot leak, cannot be subpoenaed, cannot be sold by a future owner and does not need a retention policy. That is the whole argument, and it is more powerful than any encryption scheme layered on top of a database you did not need.

Start by auditing fields, not systems. For every column you store, ask which feature breaks if it disappears. A surprising number exist because somebody thought they might be useful for analysis that never happened.

Defaults are the product. If the private setting requires four taps and the shareable one is preselected, you have chosen for your users regardless of what the settings page implies. Consent screens that pressure people into agreeing are a design decision, not a legal one.

Deletion has to actually delete. Rows removed from the primary table and left intact in backups, logs, the analytics warehouse and three caches are not deleted, and the gap between the promise and the plumbing is where trust breaks.

Done well, this becomes a feature you can say out loud. "We do not store it" is a sentence competitors with a data-hungry business model cannot copy, and it survives every future breach they suffer.

Tags: privacy, ux, security

Arjun Mehta — Arjun writes about web performance, developer tooling and applied AI for ESPYCRUX. He has spent the last decade building and maintaining production web apps, and most of his articles start from something that broke in one of them.