Answer capsule
ICO guidance makes data collection, inference, fairness, preferences, and significant decisions part of marketing design.
What the source establishes
- The ICO describes profiling as analysis of interests, habits, and behavior.
- People have a right to object to direct marketing, including related profiling.
- Sensitive data and significant automated decisions require added care.
Inference is still data use
A profile inferred by a model can be more intrusive than a field the customer supplied. The CMO should know which attributes are inferred and how they affect treatment.
The accountable team should translate this point into a named workflow, affected population, source data, human owner, approval right, exception path, retained evidence, and review date. That translation is what separates an interesting AI development from a decision that can be governed and evaluated.
Relevance is not fairness
A message can perform well while relying on a harmful proxy, excluding a group, or exploiting vulnerability. Performance review needs a separate fairness and customer-impact lens.
The accountable team should translate this point into a named workflow, affected population, source data, human owner, approval right, exception path, retained evidence, and review date. That translation is what separates an interesting AI development from a decision that can be governed and evaluated.
Preference enforcement belongs upstream
Opt-out and channel restrictions should be applied before an AI system selects or generates the message, not checked manually after activation.
The accountable team should translate this point into a named workflow, affected population, source data, human owner, approval right, exception path, retained evidence, and review date. That translation is what separates an interesting AI development from a decision that can be governed and evaluated.
Create a challenge route
Customers and service teams need a practical way to question, correct, or stop profiling-driven treatment.
The accountable team should translate this point into a named workflow, affected population, source data, human owner, approval right, exception path, retained evidence, and review date. That translation is what separates an interesting AI development from a decision that can be governed and evaluated.
Decision test
Ask whether the source changes the decision itself, the evidence required, the implementation sequence, or only the language used to describe an existing capability. Record which claims are directly supported, which are provider statements, which require an independent test, and which remain unknown. A source-linked review should make uncertainty easier to see, not bury it inside a blended score.
Questions to take into review
- Which people and channels are represented?
- Can each insight be traced to evidence?
- What training, input, and output rights apply?
- Which review gates cover claims and brand expression?
- Which repository owns approved content?
- How are market and channel variations controlled?
- What is the optimization target?
- Which placements and audiences can be excluded?
The publication supports research and executive decision preparation. It does not provide legal, financial, accounting, employment, clinical, cybersecurity, investment, procurement, or implementation advice.