A running app links to a 14-page privacy notice at sign-up. On a smartphone, a PDF full of legalese opens that nobody reads to the end. When the app later starts tracking location in the background, no notice appears, and the privacy notice can no longer be found in the settings. Everything in it is correct; it simply reaches nobody. A.1.3.4 requires the organization to provide the defined information in a way that lets data subjects find it, understand it and see who is behind the processing.
A.1.3.3 decides what has to be said. A.1.3.4 decides whether it gets through. The two controls belong together, and in audits the second is often checked against screenshots of the forms.
What does the standard require?
The control sets standards for the form of information. For content, it refers to A.1.3.3.
- Name the controller, describe the processing. The information shows who processes the data and what happens to it.
- Quality features. The content from A.1.3.3 reaches people on time, concisely, completely, transparently, understandably and in an easily accessible way.
- Language of the audience. The wording is clear and simple and suits the people it addresses.
- At collection and permanently. Where it fits, information is given at the moment of collection. It also remains available at all times.
- Pictures help. In a note, the standard recommends icons and graphics that show the intended processing at a glance.
In practice
Serve every channel. Website, app, paper form, telephone hotline and reception desk each need a suitable form. On the phone, a short sentence with a pointer to the notice is enough; at reception, a posted notice or a sheet to take away.
Place notes in the moment. When an app wants to use location, camera or contacts, a note right before the request explains why. Such well-timed notes work better than any paragraph in a long notice.
Check comprehension. Short sentences, active wording and everyday examples make notes readable. Let people from the audience read them and ask what they understood. Services for children call for a particularly strict standard.
Keep it permanently available. The notice can be reached with one click at most from every page of the website and from the app settings, and it works with screen readers. Old versions are archived, so it can later be shown which text applied when.
Bring development and business together. Notes in forms and apps are built by software development. Include information duties in the requirements for new features and have the texts approved by the data protection officer before go-live.
Typical audit evidence
For A.1.3.4, auditors typically expect:
- Privacy notices per channel: website, app, paper, phone script, posted notice
- Screenshots of collection points showing the first layer of information (→ Change Log)
- Results of comprehension checks or user tests
- Version archive of the notices with validity periods (→ Document Control Register)
- Approvals of new texts by the data protection officer
KPI
% of data subjects provided with required privacy information at collection
In practice, the figure is measured through collection points: how many people come in through points where the first layer of information is visible before they enter data? The target is 100%. Gaps usually lie with paper forms, phone and events.
Supporting KPIs:
- Share of collection points with a note right at the form
- Share of channels on which the full notice is one click away
- Result of the last comprehension check per audience
Link to the GDPR
The standard’s quality features correspond to Article 12(1) GDPR: concise, transparent, intelligible and easily accessible, in clear and plain language, in particular for information addressed to children. Article 13(1) requires information at the time of collection, and Article 14(3) sets the deadlines for third-party collection. Article 12(7) provides for standardized icons in combination with the information, and Recital 58 expressly names the website as a place for information. The transparency guidelines (WP 260) endorsed by the European Data Protection Board recommend the layered model (→ GDPR General Data Protection Regulation).
Annex D of the standard also maps A.1.3.4 to Article 11(2) and Article 21(4). If the organization cannot identify a person, it tells them so where possible. It points out the right to object at the latest at the first communication, explicitly and separately from other information.
Related controls
A.1.3.4 is how transparency is delivered:
- A.1.3.3 Determining information for PII principals: settles content and timing.
- A.1.2.5 Obtain and record consent: assumes the person was informed before consenting.
- A.1.3.2 Determining and fulfilling obligations to PII principals: supplies the contact point stated in every piece of information.
- A.1.3.5 Providing mechanism to modify or withdraw consent: needs a note on withdrawal in the information.
- A.8.25 Secure Development Life Cycle: includes information duties in the requirements for new features.
- A.5.34 Privacy and Protection of PII: anchors transparency in the ISMS.
Sources
- ISO/IEC 27701:2025, Annex A, Table A.1, A.1.3.4, and Annex B, B.1.3.4: Providing information to PII principals
- Regulation (EU) 2016/679 (GDPR), Articles 11, 12, 13, 14 and 21 and Recital 58
- Article 29 Working Party, Guidelines on transparency under Regulation 2016/679 (WP 260 rev.01), endorsed by the European Data Protection Board
- ISO/IEC 27701: Privacy Information Management System: structure of the standard and roles