Skip to content

Law and sovereigntyReading time 7 min.

Data processing under Art. 28 GDPR – what the contract must cover

If you have personal data processed by a service provider, you remain responsible for it. The contract under Art. 28 GDPR defines how far the service provider may act and how you can measure their performance.

Managed by the Legal and privacy department

A closed purple cardboard document folder with a black elastic band on a light table, with a blank white sheet of paper and a black fountain pen on top.

At a glance

  • Data processing applies when a service provider processes personal data on behalf of and on the instructions of the controller, without deciding on the purposes and essential means themselves.
  • Art. 28(3) GDPR requires the contract to describe the scope of processing and define eight obligations of the processor, from being bound by instructions to audit rights.
  • Sub-processors may only be engaged with prior specific or general written authorisation; in the case of general authorisation, the controller must be informed of any changes and be able to object.

When data processing applies – and when it does not

Under Art. 4(8) GDPR, a processor is anyone who processes personal data on behalf of a controller. Under Art. 4(7) GDPR, a controller is anyone who determines the purposes and means of processing. The actual distribution of roles is decisive, not the title of the contract: anyone who processes on instructions remains a processor, even if they choose technical details such as hardware or storage methods themselves.

Typical cases include hosting, cloud infrastructure, backups, and sending messages on behalf of a controller. An infrastructure provider processes their customers' data even if they never look at its content: storage alone constitutes processing under Art. 4(2) GDPR.

Data processing generally does not apply if a service provider provides a professional service under their own responsibility – such as lawyers or tax advisors exercising their profession, banks making a bank transfer, or postal services transporting letters. If two bodies jointly determine the purposes and means, they are joint controllers under Art. 26 GDPR and must enter into an agreement under this provision.

A processor is also responsible for the contact and billing data of your contacts, as they need this for their own contract. If they determine the purposes and means of your data on their own authority, they are considered a controller in this respect under Art. 28(10) GDPR.

What the contract under Art. 28(3) must cover

Under Art. 28(3) GDPR, processing is carried out on the basis of a contract or other legal act that binds the processor to the controller. The subject matter and duration, nature and purpose of the processing, the type of personal data, the categories of data subjects, and the obligations and rights of the controller must be specified. In addition, there are eight obligations of the processor.

  • Instructions (lit. a): processing only on documented instructions, including with regard to transfers to a third country or an international organisation. If Union or Member State law requires processing, this must be communicated in advance, unless that law prohibits such communication on important grounds of public interest.
  • Confidentiality (lit. b): commitment of authorised persons to confidentiality or an appropriate statutory obligation of confidentiality.
  • Security (lit. c): all measures required pursuant to Art. 32 GDPR.
  • Sub-processors (lit. d): compliance with the conditions referred to in paragraphs 2 and 4.
  • Data subject rights (lit. e): assistance, insofar as this is possible, with appropriate technical and organisational measures for requests under Chapter III.
  • Further obligations (lit. f): assistance in ensuring compliance with the obligations pursuant to Art. 32 to 36 GDPR – security, notification and communication of personal data breaches, data protection impact assessment, prior consultation.
  • Deletion or return (lit. g): after the end of the provision of services and at the choice of the controller, including the deletion of existing copies, unless Union or Member State law requires storage.
  • Evidence and audits (lit. h): provision of all necessary information as evidence of the obligations and enabling audits including inspections by the controller or an auditor mandated by them.

If the processor considers an instruction to infringe data protection provisions, they must immediately inform the controller under Art. 28(3) subparagraph 2 GDPR. A mere repetition of the legal text is not sufficient according to the European Data Protection Board; the contract should describe how the obligations are fulfilled in practice.

Technical and organisational measures under Art. 32

Art. 32 GDPR obliges controllers and processors alike to ensure a level of security appropriate to the risk. The state of the art, the costs of implementation, the nature, scope, context and purposes of processing, as well as the likelihood and severity of the risk to data subjects, must be taken into account.

As examples, the provision mentions pseudonymisation and encryption, the ongoing assurance of confidentiality, integrity, availability and resilience of systems, rapid recovery after a physical or technical incident, and a process for regularly testing effectiveness. A contract that only promises “appropriate measures” cannot be measured against this; it only becomes verifiable with a description of the procedures, such as for encryption, rights management, logging, and tenant isolation.

