Question

A retail company is building an internal customer-service application. During design review, an engineer proposes an autocomplete feature that surfaces full customer records (including national ID and full payment history) as soon as an agent types the first three characters of any name, to speed up lookups. The privacy engineer must apply privacy by default to this feature. Which recommendation BEST embodies privacy by default while preserving usability?

Accepted Answer

Configure autocomplete to return only minimal disambiguating fields (e.g., name and masked account reference) by default, exposing sensitive fields only after an explicit, purpose-justified record open

Answer

Allow the autocomplete to display all fields but log every keystroke so misuse can be investigated after the fact

Answer

Keep the full-record autocomplete but add a banner reminding agents to access only records they need

Answer

Disable autocomplete entirely and require agents to request each record through a manual approval workflow