An information request often grows one field at a time. A detail that might be useful later becomes a required question today, even when the immediate task does not depend on the answer.
Start with the purpose of the collection. Which information is necessary to complete that purpose, and which is merely convenient? Asking less can reduce the work of protecting, correcting, and eventually removing information that never needed to be collected.
Review the fields when the task changes. A question that made sense in an earlier process may no longer belong. A clear purpose gives both the person asking and the person answering a better basis for deciding what to share.
- Connect each field to a current purpose.
- Separate necessary information from optional detail.
- Review the collection when the task changes.
A small working example.
A reading preference form may need a topic but no home address. Comparing each requested field with the task makes unnecessary collection easier to notice.
A note to keep beside it.
A boundary becomes useful when a person can recognize it. Plain explanations should accompany the choices that change who can access or retain information.
Follow a related question
Identify profile-specific and device-wide settings.
Preferences that travel with the personUse one easy landing place.
An inbox for informationKeep learning
Related background to continue exploring this subject.
MDN: privacy on the web MDN: web security
