Texts to 22 Oct 2026

Amendment 374· Digital Omnibus proposal Recital 38a (new)

Addition

Tabled by
Axel Voss (EPP)
Committee and document
ITRE–LIBE·amendments 251–400 to the draft report (CJ72-AM-790967, PE790.967v01-00)·27 July 2026
Source
Official text, pp. 138–140·printed header: Recital 38 a (new)
Targets
Recital 38a (new) of the Digital Omnibus proposal

Text of the amendment

As tabled

Wording it would add

(38a)To ensure compliance with the requirements of this Regulation in respect of the processing to be carried out by the processor on behalf of the controller, when entrusting a processor with processing activities, the controller should use only processors providing sufficient guarantees, in particular in terms of expert knowledge, reliability and resources, to implement technical and organisational measures which will meet the requirements of this Regulation, including for the security of processing. The adherence of the processor to an approved code of conduct or an approved certification mechanism may be used as an element to demonstrate compliance with the obligations of the controller. If processing by a processor is governed by an agreement with the controller which specifies the subject matter and duration of the processing, the nature and purpose of the processing, the types of data to be processed and the categories of data subjects the tasks and duties of the processor shall be directly qualified by this Regulation in order to avoid legal uncertainty and provide clear standards for all parties, which process personal data within the scope of European law. Furthermore, if the processor provides a binding assurance as to the level of protection to which it is able to ensure the security of the processing and its obligation to assist the controller by means of appropriate technical and organisational measures and confirms the suitability of these safeguards for the processing operations it intends to carry out, due to the nature of these services as mere digital infrastructure Services their agreements may renounce on some specific notification requirements of controllers. However, processors who fail to fulfil those assurances are directly liable for this non compliance. After the completion of the processing on behalf of the controller, the processor should, at the choice of the controller, return or delete the personal data, unless there is a requirement to store the personal data under Union or Member State law to which the processor is subject.

Justification

Article 28 should better reflect modern cloud, hosting, security and infrastructure services, which are standardised, layered and technically complex. For such infrastructure processing, controllers need enforceable assurances on security, assistance and downstream liability, not bespoke descriptions of every technical sub-operation. The amendment cuts formalistic contract burdens while preserving core duties: confidentiality, security, assistance, deletion or return, audits, controller suitability checks and processor liability for sub-processors.

Target

Wording of the targeted provisionlaw in force, Commission proposal, latest Council text

No Council text amends Recital 38a (new).

Cite this amendment

Amendment 374 (Axel Voss), European Parliament, Committee on Industry, Research and Energy and Committee on Civil Liberties, Justice and Home Affairs, amendments 251–400 to the draft report on COM(2025) 837 (CJ72-AM-790967, PE790.967v01-00, 27 July 2026), pp. 138–140

Link, short form and official text
Reference

Amendment 374 (Axel Voss), European Parliament, Committee on Industry, Research and Energy and Committee on Civil Liberties, Justice and Home Affairs, amendments 251–400 to the draft report on COM(2025) 837 (CJ72-AM-790967, PE790.967v01-00, 27 July 2026), pp. 138–140

Short form

ITRE–LIBE Amendment 374 (CJ72-AM-790967), p. 138

Entry in the source list