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

A.1.3.6 Providing mechanism to object to PII processing

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

An online shop regularly emails product recommendations to existing customers, relying on its legitimate interest. The link “No more recommendations” at the bottom of the email leads to a login page. One customer has forgotten her password, writes to support twice and still keeps receiving marketing. Her complaint to the supervisory authority is quickly made out: an objection to direct marketing applies without any balancing. A.1.3.6 requires a mechanism that lets data subjects object to the processing of their data, and that route suits the kind of service.

Objection is the counterpart to withdrawal. Where a legitimate or public interest carries the processing, it gives data subjects a means to halt it.

What does the standard require?

The control builds on the law of each jurisdiction and requires it to be usable in practice.

  • A route to object. The organization provides a mechanism through which data subjects can object to the processing of their data.
  • Observe the legal basis. Some jurisdictions give data subjects a right to object. Organizations subject to such rules take suitable measures so that the right can be exercised.
  • Document requirements. The organization records which legal and regulatory requirements apply to objections. The standard gives objection to direct marketing as an example.
  • Inform. Data subjects learn in which situations they can object.
  • Suited to the service. Mechanisms may differ but match the kind of offer. An online service offers objection online.

In practice

Distinguish two kinds of objection. Against direct marketing, an objection takes effect immediately and without balancing. Against other processing based on legitimate or public interests, the organization checks whether compelling grounds override the person’s interests. Both cases need a procedure of their own with clear responsibility.

Match the route to the channel. Every marketing email contains an unsubscribe link that works without logging in. The customer account has a switch for recommendations and profiling. For marketing letters, a reply address or a form the letter points to is enough.

Make the note visible. The right to object appears in the information at the latest at the first contact, understandably and separately from other details. For email marketing to existing customers in Germany, section 7(3) of the Act against Unfair Competition additionally requires the note at collection and with every use.

Keep a suppression list. After an objection to marketing, the address goes onto a suppression list that every campaign is checked against. The list holds only what the check requires.

Document balancing tests and reply. For a general objection, record which grounds were examined and how the decision went. The person receives a reply with reasons, and while the review is running, they can ask for processing to be restricted.

Typical audit evidence

For A.1.3.6, auditors typically expect:

  • Documented requirements for objections per jurisdiction (→ Legal Compliance Register)
  • Flags for processing open to objection in the record of processing activities
  • Notes on the right to object in privacy notices and marketing material
  • Objection routes per service and a maintained suppression list
  • Handling records with balancing tests and replies for general objections

KPI

% of applicable processing activities with functioning objection mechanism

Applicable means all processing that can be objected to under the law in force. Functioning means: the route is reachable on the service’s channel, is named in the information and demonstrably leads to implementation. The target is 100%.

Supporting KPIs:

  • Average time from a marketing objection to implementation in all channels
  • Number of marketing contacts after an objection (target: 0)
  • Share of general objections with a documented balancing test and a timely reply

A.1.3.6 implements Article 21 GDPR. Under paragraph 1, the person can object, on grounds relating to their particular situation, to processing under Article 6(1)(e) or (f), including profiling. Processing stops unless compelling legitimate grounds prevail or it serves legal claims. Against direct marketing, the objection applies without balancing under paragraphs 2 and 3. Paragraph 4 requires the right to be brought explicitly and separately to the person’s attention at the latest at the first communication, paragraph 5 allows automated means for online services, and paragraph 6 covers research and statistics. The information duty also appears in Articles 13(2)(b) and 14(2)(c), and restriction during the review in Article 18(1)(d). For public bodies in Germany, section 36 of the Federal Data Protection Act restricts the right (→ GDPR General Data Protection Regulation).

Objection sits between the lawful basis and passing data on:

Sources

Frequently asked questions

Does every objection have to be accepted?

For objections to direct marketing, yes, without any balancing and without the person having to give a reason. For general objections to processing based on legitimate or public interests, processing may continue if compelling legitimate grounds prevail or it serves legal claims. You have to be able to set out those grounds.

How do objection and withdrawal differ?

Withdrawal concerns processing based on consent and ends it for the future. Objection targets processing on another basis, above all legitimate interests, public tasks and direct marketing. Both rights belong in the information for data subjects, each with the processing it applies to.

May the address be kept after an objection to marketing?

In common practice, yes, on a suppression list holding only the details needed to prevent further marketing. Without such a list, the person could be contacted again through a new address set. The suppression list serves this purpose alone and is used for nothing else.

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.