# GDPR Article 37 — Designation of the data protection officer - Source: https://support.icompaas.com/compliance/gdpr/article-37-designation-of-the-data-protection-officer - Section: [Compliance](https://support.icompaas.com/compliance) › [GDPR (Regulation (EU) 2016/679)](https://support.icompaas.com/compliance/gdpr) › Articles 31–40 - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **GDPR**·Article `Article 37`·medium·Component: **Chapter IV: Controller and Processor** ## What this control requires > Controllers and processors must designate a data protection officer (DPO) for public authorities, large-scale systematic monitoring, or processing special categories of data. The DPO, selected for expertise, may serve multiple entities and must have published contact details shared with the supervisory authority. This control addresses Data Protection Officer. > > — GDPR, Article Article 37 ### In plain English Controllers and processors must designate a data protection officer (DPO) for public authorities, large-scale systematic monitoring, or processing special categories of data. In practice, this means you can prove you data controller-level controls on a defined cadence. ## Why it matters GDPR administrative fines reach the greater of €20 million or 4% of global annual turnover. The European Data Protection Board (EDPB) coordinates supervisory-authority enforcement across the EU/EEA, and DPAs publish enforcement decisions citing specific Articles. ## What an auditor looks for A DPA or privacy auditor expects: a Records of Processing Activities (RoPA) entry, a documented lawful basis, evidence the Article's data-subject right is operationalised end-to-end, a named DPO contact (where required), and Article 30 records that match what the front-end actually does. Within **Chapter IV: Controller and Processor**, the assessor will trace your implementation back to the catalogue reference (Article Article 37) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Policy Management **Docs.** Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA. ### Operational checklist - **Data.** Document the trigger, the owner and the cadence. - **Processor.** Document the trigger, the owner and the cadence. - **Designation.** Document the trigger, the owner and the cadence. - **Supervisory.** Document the trigger, the owner and the cadence. - **Scope:** controller, controllers, supervisory authority, data protection officer. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. Signed policy or standard documents the safeguard. Focus: Designation of the data protection officer. ## Common pitfalls - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**India DPDP Act 2023 GV-001** — Data Protection Officer (DPO) Appointment & Publication](https://support.icompaas.com/compliance/india-dpdp-act-2023/gv-001-data-protection-officer-dpo-appointment-publication) - [**BSI C5:2020 OIS-01** — Information Security Management System (ISMS)](https://support.icompaas.com/compliance/bsi-c5-2020/ois-01-information-security-management-system-isms) ## Related controls in GDPR - [**Article Article 31** — Cooperation with the supervisory authority](https://support.icompaas.com/compliance/gdpr/article-31-cooperation-with-the-supervisory-authority) - [**Article Article 36** — Prior consultation](https://support.icompaas.com/compliance/gdpr/article-36-prior-consultation) - [**Article Article 39** — Tasks of the data protection officer](https://support.icompaas.com/compliance/gdpr/article-39-tasks-of-the-data-protection-officer) - [**Article Article 33** — Notification of a personal data breach to the supervisory authority](https://support.icompaas.com/compliance/gdpr/article-33-notification-of-a-personal-data-breach-to-the-supervisory-authority) - [**Article Article 35** — Data protection impact assessment](https://support.icompaas.com/compliance/gdpr/article-35-data-protection-impact-assessment) - [**Article Article 27** — Representatives of controllers or processors not established in the Union](https://support.icompaas.com/compliance/gdpr/article-27-representatives-of-controllers-or-processors-not-established-in-the-union) ## References - [European Union — GDPR](https://eur-lex.europa.eu/eli/reg/2016/679/oj) - Catalogue identifier: `Article Article 37` Topics: governance riskcontinuous monitoringpolicy management ## Related compliance guidance - [GDPR compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/gdpr): Start with the full GDPR implementation guide — scope, roadmap, evidence and how the assessment runs. - [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): The security management system most EU procurement teams ask for alongside a DPA; its controls supply much of the Article 32 evidence. - [India's DPDP Act 2023: a practical compliance guide for cloud teams](https://support.icompaas.com/compliance/india-dpdp-act-2023): If engineering or support teams sit in India, the same data flows are also subject to India’s Digital Personal Data Protection Act.