An online language school wins its customers exclusively through its website and app. Its privacy notice gives a postal address and a fax number as the contact for all privacy matters. Anyone who wants to exercise the right of access has to write a letter, although they have only ever dealt with the school online. Internally, nobody knows exactly which obligations work differently in Austria and Switzerland than in Germany. A.1.3.2 requires the organization to know all its obligations to data subjects, whether they stem from law, regulators or its own promises, to record them and to provide a workable route for each one.
The control opens the group of obligations to PII principals. It is the frame into which information, withdrawal, objection, access, correction and erasure fit.
What does the standard require?
The control has two halves: knowing the obligations and making them workable in practice.
- Determine and document obligations. The organization establishes which obligations it has towards the people whose data it processes. This covers legal, regulatory and business obligations, so its own commitments too.
- Differences between jurisdictions. Which obligations exist and how they are met varies from country to country.
- Accessible and timely. The means of fulfilment are within reach of data subjects and lead to a result within a reasonable time.
- Clear information for data subjects. The organization explains in plain terms to what extent and by which route it meets its obligations, and names a current contact point for requests.
- Same channel. The contact point can be reached in a similar way to the collection. Whoever gathers data by email or through a website also offers contact by email or website and does not fall back on phone or fax.
In practice
Create a catalogue of obligations. Record each obligation with its source, trigger, deadline, responsible role and the means of meeting it. This covers data subject rights, information duties, notification after data breaches, national special rules and sector regulations. Do not forget your own promises: whoever pledges a reply within 14 days in the privacy notice is bound by it.
Match jurisdictions. For each country in which the organization processes data, check for differences in rights, deadlines and exceptions. The result belongs in the legal register, so that changes in the law reach the catalogue.
Set up a stable contact point. Use a shared mailbox or a form looked after by several people. Name the contact point in the privacy notice, on the website and in forms. A deputy arrangement for holidays and illness is part of it.
Match the channel to the collection. An app offers the privacy contact inside the app, an online shop in the customer account or by email. Post remains allowed as an additional route, yet it does not replace the digital way back.
Test reachability regularly. Once a quarter, send a test request through every channel offered and measure when and how the reply arrives. Orphaned mailboxes and broken forms stand out before a real request gets lost.
Typical audit evidence
For A.1.3.2, auditors typically expect:
- Catalogue of obligations with source, deadline and responsible role per obligation (→ Legal Compliance Register)
- Privacy notices describing how rights are exercised, with a current contact point
- Channel comparison between collection points and contact routes
- Logs of test requests to the contact point
- Responsibilities for each obligation (→ RACI Matrix)
KPI
% of obligations to data subjects identified and assigned to responsible owners
Every obligation in the catalogue counts if it has a responsible role and a described means of fulfilment. The target is 100%. Obligations without an owner are the ones left undone when it matters.
Supporting KPIs:
- Share of collection points with a way back on the same channel
- Share of test requests answered within the promised time
- Time since the catalogue of obligations was last updated
Link to the GDPR
The obligations to data subjects are set out in Chapter III of the GDPR, Articles 12 to 23. Article 12(2) requires the controller to facilitate the exercise of rights, and Article 13(1)(a) and (b) require the contact details of the controller and the data protection officer. Article 23 allows Member States to restrict rights, which Germany has done in sections 32 to 37 of its Federal Data Protection Act (→ BDSG German Federal Data Protection Act). Notification of data subjects after high-risk breaches under Article 34 comes on top. Under Article 38(4), data subjects can contact the data protection officer on all questions about their rights (→ GDPR General Data Protection Regulation).
Related controls
A.1.3.2 is the frame for the other controls in the group:
- A.1.3.3 Determining information for PII principals: describes what data subjects learn about their rights.
- A.1.3.7 Access, correction or erasure: puts the most important rights into practice.
- A.1.3.10 Handling requests: governs how incoming requests are handled.
- A.1.2.8 Joint PII controller: settles the contact point under joint control.
- A.2.3.2 Comply with obligations to PII principals: obliges processors to support the controller.
- A.5.31 Legal, Statutory, Regulatory and Contractual Requirements: identifies the legal sources of the catalogue.
Sources
- ISO/IEC 27701:2025, Annex A, Table A.1, A.1.3.2, and Annex B, B.1.3.2: Determining and fulfilling obligations to PII principals
- Regulation (EU) 2016/679 (GDPR), Articles 12, 13, 23, 34 and 38
- German Federal Data Protection Act (BDSG), sections 32 to 37
- ISO/IEC 27701: Privacy Information Management System: structure of the standard and roles