Match the information to the task
A public article does not need a birth date, and browsing a playlist need not require an account. Where a calculation needs particular inputs, explain their purpose. Optional fields should look optional. Avoid collecting extra details simply because they might be useful for a future feature that the visitor has not requested.
Explain where information goes
Distinguish information kept on a device from information saved to an account or sent to a service provider. Do not make broad privacy promises that the implementation cannot support. Explain the consequences of signing out or clearing browser storage, particularly when the visitor has saved something only on that device.
Make control easy to find
Provide routes to correct details, remove saved material and request help. Separate service messages from optional promotional preferences. A privacy notice matters, but so do ordinary interface choices: clear labels, sensible defaults and understandable confirmation messages. Trust grows when people can see what an action will do before they take it.
