The data owner is the person who, for a given set of the organisation’s data, has the authority to decide what purpose it serves, who may use it and what quality is acceptable, and who answers for it to the organisation.
What defines it, then, even before ownership, is the responsibility it answers for: after all, without a name and a mandate, decisions about data belong to no one and end up with whoever has the credentials to carry them out. The data owner is therefore part of the organisational structure: it gives one person authority and accountability for decisions that would otherwise remain spread between the business and IT.
In this guide we look at what a data owner decides, how the role differs from the controller and the other roles, how one is chosen, and why the appointment is a governance decision rather than an IT task.
Data owner: what it means and why “owner” is misleading
Data ownership means formally assigning responsibility for data to a person, by domain: customer data, employee data, accounting data. We are talking about sensitive, specific decisions such as access, use, problem resolution, versions and compliance (Government Digital Service, 2026). It is a governance function first, and a management function only second.
Accountability becomes particularly important for data shared across many processes, such as customers, products and suppliers: this is the territory of Master Data Management, where owners and stewards must guarantee common definitions and rules.
Yet the label is misleading, because ‘owner’ suggests a proprietor. The law, however, says otherwise. The GDPR contains neither the term ‘data owner’ nor that of data proprietor: it assigns decisions to the controller, that is, whoever determines the purposes and means of processing personal data (Regulation (EU) 2016/679, Art. 4). The Data Act does not assign ownership: it defines the data holder as whoever has the right or obligation, under the regulation and applicable law, to use and make data available, and the user as whoever owns a connected product or holds temporary rights to use it (Regulation (EU) 2023/2854, Art. 2). Rights and obligations, not ownership.
The data owner is therefore an organisational choice: it is how an organisation decides who, internally, takes the decisions on data that the law and good governance require of it.
Three meanings of ‘owner’
Why data owner does not mean data proprietor.
| Term | Where it appears | What it denotes | Who it is |
|---|---|---|---|
| Proprietor | Everyday language | The person who owns something | The GDPR and the Data Act do not assign ownership of data |
| Data controller | GDPR, Art. 4 | Whoever determines the purposes and means of processing personal data | Normally the organisation |
| Data holder | Data Act, Art. 2 | Whoever has the right or obligation to use and make data available | Natural or legal person |
| Data owner | Data governance | Whoever decides and answers for a data domain within the organisation | Designated person acting under the controller’s authority |
Sources: Regulation (EU) 2016/679, Art. 4; Regulation (EU) 2023/2854, Art. 2; Government Digital Service, Data ownership model, 2026. Summary by Bliss.
What a data owner decides
The UK model lists the owner’s responsibilities: understanding how data is used, by whom and where it flows; setting core definitions and directing stewards to apply them; approving changes; ensuring that quality is known and monitored; restricting access, especially to personal or sensitive data; maintaining retention periods; complying with licence conditions (Government Digital Service, 2026).
Knowing where data originates, what transformations it goes through and where it is used is the task of data lineage, which makes the path the owner is accountable for verifiable.
We group them into five decisions, which are the non-delegable part of the role:
- Purpose: what the data may be used for, and what it may not.
- Access: who can view, modify and export, and under what rule.
- Acceptable quality: how much error can be tolerated in the decisions that depend on that data.
- Retention: how long data is kept and when it is deleted.
- Exceptions: who authorises what the rules do not provide for, and what is escalated.

