Spanish Data Protection Act, articles 28 to 39: controllers, processors and the data protection officer
Organic Law 3/2018 on the Protection of Personal Data, articles 28 to 39: the general obligations of controllers and processors and the higher-risk situations they must assess, joint controllers, representatives of controllers and processors not established in the European Union, the record of processing activities and the blocking of data. It also covers the processor, the cases in which a data protection officer must be appointed, the officer’s qualification, position and role in complaints, codes of conduct and the accreditation of certification bodies.
Title V. Controller and processor
Chapter I. General provisions. Active accountability measures
Article 28. General obligations of the controller and processor
1. Controllers and processors, taking into account the elements listed in articles 24 and 25 of Regulation (EU) 2016/679, shall determine the appropriate technical and organisational measures they must apply in order to ensure and demonstrate that the processing complies with that Regulation, with this Organic Law, its implementing rules and the applicable sectoral legislation. In particular, they shall assess whether a data protection impact assessment and the prior consultation referred to in Section 3 of Chapter IV of that Regulation are required.
2. In adopting the measures referred to in the preceding paragraph, controllers and processors shall take into account, in particular, the greater risks that could arise in the following cases:
a) Where the processing could give rise to discrimination, identity theft or fraud, financial loss, damage to reputation, loss of confidentiality of data subject to professional secrecy, unauthorised reversal of pseudonymisation or any other significant economic, moral or social harm to the data subjects.
b) Where the processing could deprive data subjects of their rights and freedoms or could prevent them from exercising control over their personal data.
c) Where there is processing, not merely incidental or ancillary, of the special categories of data referred to in articles 9 and 10 of Regulation (EU) 2016/679 and articles 9 and 10 of this Organic Law, or of data relating to the commission of administrative offences.
d) Where the processing involves an evaluation of personal aspects of the data subjects in order to create or use personal profiles of them, in particular through the analysis or prediction of aspects concerning their performance at work, economic situation, health, personal preferences or interests, reliability or behaviour, financial solvency, location or movements.
e) Where data of groups of data subjects in a situation of particular vulnerability are processed, and in particular data of minors and persons with disabilities.
f) Where there is large-scale processing involving a large number of data subjects or entailing the collection of a large amount of personal data.
g) Where the personal data are to be transferred, on a regular basis, to third States or international organisations in respect of which an adequate level of protection has not been declared.
h) Any others which, in the opinion of the controller or processor, could be relevant, and in particular those provided for in codes of conduct and standards defined by certification schemes.
Article 29. Cases of joint controllership
The responsibilities referred to in article 26.1 of Regulation (EU) 2016/679 shall be determined according to the activities actually carried out by each of the joint controllers.
Article 30. Representatives of controllers or processors not established in the European Union
1. Where Regulation (EU) 2016/679 applies to a controller or processor not established in the European Union by virtue of article 3.2 thereof and the processing concerns data subjects who are in Spain, the Spanish Data Protection Agency (AEPD) or, where applicable, the regional data protection authorities may impose on the representative, jointly and severally with the controller or processor, the measures established in Regulation (EU) 2016/679.
That requirement shall be without prejudice to any liability that may fall on the controller or processor and to the representative’s exercise of a right of recourse against whoever is appropriate.
2. Likewise, where liability is claimed under article 82 of Regulation (EU) 2016/679, controllers, processors and representatives shall be jointly and severally liable for the damage caused.
Article 31. Record of processing activities
1. Controllers and processors or, where applicable, their representatives must keep the record of processing activities referred to in article 30 of Regulation (EU) 2016/679, unless the exception provided for in paragraph 5 of that article applies.
The record, which may be organised around structured sets of data, must specify, according to their purposes, the processing activities carried out and the other particulars established in that Regulation.
Where the controller or processor has appointed a data protection officer, they must notify the officer of any addition, modification or deletion in the content of the record.
2. The bodies listed in article 77.1 of this Organic Law shall make public an inventory of their processing activities, accessible by electronic means, setting out the information established in article 30 of Regulation (EU) 2016/679 and its legal basis.
Article 32. Blocking of data
1. The controller shall be obliged to block the data when it rectifies or erases them.
2. Blocking of data consists of identifying and reserving the data, adopting technical and organisational measures to prevent their processing, including their viewing, except for making the data available to judges and courts, the Public Prosecutor’s Office or the competent public administrations, in particular the data protection authorities, for the purpose of claiming any liability arising from the processing, and only for the limitation period of such liability.
Once that period has elapsed, the data must be destroyed.
3. Blocked data may not be processed for any purpose other than that indicated in the preceding paragraph.
4. Where, in order to comply with this obligation, the configuration of the information system does not permit blocking or would require an adaptation involving disproportionate effort, a secure copy of the information shall be made so that there is digital or other evidence capable of proving its authenticity, the date of blocking and that the data were not manipulated during the blocking.
5. The Spanish Data Protection Agency and the regional data protection authorities, within their respective spheres of competence, may establish exceptions to the blocking obligation laid down in this article in cases where, given the nature of the data or the fact that they concern a particularly large number of data subjects, their mere retention, even when blocked, could create a high risk to the rights of the data subjects, as well as in cases where the retention of the blocked data could involve a disproportionate cost for the controller.
Chapter II. Processor
Article 33. Processor
1. Access by a processor to the personal data needed to provide a service to the controller shall not be considered a disclosure of data, provided that the provisions of Regulation (EU) 2016/679, this Organic Law and its implementing rules are complied with.
2. A person who, in their own name and without it being shown that they act on behalf of another, establishes relations with the data subjects shall be considered a controller and not a processor, even where there is a contract or legal act with the content laid down in article 28.3 of Regulation (EU) 2016/679. This provision shall not apply to processing assignments made under public sector procurement legislation.
A person who, while appearing as a processor, uses the data for their own purposes shall also be considered a controller.
3. The controller shall determine whether, when the processor’s services end, the personal data must be destroyed, returned to the controller or, where applicable, handed over to a new processor.
The data shall not be destroyed where a legal provision requires them to be retained, in which case they must be returned to the controller, who shall ensure their retention for as long as that obligation persists.
4. The processor may retain the data, duly blocked, for as long as liability could arise from its relationship with the controller.
5. In the public sector, the powers of a processor may be assigned to a specific body of the General State Administration, the Administration of the Autonomous Communities, the entities making up the Local Administration or the bodies attached to or dependent on them, by adopting a rule governing those powers, which must include the content required by article 28.3 of Regulation (EU) 2016/679.
Chapter III. Data protection officer
Article 34. Appointment of a data protection officer
1. Controllers and processors must appoint a data protection officer in the cases provided for in article 37.1 of Regulation (EU) 2016/679 and, in any event, in the case of the following entities:
a) Professional associations (colegios profesionales) and their general councils.
b) Educational establishments offering education at any of the levels established in the legislation governing the right to education, as well as public and private universities.
c) Entities that operate networks and provide electronic communications services in accordance with their specific legislation, where they habitually and systematically process personal data on a large scale.
d) Information society service providers where they carry out large-scale profiling of the users of the service.
e) The entities included in article 1 of Law 10/2014 of 26 June on the regulation, supervision and solvency of credit institutions.
f) Financial credit establishments.
g) Insurance and reinsurance undertakings.
h) Investment firms regulated by securities market legislation.
i) Distributors and suppliers of electricity and distributors and suppliers of natural gas.
j) Entities responsible for common files for assessing financial solvency and credit or common files for fraud management and prevention, including the controllers of files governed by legislation on the prevention of money laundering and terrorist financing.
k) Entities carrying out advertising and commercial prospecting activities, including commercial and market research, where they carry out processing based on the preferences of data subjects or carry out activities involving profiling of them.
l) Health centres legally obliged to keep patients’ clinical records.
Health professionals who, although legally obliged to keep patients’ clinical records, practise on an individual basis are excepted.
m) Entities one of whose purposes is to issue commercial reports that may refer to natural persons.
n) Operators carrying on gaming activity through electronic, computer, telematic and interactive channels, in accordance with gaming regulations.
ñ) Private security companies.
o) Sports federations where they process data of minors.
2. Controllers or processors not included in the preceding paragraph may voluntarily appoint a data protection officer, who shall be subject to the regime established in Regulation (EU) 2016/679 and in this Organic Law.
3. Controllers and processors shall notify the Spanish Data Protection Agency or, where applicable, the regional data protection authorities, within ten days, of the designations, appointments and removals of data protection officers, both where they are obliged to appoint one and where the appointment is voluntary.
4. The Spanish Data Protection Agency and the regional data protection authorities shall, within their respective spheres of competence, keep an up-to-date list of data protection officers, accessible by electronic means.
5. In complying with the obligations of this article, controllers and processors may provide for the officer to work full time or part time, depending, among other criteria, on the volume of processing, the special category of the data processed or the risks to the rights or freedoms of the data subjects.
Article 35. Qualification of the data protection officer
Compliance with the requirements laid down in article 37.5 of Regulation (EU) 2016/679 for the appointment of the data protection officer, whether a natural or legal person, may be demonstrated, among other means, through voluntary certification mechanisms which shall take particular account of a university degree demonstrating specialised knowledge of data protection law and practice.
Article 36. Position of the data protection officer
1. The data protection officer shall act as the point of contact of the controller or processor with the Spanish Data Protection Agency and the regional data protection authorities. The officer may inspect procedures related to the subject matter of this Organic Law and issue recommendations within the scope of their competence.
2. Where the officer is a natural person integrated into the organisation of the controller or processor, the data protection officer may not be removed or penalised by the controller or processor for performing their duties unless they act with intent or gross negligence in performing them. The independence of the data protection officer within the organisation shall be guaranteed, and any conflict of interest must be avoided.
3. In performing their duties, the data protection officer shall have access to the personal data and processing operations, and the controller or processor may not invoke against that access any duty of confidentiality or secrecy, including that provided for in article 5 of this Organic Law.
4. Where the data protection officer finds a significant breach in data protection matters, the officer shall document it and report it immediately to the administrative and management bodies of the controller or processor.
Article 37. Involvement of the data protection officer in the event of a complaint to the data protection authorities
1. Where the controller or processor has appointed a data protection officer, the data subject may, before lodging a complaint against them with the Spanish Data Protection Agency or, where applicable, with the regional data protection authorities, address the data protection officer of the entity against which the complaint is made.
In that case, the data protection officer shall inform the data subject of the decision taken within a maximum of two months from receipt of the complaint.
2. Where the data subject lodges a complaint with the Spanish Data Protection Agency or, where applicable, with the regional data protection authorities, those authorities may forward the complaint to the data protection officer so that the officer may respond within one month.
If, once that period has elapsed, the data protection officer has not informed the competent data protection authority of the response given to the complaint, that authority shall continue the procedure in accordance with Title VIII of this Organic Law and its implementing rules.
3. The procedure before the Spanish Data Protection Agency shall be that established in Title VIII of this Organic Law and its implementing rules. Likewise, the Autonomous Communities shall regulate the corresponding procedure before their regional data protection authorities.
Chapter IV. Codes of conduct and certification
Article 38. Codes of conduct
1. The codes of conduct governed by section 5 of Chapter IV of Regulation (EU) 2016/679 shall be binding on those who adhere to them.
Such codes may provide for out-of-court dispute resolution mechanisms.
2. In addition to the associations and bodies referred to in article 40.2 of Regulation (EU) 2016/679, such codes may be promoted by undertakings or groups of undertakings and by the controllers or processors referred to in article 77.1 of this Organic Law.
They may also be promoted by the bodies or entities that assume the functions of supervision and out-of-court dispute resolution referred to in article 41 of Regulation (EU) 2016/679.
Controllers or processors that adhere to the code of conduct undertake to submit to the supervisory body or entity the complaints made to them by data subjects in relation to the processing of data within its scope, where they consider that the request in the complaint should not be granted, without prejudice to article 37 of this Organic Law. In addition, without prejudice to the powers conferred by Regulation (EU) 2016/679 on the data protection authorities, they may voluntarily, and before carrying out the processing, submit to that supervisory body or entity the verification of the conformity of the processing with the matters covered by the code of conduct.
If the supervisory body or entity rejects or dismisses the complaint, or if the controller or processor does not submit the complaint to its decision, the data subject may lodge it with the Spanish Data Protection Agency or, where applicable, the regional data protection authorities.
The competent data protection authority shall verify that the bodies or entities promoting the codes of conduct have provided those codes with supervisory bodies that meet the requirements established in article 41.2 of Regulation (EU) 2016/679.
3. Codes of conduct shall be approved by the Spanish Data Protection Agency or, where applicable, by the competent regional data protection authority.
4. The Spanish Data Protection Agency or, where applicable, the regional data protection authorities shall submit draft codes to the consistency mechanism referred to in article 63 of Regulation (EU) 2016/679 in the cases where this is appropriate under article 40.7 thereof. The procedure shall be suspended until the European Data Protection Board issues the opinion referred to in articles 64.1.b) and 65.1.c) of that Regulation.
Where it is a regional data protection authority that submits the draft code to the consistency mechanism, article 60 of this Organic Law shall apply.
5. The Spanish Data Protection Agency and the regional data protection authorities shall keep registers of the codes of conduct they have approved, which shall be interconnected with each other and coordinated with the register managed by the European Data Protection Board under article 40.11 of that Regulation.
The register shall be accessible by electronic means.
6. The content of the register and the specific features of the procedure for approving codes of conduct shall be established by royal decree.
Article 39. Accreditation of certification bodies
Without prejudice to the accreditation functions and powers of the competent supervisory authority under articles 57 and 58 of Regulation (EU) 2016/679, the accreditation of the certification bodies referred to in article 43.1 of that Regulation may be carried out by the National Accreditation Entity (ENAC), which shall notify the Spanish Data Protection Agency and the data protection authorities of the Autonomous Communities of the grants, refusals or revocations of accreditations, together with the reasons for them.
Where this sits
Previous: Data Protection Act, articles 19 to 27: specific processing. Next: Data Protection Act, articles 70 to 78 and 87 to 91: penalties and workplace rights. All translated laws: Spanish laws in English.
Related on voixa.es: Cookie consent in Spain: LSSI and AEPD; Email marketing opt-in rules in Spain; Hiring your first employee in Spain.
Nothing here is advice on your own position, and this reading is not the official text. Spain publishes no official English version of this text; where the wording matters to a decision, read it against the Spanish original published in the BOE.