What it is
A detection policy centralizes which field names and patterns count as sensitive, along with how they should be masked, so multiple tools can apply the same rules consistently.
When to use it
Privacy engineers use this to define an organization-wide policy once, then reuse it across the PII Detector and Content Desensitizer instead of reconfiguring rules each time.
Gotchas & limits
A policy is only as strong as the field names and regexes you include; review it periodically as new sensitive field types are introduced into your systems.