A tour operator collects marketing consent with one tap in its app. Anyone who wants to take it back has to write to a separate email address and attach a copy of their ID. After the withdrawal, the newsletter stops, yet the CRM keeps feeding the address to an agency that sends text message offers for weeks. A.1.3.5 requires a mechanism that lets data subjects modify or withdraw their consent, and requires the change to reach every place where the data is processed.
Consent is only as free as the way back. If withdrawal is hard work, the validity of the original consent is in doubt too.
What does the standard require?
The control covers everything that follows consent: information, route, record, passing on and deadline.
- Inform about the right to withdraw. Data subjects can learn at any time which rights they have when withdrawing. These rights may differ between jurisdictions.
- Offer the same route. The mechanism depends on the system and, where possible, matches the route used to obtain consent. Whoever consents by email or website withdraws there too and does not have to pick up the phone or send a fax.
- Modifying can mean restricting. A changed consent can limit the processing, in some cases up to a ban on deleting the data.
- Observe legal limits. Some jurisdictions regulate when and how consent can be changed or withdrawn.
- Record, pass on, act on time. Each withdrawal and change is recorded in much the same way as the consent itself, passed to authorized users and relevant third parties and handled within a defined response time.
- Do not reuse earlier results. As additional information, the standard explains that processing before the withdrawal remains acceptable, while its results do not feed into new processing. After consent to profiling is withdrawn, the profile is no longer used.
In practice
Offer the way back where consent was given. An unsubscribe link in every marketing email, a switch in the account or app settings, a reply to the same address. The note on withdrawal already appears in the consent statement.
Know three states. Besides “given” and “withdrawn”, the system needs a third state: restricted. The data then remains but is no longer processed for the purpose concerned. This matters when deletion is not legally possible.
Record withdrawals like consents. Time, person, the consent affected and channel belong in the record. That makes it possible to show later from when the processing had to stop.
Pass changes on automatically. Newsletter tool, CRM, advertising platforms and contracted agencies receive the new status through interfaces or a fixed reporting route. Where partners are involved, A.1.3.8 also applies, with acknowledgement of receipt.
State limits openly. Record for each jurisdiction where a withdrawal does not take effect, for example because of retention duties or pending legal claims. Tell the person in such cases what happens to their data, so that the request does not run into silence.
Typical audit evidence
For A.1.3.5, auditors typically expect:
- Withdrawal route per consent mechanism, evidenced by screenshots or test logs
- Withdrawal records with the same structure as the consent records
- Evidence of passing changes on to systems and third parties, such as interface logs or acknowledgements
- Defined response time and its measurement
- Consent texts with a note on the right to withdraw (→ Document Control Register)
KPI
% of consent-based processes offering functional consent withdrawal mechanism
Functional means: withdrawal is possible on the channel of collection, is recorded and reaches all systems and third parties within the defined time. The target is 100%. One test withdrawal per process per year provides the basis for measurement.
Supporting KPIs:
- Average time from withdrawal to implementation in all systems
- Ratio of steps for withdrawal to steps for consent
- Share of withdrawals with confirmed delivery to all recipients
Link to the GDPR
Under Article 7(3) GDPR, data subjects can withdraw consent at any time. They are told about this before consenting, withdrawal has to be as easy as giving consent, and processing up to the withdrawal remains lawful. Articles 13(2)(c) and 14(2)(d) require the information to mention the right to withdraw. If no other lawful basis exists after the withdrawal, the data has to be erased under Article 17(1)(b). Restriction of processing is governed by Article 18, and notifying recipients of erasure or restriction by Article 19 (→ GDPR General Data Protection Regulation).
Related controls
Withdrawal closes the circle that consent opens:
- A.1.2.5 Obtain and record consent: supplies the record that withdrawal follows.
- A.1.3.8 PII controllers’ obligations to inform third parties: carries the withdrawal to recipients.
- A.1.3.6 Providing mechanism to object to PII processing: the counterpart for processing without consent.
- A.1.3.10 Handling requests: sets deadlines and procedures for requests that do not run through a switch.
- A.1.4.3 Limit processing: restricts processing to what is still permitted after the withdrawal.
- A.5.34 Privacy and Protection of PII: anchors data subject rights in the ISMS.
Sources
- ISO/IEC 27701:2025, Annex A, Table A.1, A.1.3.5, and Annex B, B.1.3.5: Providing mechanism to modify or withdraw consent
- Regulation (EU) 2016/679 (GDPR), Articles 7, 13, 14, 17, 18 and 19
- ISO/IEC 27701: Privacy Information Management System: structure of the standard and roles