Before an AI feature reaches production, list every data path it creates. Include user input, retrieved context, generated output, logs, telemetry, backups, and support access. The list is often more revealing than a product label.
Describe the minimum useful input
Ask what the feature actually needs to complete its task. Remove identifiers, narrow the context window, or give users a way to preview what will be sent before a request leaves the device.
Set retention and access rules
Document how long inputs and outputs remain available, which teams can inspect them, and how a deletion request travels through caches and backups. A short, specific rule is easier to test than a broad promise.
Make the boundary visible
Explain the data flow in product language. Users should be able to tell whether a feature is processing a document locally, sending it to a service, or using it to improve a future system.
Trust is easier to maintain when the data path can be described in one clear paragraph.
Sources and further reading
Use the NIST Privacy Framework and the OWASP LLM application guidance when building a review checklist.