This separation between those who decide, those who execute and those who verify is part of the wider internal control system, which assigns responsibilities and controls according to the organisation’s risks.
Data owner, controller and other roles: who does what
For personal data, the controller remains the organisation, which is accountable for compliance with the regulation and must be able to demonstrate it: this is accountability (Regulation (EU) 2016/679, Arts 5 and 24). The Italian Privacy Code allows the controller, under its own responsibility and within its own organisational structure, to assign specific tasks and functions relating to processing to expressly designated natural persons acting under its authority (Legislative Decree 196/2003, Art. 2-quaterdecies). Anyone acting under that authority processes data only on the controller’s instructions (GDPR, Art. 29).
A decisive point follows: designating a data owner delegates decisions, not accountability. The controller assigns them to a person, but remains accountable. That is why the appointment is something to be put in writing, with a mandate and limits, and not an organisational courtesy. The designation issue concerns personal data; the same governance logic applies to other data, but there is no legal obligation of this kind.
The other roles are distinguished by the question they answer. The data steward looks after the data day to day and applies the owner’s rules. The data custodian, in the British model, acquires, stores and deletes data according to the owner’s requirements and applies the security measures. The data protection officer monitors and reports directly to the controller’s highest management level (GDPR, Art. 38(3)): they do not decide the purposes, and for precisely this reason should not be the owner of the data they monitor.
Who does what with data
Six roles, six different questions.
| Role | Question it answers | Limits of the role |
|---|---|---|
| Data owner | Which purposes, access rights and quality levels apply to this domain? | Decides, but does not look after the data day to day |
| Data steward | Are the rules applied? Is the data described and of good quality? | Maintains, but does not decide the purposes |
| Data custodian | How is data acquired, stored and protected on the systems? | Manages the systems, not the meaning of the data |
| Data controller | Does the processing comply with the GDPR, and can this be demonstrated? | Does not delegate its own responsibility |
| Processor | Does processing on behalf of the controller follow the controller’s instructions? | Processes data on behalf of the controller |
| DPO | Does the organisation comply with personal data legislation? | Oversees and reports to senior leadership; does not decide purposes |
Sources: Regulation (EU) 2016/679, Arts 4, 24, 38; Government Digital Service, Data ownership model, 2026. Summary by Bliss.
The data owner and those who govern the company
The governance rationale is the same one that explains the role. The ISO/IEC 38505-1:2026 standard on data governance is addressed to the governing bodies of organisations (owners, directors, shareholders, executives) and gives them the principles for the effective, efficient and acceptable use of data (ISO/IEC 38505-1:2026). Ultimate responsibility for data therefore sits above the owner. Senior leadership does not appoint every single owner, but it is accountable for a system in which every critical data asset has one, and it receives evidence that the system works.
The link with corporate governance is direct: governance is the system of rules, roles and controls that establishes who decides what and to whom they answer, and data ownership is its application to data. Where data governance has not yet been built, the owner is one of the first concrete steps, because rules without a person to apply them change nothing. The broader framework is set out in the guide to data governance (coming soon).
The Bliss angle: the ‘no’ test
The data owner is the point at which governance stops being a document.
The ‘no’ test
To see why, take the five data sets on which your accounts, your customers and your legal obligations depend, and for each one ask who can refuse an access request. If the answer is ‘it depends’ or ‘IT’, there is no owner yet.
There is also a brand dimension. An organisation that cannot say who answers for its data cannot say to whom a customer has entrusted theirs either: and stakeholder trust depends on this too.
Who to appoint as data owner, and how
The UK model calls for a ‘senior’ owner with dedicated responsibilities for data, and requires a responsible owner to be appointed for every critical dataset. It sets out a path for the appointment: identify people with the right skills, appoint them with defined responsibilities, train the appointee, have the appointee confirm in writing that they understand their obligations, then review periodically, normally every year or whenever roles change significantly (Government Digital Service, 2026).
On everything else, our reading is this. The owner is chosen by business area, not by technical expertise: whoever is accountable for people management is also accountable for employee data, even without knowing how it is stored. They must have the authority to decide and the resources to have decisions carried out: an owner with neither budget nor the power to say no is a steward with a grander title. And there must be only one, because a committee accountable for everything is accountable for nothing. It is the same rule that applies in a RACI matrix: for each activity there is only one accountable.
Be careful, though, because three mistakes keep recurring.
The first is appointing IT by default: IT looks after the systems, but does not decide what purposes their contents serve. The second is appointing everyone: if every executive owns the data they use, no one answers for shared data. The third is leaving the owner both to decide and to check: whoever authorises access cannot also verify it, a principle we find in segregation of duties.
Domande frequenti
Who is the data owner?
The person who, for a given data domain, decides purposes, access, acceptable quality, retention and exceptions, and is accountable for them to the organisation. It is not a technical role: as a rule it is a business manager with enough authority to decide and to have decisions carried out. The UK model describes it as a senior owner with dedicated responsibilities for data (Government Digital Service, 2026).
What does data ownership mean?
It means formally assigning responsibility for data to specific people, domain by domain. It does not denote ownership of the data: the UK model says so explicitly, and European law speaks of the data holder and the controller, that is, of rights, obligations and decisions on purposes and means. It is a governance function.
Is the data owner the owner of the data?
No. The GDPR does not use the expression “data owner”, and the Data Act does not confer ownership of data: it defines the data holder as the party with the right or obligation to use data and make it available. The data owner is an internal role an organisation establishes so that it knows who decides on a given data domain.
What is the difference between a data owner and a data controller?
The data controller is whoever determines the purposes and means of the processing of personal data, and is accountable for compliance with the GDPR (Arts. 4 and 24): as a rule, the organisation itself. The data owner is a person within the organisation to whom the controller may assign, under its own responsibility, tasks and decisions concerning data. Responsibility remains with the controller.
What is the difference between a data owner and a data steward?
The owner decides the rules and is accountable for them; the steward applies them in day-to-day work, looking after definitions, quality and the reporting of errors. The former answers for “what is permitted”, the latter for “how the data is kept in order”. An owner without a steward has no one to carry things out; a steward without an owner has no one to decide.
Who appoints the data owner?
Senior management, through a written act defining scope, decisions and limits. For personal data, the designation of persons acting under the controller’s authority is provided for by the Italian Privacy Code (Art. 2-quaterdecies). The top level approves the appointment system and checks that it works.
What level of seniority should a data owner have?
They must be senior enough to decide and to have decisions carried out without asking for permission each time. The UK model points to senior figures for large or complex datasets and lower levels for smaller ones (Government Digital Service, 2026). The criterion is not the title but authority: if they cannot say no to an access request, they are not an owner.
Does an SME need a data owner too?
Yes, but the role is lighter. In a small business it may coincide with the person already responsible for the area, for example the finance function for accounting data. Two things matter: that the name is written down and that there is only one owner per area. The rest of the system is scaled to the data that really matters.
Is the data owner liable in the event of a data breach?
The GDPR places responsibility on the controller (Art. 24), not on the data owner as a role. The internal liability of an appointed person depends on the organisation’s rules and on their employment relationship, and is not a matter this guide can settle: a specific case calls for legal advice.
Can the data owner and the DPO be the same person?
It is inadvisable. The DPO monitors compliance with the law and reports directly to the controller’s highest management level (GDPR, Art. 38(3)); the owner decides the purposes of and access to the data. If one person does both, they are checking their own decisions. The British model treats the data protection officer as a distinct role, with whom the owner works.
Fonti e riferimenti
- Government Digital Service, Data ownership model, GOV.UK, 2026
- Parlamento europeo e Consiglio, Regolamento (UE) 2016/679 (GDPR), artt. 4, 5, 24, 29, 38
- Parlamento europeo e Consiglio, Regolamento (UE) 2023/2854 (Data Act), art. 2
- Decreto legislativo 30 giugno 2003, n. 196 (Codice privacy), art. 2-quaterdecies
- ISO/IEC, ISO/IEC 38505-1:2026, Governance of data

