Data Minimalism — Building Systems That Forget
The Cost of Collection
Every byte of personal data you collect is a liability. It can be breached. It can be subpoenaed. It can be sold. It can be used in ways you never intended and could never have predicted.
The safest data is the data you never collected in the first place.
Protocol Four in Practice
Protocol Four — Minimal Footprint — is not a vague aspiration. It is a concrete engineering discipline:
What We Collect
- Nothing by default. A new free application starts with zero unnecessary data collection. Every field, every metric, every log entry must justify its existence.
- Only what is needed. If a feature works without a piece of data, that data is not collected.
- Only what is used. If collected data is not actively used by a feature the user directly benefits from, it is deleted.
What We Never Collect
- IP addresses for tracking purposes
- Device fingerprints
- Behavioral analytics
- Location data (unless the user explicitly opts in for a location-specific feature)
- Third-party tracking pixels or scripts
The Forget-by-Default Pattern
Traditional systems remember by default and require deliberate action to delete. Our systems invert this:
Data has a time-to-live. When the TTL expires, the data is automatically purged. The user must actively choose to retain data beyond its natural lifespan.
This is not just a privacy feature. It's a simplification. Systems that forget are lighter, faster, and easier to maintain. The database that holds less data responds more quickly. The backup that contains less data restores more reliably.
Trust Is the Product
We don't earn trust through privacy policies. Privacy policies are read by lawyers, not users. We earn trust through behavior:
- The health app that doesn't phone home
- The financial tool that stores everything on your device
- The messaging system that can't read your messages even if subpoenaed
Trust is not a feature. It is the product.
This dispatch documents the free-apps approach to minimal footprint.