Evidence supplements this description; it does not replace it. Under Art. 28(5) GDPR, adherence to approved codes of conduct under Art. 40 or an approved certification mechanism under Art. 42 may be used as an element to demonstrate sufficient guarantees. For certificates and attestations under other standards, the scope matters: it specifies the audited services and locations.

Sub-processors and form of the contract

Under Art. 28(2) GDPR, the processor may only engage another processor with the prior specific or general written authorisation of the controller. In the case of general authorisation, they must inform the controller of any intended addition or replacement so that the controller can object. The regulation does not specify a deadline for this; it belongs in the contract.

Under Art. 28 (4) GDPR, the sub-processor must be contractually bound by the same data protection obligations as set out in the contract with the controller. If they fail to fulfil them, the initial processor remains liable to the controller for compliance. Therefore, you should check not only the names on the list, but also the service, data access and country of establishment of each entry.

Regarding form, Art. 28 (9) GDPR stipulates that the contract must be in writing, including in electronic form; a contract concluded and documented electronically during the order process can meet this requirement.

Checklist for clients

The following questions are based on the structure of Art. 28 GDPR and supplement what the law leaves to the contract. They are suitable for review prior to concluding a contract as well as for procurement documents.

  • Are the subject matter, duration, nature and purpose of the processing, the type of data and categories of data subjects described or expressly left to your determination?
  • How are instructions issued, and is text form sufficient?
  • In which cases does the provider access content data, and is every access logged?
  • Are the technical and organisational measures described in detail, and what is the scope of the evidence?
  • Which sub-processors are used, with what service and in which country of establishment?
  • What is the notice period for changes, and what happens if you object?
  • Within what timeframe does the provider report a personal data breach?
  • How are on-site audits conducted, and what evidence is accepted instead?
  • What happens to the data at the end of the contract, within what timeframe and using which deletion method?

Record the reference for each answer. In the event of an audit by the supervisory authority, what is written in the contract is what counts.

How ENTRONYX handles data processing agreements

Insofar as you use the ENTRONYX infrastructure to process personal data, ENTRONYX Deutschland GmbH acts as a processor. The data processing agreement is concluded with the main contract and is an integral part of the contract without any separate request; no additional fee is charged for this. ENTRONYX does not negotiate alternative versions.

The subject matter is the provision of compute, storage and network capacity. You determine the nature and purpose of the processing, the categories of data subjects and the type of data; ENTRONYX has no knowledge of the content. Content data is only accessed in three cases: upon your explicit instruction as part of a support request, to avert a specific and acute threat to operations, or on the basis of a valid official order. Every access is logged and displayed to you in the customer panel.

Obligations under Art. 28 (3) GDPR and how they are regulated at ENTRONYX
MandatoryRegulation at ENTRONYX
Instructions (lit. a)Only documented instructions, text form is sufficient; an instruction considered unlawful will be reported to you and may be suspended until clarified.
Confidentiality (lit. b)Obligation of all employees, including after termination of employment.
Security (lit. c)Documented technical and organisational measures in accordance with Art. 32 GDPR.
Sub-processors (lit. d)General authorisation upon conclusion of the contract; changes are announced at least 30 days in advance. During this period, you can object and, if ENTRONYX does not remedy the objection, terminate the contract extraordinarily.
Assistance (lit. e and f)With data subject rights, data protection impact assessments and notifications. ENTRONYX will report a personal data breach to you no later than 24 hours after confirmed knowledge.
Deletion or return (lit. g)After the end of the contract, there is a 30-day grace period for export, after which the data is deleted; upon request, the grace period can be waived. Block and object storage are deleted by destroying the key and subsequently overwriting.
Evidence and audits (lit. h)C5 attestation, ISO 27001 certificate with scope and documentation of measures. On-site audit after notification with 30 days' notice, at most once per calendar year, except in the event of a specific incident.

The detailed regulations can be found in section 14 of the Privacy Policy; the data processing agreement template is available as a file.

The list of sub-processors specifies the country of establishment, service, scope and basis for each entry; the valid version is available in the customer panel. The measures under Art. 32 are described in detail on the Security and compliance page. The service is not certified under Art. 42 GDPR; as the controller, you decide whether your processing is permissible.

Note

This article is a general overview and does not constitute legal advice in individual cases. The wording of the regulation and the contract you conclude are authoritative.

Published on 8 November 2026. Prices and product values in this post are taken from the price list and reflect their current status.

Further reading

Read more

Questions for the department

Technical questions about a post are answered by the person responsible for the department — in a conversation, not a presentation. For quotes and framework agreements, sales will lead the initial conversation.