A group of car dealerships buys addresses from a list broker for a marketing campaign and sends out 20,000 letters. Where the addresses came from is stated nowhere. Several recipients complain, and the supervisory authority asks how the group meets its information duties for data obtained from third parties. No decision on this exists; the website’s privacy notice only describes contact through the web form. A.1.3.3 requires the organization to decide, for each processing activity, what data subjects need to know and when, and to document that decision.
The control is the editorial plan of transparency. It settles content and timing. How the information reaches people is then governed by A.1.3.4.
What does the standard require?
The control asks two questions: what does the person need to know, and when?
- Derive timing from requirements. From law, regulators and its own commitments, the organization establishes when information is due: for example before any data is processed, or within a set time after someone has asked for it.
- Decide the content. It also settles which kind of information is required. Depending on the requirement, this may be a formal notice.
- Typical content. The standard offers a list of examples: purpose, contact details of the controller or its representative, lawful basis, source of the data if obtained from third parties, whether providing data is a statutory or contractual requirement and what happens if it is refused. Further items are the rights from A.1.3.2 and how to use them, withdrawal of consent, transfers, recipients, storage period, automated decisions, the right to complain and how often information is given.
- Update after a change of purpose. If a purpose is changed or extended, the organization provides fresh information.
In practice
Keep an information matrix. Assign each processing activity the content items from the list, together with timing and form: note in the form, privacy notice, information letter or posted notice. You can see at a glance where information is missing or arrives too late.
Feed the content from the record. Purpose, lawful basis, recipients and storage period are already in the record of processing activities. Take them from there, so that notices and record contain the same details and a change only has to be made in one place.
Plan third-party collection separately. If data comes from other sources, such as list brokers, partners or public registers, a separate information letter stating the source is needed. Decide who sends it and when.
Mark mandatory fields. Where forms ask for data, they state which details are required and what happens if they are missing. This applies to job applications as much as to contract sign-ups.
Book changes of purpose twice. A new or extended purpose triggers two steps: the entry in the record and informing data subjects before the new use begins. People are reached through the channel on which the organization is in contact with them.
Typical audit evidence
For A.1.3.3, auditors typically expect:
- Decision per processing activity on the content, timing and form of information
- Current privacy notices, checked against the record of processing activities (→ Document Control Register)
- Legal sources of deadlines for each jurisdiction (→ Legal Compliance Register)
- Templates and dispatch records for information letters after third-party collection
- Evidence for changes of purpose with data subjects informed beforehand (→ Change Log)
KPI
% of processing activities with complete data subject information documentation
Complete means: for the processing activity, it is decided which content data subjects receive, when and in what form, and the decision matches the current state of the record. The target is 100%.
Supporting KPIs:
- Share of privacy notices checked after the last change to the record
- Share of changes of purpose with information given before the new use began
- Share of third-party collections with a timely information letter
Link to the GDPR
The standard’s list of examples largely follows Article 13 GDPR for data collected from the person and Article 14 for data from other sources. Article 14(2)(f) requires the source to be stated, and Article 14(3) sets the deadline: a reasonable period, one month at the latest, earlier on first contact or disclosure. For new purposes, Articles 13(3) and 14(4) require information before the further processing. What data subjects learn on request is governed by Article 15. The frequency of information is an addition by the standard with no direct counterpart in the GDPR (→ GDPR General Data Protection Regulation).
Annex D of the standard also maps A.1.3.3 to three information duties found elsewhere: Article 11(2) for cases in which the organization cannot identify the person, Article 18(3) for informing the person before a restriction is lifted, and Article 21(4), under which the right to object is brought to the person’s attention explicitly and separately from other information at the latest at the first communication.
Related controls
A.1.3.3 gathers details from across the conditions for processing:
- A.1.2.2 Identify and document purpose: supplies purposes worded to fit the information.
- A.1.2.3 Identify lawful basis: supplies the basis that is communicated.
- A.1.3.2 Determining and fulfilling obligations to PII principals: settles the rights people are told about.
- A.1.3.4 Providing information to PII principals: brings the defined content to people in an understandable form.
- A.1.4.8 Retention: supplies the storage period.
- A.5.34 Privacy and Protection of PII: anchors the transparency duties in the ISMS.
Sources
- ISO/IEC 27701:2025, Annex A, Table A.1, A.1.3.3, and Annex B, B.1.3.3: Determining information for PII principals
- Regulation (EU) 2016/679 (GDPR), Articles 11, 13, 14, 15, 18 and 21
- ISO/IEC 27701: Privacy Information Management System: structure of the standard and roles