Guide
Data Fiduciary or Data Processor: who carries which duty
The Act places its obligations on the Data Fiduciary, including for work done by its processors. A practical look at what that means on each side of the contract.
Almost every obligation in the Act is addressed to the Data Fiduciary. Before reading the obligations, an organisation needs to know which of its activities make it a fiduciary and which make it a processor. The answer can differ from one activity to the next.
The two definitions
“Data Fiduciary” means any person who alone or in conjunction with other persons determines the purpose and means of processing of personal data.
Section 2(i)
“Data Processor” means any person who processes personal data on behalf of a Data Fiduciary.
Section 2(k)
The test is who decides
The definitions turn on who determines the purpose and means of processing. An organisation that decides why personal data is collected and how it will be used is a Data Fiduciary for that processing. One that handles the data on the fiduciary's behalf is its Data Processor.
The Act gives an illustration in Section 6. A telecom service provider contracts with another company to email bills to its customers. The telecom provider is the Data Fiduciary and the company sending the emails is its Data Processor. When a customer opts to receive bills only in the app, the provider has to stop emailing and has to cause the processor to stop as well.
What the Act places on the fiduciary
- Responsibility for complying with the Act and the Rules for any processing undertaken by it or on its behalf by a Data Processor, irrespective of any agreement to the contrary (Section 8(1)).
- Engaging a Data Processor only under a valid contract (Section 8(2)).
- Reasonable security safeguards, including for processing by a Data Processor (Section 8(5)), with appropriate provision for them in the contract (Rule 6(1)(f)).
- On withdrawal of consent, ceasing processing and causing its Data Processors to cease (Section 6(6)).
- Causing its Data Processor to erase personal data that it made available for processing (Section 8(7)(b)).
- Retaining personal data, traffic data and logs for at least one year, for processing undertaken by it or on its behalf by a Data Processor (Rule 8(3)).
What that means for a processor
Because these duties sit with the fiduciary, a processor meets most of them through its contract. In practice a fiduciary will ask a processor to show its safeguards, to act on instructions to stop processing or erase data, to keep logs, and to tell it promptly of any incident, so that the fiduciary can meet its own time limits.
That a duty reaches a processor by contract does not make it optional. A processor that cannot do these things is one a fiduciary cannot safely engage.
One organisation, two roles
A company that processes customer data for its clients is their Data Processor. The same company is a Data Fiduciary for the data of its own employees, job applicants and sales contacts. Each role should be recorded separately, because the obligations differ.
A checklist for the contract
The first two items restate the Act and the Rules. The rest are terms we recommend, because they are how a fiduciary can meet duties that the Act places on it.
- Section 8(2)A valid contract is in place before the processor handles personal data.
- Rule 6(1)(f)The contract makes appropriate provision for the processor to take reasonable security safeguards.
- Good practiceThe processor acts only on the fiduciary's documented instructions.
- Good practiceThe contract states how quickly the processor tells the fiduciary of an incident, in support of the fiduciary's duty under Rule 7.
- Good practiceThe contract states how an instruction to stop processing or to erase data is given and confirmed, in support of Sections 6(6) and 8(7)(b).
- Good practiceThe processor keeps logs of processing for the period the fiduciary needs, in support of Rule 8(3).
- Good practiceAny further processor engaged by the processor is disclosed and bound by the same terms.
- Good practiceThe processor helps the fiduciary answer requests from Data Principals under Sections 11 and 12.
Related reading
Building a personal data inventory that stays current
The Act does not ask for an inventory by name, yet most of its duties depend on one. A method for building it and keeping it honest about what is still unknown.
Personal data breach intimation under Rule 7
Who has to be told, what they have to be told and by when, taken from the text of Section 8(6) and Rule 7, with the preparation that makes it achievable.
DPDP readiness: a starter checklist
Thirty questions, grouped by theme, to establish where an organisation stands before detailed assessment begins.