Children and Household Profiles Addendum

Purpose

IngredientsMatter can be used by households to manage meal plans and dietary restrictions for multiple people, including children. This addendum sets stronger privacy defaults for child-profile handling.

Starter policy position

• Child profiles should be created and managed by an adult account holder or household admin.
• Only the minimum data needed to make the product work should be collected.
• Child profile data should not be used for advertising or behavioural profiling.
• Free-text medical detail should be avoided where structured controls are enough.
• Child data should only be shared with processors needed to run the service or where required by law.

Data fields to allow

• First name or nickname.
• A birth month (year and month) where age matters, from which an age band is derived; never a full date of birth.
• Dietary rules, allergy flags, meal preferences, and safety notes entered by the responsible adult.

Data fields to avoid by default

• Full date of birth unless clearly needed.
• Location or school details.
• Excessive free-text medical history.
• Marketing preferences attached to child profiles.

Governance and UX expectations

Household-admin approval, clear profile labels, easy export and delete controls, and privacy-protective defaults should remain part of any future child-profile workflow.