Question

A retail company's mobile app initially collects only an email address to create an account, with the stated purpose of order confirmation. Over the following months, the product team wants to progressively collect additional data (birthdate, purchase preferences, location) as users interact with new features, to power a personalized recommendation engine. As the privacy engineer advising on the data life cycle, what is the MOST appropriate control to embed before this progressive collection begins?

Accepted Answer

Ensure each new data element is tied to a specific, disclosed purpose and a corresponding lawful basis before it is collected at the relevant interaction point

Answer

Collect all the additional data elements at account creation so consent only needs to be obtained once, simplifying the user experience

Answer

Rely on the existing account-creation consent, since the user already agreed to the privacy policy when signing up

Answer

Defer any privacy analysis until the recommendation engine is fully built, then apply de-identification to the aggregated dataset