Data Minimization: Collect Only What You Need

WHY IT EXISTS: In the past, companies hoarded user data, believing more data was always better. This created massive security risks and privacy intrusions. Data minimization exists to reverse this, forcing systems to be designed with privacy first and treating personal data as a liability to be protected, not an asset to be exploited.

THE MENTAL MODEL: Think of it like packing for a hike. You only bring what's essential for the journey—water, a map, a first-aid kit. You don't pack your entire kitchen "just in case" you decide to bake a cake. Every piece of data you collect is an item in your backpack; it has a weight (storage cost, security risk) and must have a clear purpose for being there.

HOW IT WORKS: Data minimization is implemented by asking "Do I absolutely need this piece of information to provide the service right now?" for every data field. First, you define a specific, legitimate purpose for data processing. Second, you identify the minimum data set required to achieve that purpose. Third, you collect only that data and nothing more. For example, if the purpose is sending a newsletter, the only necessary data is the email address.

WHEN TO USE IT: This principle should be applied whenever you are designing any system that handles personal data. It's a foundational concept for user registration flows, checkout processes, and analytics tracking. It is a legal requirement under privacy laws like GDPR, making it non-negotiable for most modern applications.

WHEN NOT TO USE IT: There is no situation where it's appropriate to intentionally ignore data minimization when dealing with personal data. However, the definition of "necessary" can be context-dependent. For example, collecting a date of birth is unnecessary for a blog, but it is necessary for an age-restricted service. The key is that the necessity must be justifiable and documented.

ONE CANONICAL EXAMPLE: A classic example is a user signup form. A "minimal" form might only ask for an email and a password. A form that violates the principle would ask for email, password, full name, date of birth, and home address "to personalize your experience" without providing any immediate, concrete personalization that requires all that data. The minimal approach respects user privacy and reduces the company's risk profile.