Zum Hauptinhalt springen
ISO/IEC 27701:2025 · Annex A, Table A.2 · Control for PII processors

A.2.2.4 Marketing and advertising use

Updated on 5 min Reviewed by: Cenedril Editorial
ISO/IEC 27701:2025GDPR

A provider of point-of-sale and loyalty systems runs the customer cards of several hundred retailers. Sales suggests sending “partner offers” to the cardholders and offering advertisers target groups built from purchase data. For years, the contract template has contained a clause meant to allow this, and the retailers signed it. Nobody asked the people whose purchases are in the data. A.2.2.4 requires you to use data from an assignment for marketing or advertising only once it is established that the data subject consented beforehand, and never to make that consent a condition of the service.

Advertising is where the temptation to use customer data for your own goals is greatest. This is why the standard deals with it separately, in addition to the general purpose limitation of A.2.2.3.

What does the standard require?

The control contains two prohibitions and two pieces of implementation guidance.

  • No advertising without established consent. You use data processed under a contract for marketing and advertising only after you have established that the right data subject consented beforehand.
  • No bundling. Consent must not be a condition for anyone receiving the service.
  • Document contractual compliance. That processors meet the customer’s contractual requirements is documented. The standard stresses this for cases where advertising is planned.
  • Do not force advertising clauses. Where express consent has not been obtained fairly, you do not push for advertising uses to be written into the contract.
  • An addition to A.2.2.3. The standard makes clear that this control adds to the general purpose limitation and does not replace it.

In practice

Record every advertising use. List where customer data touches advertising: your own campaigns, partner programmes, audiences for ad networks, lookalike lists, cross-selling inside the application, and also case studies and reference figures in sales. Many of these uses arise on the side and appear in no record.

Separate your own advertising from advertising on behalf of the customer. If you send advertising for your customer, they set the purposes and collect the consents. A proven approach is for the customer to assure you in the contract that the necessary consents exist, and for you to request evidence in spot checks, such as double opt-in logs. Advertising of your own with customer data is ruled out without the data subject’s consent.

Decouple consent from the service. Check sign-up flows, forms and terms you operate for customers. A marketing checkbox without which registration cannot be completed breaches the control.

Train sales and product teams. Most breaches start with a well-meant idea from sales or product management. A short rule helps: customer data goes into no advertising without approval from the data protection officer.

Keep evidence. Record which advertising uses exist, what they rest on and when you last checked the consent records. Ask your subcontractors for the same documentation if they take part in advertising activities.

Typical audit evidence

For A.2.2.4, auditors typically expect:

  • Rule or policy that prohibits advertising of your own with customer data unless consent exists (→ Acceptable Use Policy)
  • Reviewed contract templates and terms of use free of impermissible advertising clauses (→ Document Control Register)
  • Overview of advertising uses with their basis and the date the consent records were last checked
  • Customer assurances and results of spot checks for advertising on their behalf
  • Training records for sales, marketing and product management (→ Training Register)

KPI

% of marketing activities with verified PII consent basis

What counts are all activities in which customer data is used for advertising, whether your own or on behalf of the customer. Verified means: evidence of consent has been checked, at least in a sample. The target is 100%. An activity without a verified basis is stopped until the evidence is in place.

Supporting KPIs:

  • Number of contract templates and terms with open advertising clauses
  • Share of sign-up flows without bundled marketing consent
  • Share of staff in sales and marketing with current training on this rule

Article 7(4) GDPR makes bundling the test of whether consent is freely given: if a service depends on consent that is not needed to provide it, that speaks against free consent. Under Article 7(1), the controller must be able to demonstrate consent, hence the spot checks for advertising on behalf of customers. Article 21(2) and (3) give data subjects a right to object to direct marketing. As a processor, you are also bound by Article 28(3)(a): advertising without an instruction makes you a controller for that processing under Article 28(10) (→ GDPR General Data Protection Regulation).

A.2.2.4 sharpens purpose limitation for a particularly sensitive area:

Sources

Frequently asked questions

Does the control apply when I send advertising on my customer's behalf?

Yes. The control covers every use of customer data for advertising. If you send a customer's newsletter, consent is their responsibility. You should still make sure it exists, for example through a contractual assurance and spot checks of double opt-in records.

Can a legitimate interest replace consent?

Not for the processor. Under the GDPR, a controller can in some cases base direct marketing on its legitimate interest. A.2.2.4, however, expressly calls for the prior consent of the data subject for advertising with customer data, and advertising of your own would lie outside the instructions anyway.

May I use anonymized analyses for my own marketing?

Genuine anonymization removes the link to a person, so the results are no longer subject to data protection law. Getting there is itself processing of customer data, though, and needs a basis in the assignment. Clarify this with the customer before using customer data for case studies or sales figures.

No Cookies!

This wiki collects nothing, bakes nothing and leaves nothing behind. There's nothing to consent to. Privacy doesn't get better than this.