Collection and purpose
List the fields or events and the task they support. Identify what the interface says and who can approve the intended handling.
Resources / Data-flow mapping
Where does the information from this task go?
Begin with one form, event or account workflow. Use safe descriptions and keep private evidence in an agreed controlled location.
Application and vendor destinations
Follow the information into the application, queues, logs and connected services within scope. Mark a destination as unknown if it has not been checked.
Choices and changes
In a fictional account-preference workflow, a saved choice may need to reach both the application and a connected messaging service. Test those steps separately instead of relying only on the saved interface value.
Retention and requests
Record the approved rules and the systems they cover. Identify exceptions, backups and third-party responsibilities that need a decision before implementing removal or export.
Keep the map maintainable.
Give each reviewed path an owner and a record of what was observed. Revisit the relevant map when a new form, vendor or AI-connected feature changes that path.