Roles and Responsibilities Related to Data is the organizational framework that assigns legally defined and operationally necessary accountability for how personal and organizational data is collected, processed, protected, and governed. The framework distinguishes four primary designations: (1) Data Controller — the legal entity that determines the purposes and means of processing personal data, bearing ultimate regulatory accountability; (2) Data Processor — a third party that processes data on behalf of, and under instruction from, the Controller; (3) Data Protection Officer (DPO) — an independent, designated expert who monitors compliance, advises on data protection obligations, and serves as the contact point for data subjects and supervisory authorities; and (4) Data Steward — an operational role responsible for data quality, metadata management, and business-rule enforcement within a specific domain. Additional roles include Data Owner (the business-side accountable for a data asset), Chief Privacy Officer (CPO, a strategic C-suite role), and Vendor Privacy Manager (accountable for executing and maintaining Data Processing Agreements with third parties). These roles may be held by different individuals, consolidated in smaller organizations, or distributed across a federated governance model.
Where it stops · what it isn't
- —IS: Legally grounded designations (Controller, Processor, DPO) derived from GDPR, CCPA/CPRA, LGPD, and equivalent regulations, plus operationally defined roles (Data Steward, Data Owner, CPO) from governance frameworks such as DMBOK and ISACA CDPSE
- —IS NOT: A generic org-chart design exercise — these roles carry specific legal obligations, liability exposure, and in some cases mandatory appointment requirements that cannot be arbitrarily reassigned
- —IS NOT: A one-size-fits-all structure — a solopreneur may consolidate all roles personally, while an enterprise may distribute them across dozens of people in a matrix structure
- —IS: Applicable to both internal data governance (employee data, operational data) and external processing (customer data, partner data, data subject rights management)
- —IS NOT: Interchangeable with Information Security roles (CISO, Security Engineer) — privacy roles govern lawfulness, fairness, and purpose limitation; security roles govern confidentiality, integrity, and availability. Overlap exists but the accountabilities are distinct
- —IS NOT: Static — role definitions evolve as new regulations (EU AI Act, DSA, US state-level privacy laws) add new accountability requirements
Connected concepts in the graph
Every cubelet sits in a knowledge graph. Here's what this one connects to.
PART OFPrivacy Governance — Management (ISACA CDPSE Domain 1)
REQUIRESData Processing Agreements (DPA) and Standard Contractual Clauses (SCC)Privacy Impact Assessments (PIA / DPIA)
ENABLESData Subject Rights Management (Access, Erasure, Portability)Privacy by Design and Default implementationIncident Response and Breach Notification
RELATED TOPrivacy Governance Frameworks and Policies
CONSTRAINSVendor and Third-Party Data ManagementData Retention and Lifecycle Governance