> For the complete documentation index, see [llms.txt](https://www.mica.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mica.wtf/mica.wtf/gdpr/chapter-iv-controller-and-processor-art.-24-43/28.md). # Art. 28 — Processor 1. Where [processing](https://headlesslaw.com/definitions/gdpr/processing/) is to be carried out on behalf of a [controller](https://headlesslaw.com/definitions/gdpr/controller/), the controller shall use only processors providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that processing will meet the requirements of this Regulation and ensure the protection of the rights of the data subject. 2. The [processor](https://headlesslaw.com/definitions/gdpr/processor/) shall not engage another processor without prior specific or general written authorisation of the controller. In the case of general written authorisation, the processor shall inform the controller of any intended changes concerning the addition or replacement of other processors, thereby giving the controller the opportunity to object to such changes. 3. Processing by a processor shall be governed by a contract or other legal act under Union or Member State law, that is binding on the processor with regard to the controller and that sets out the subject-matter and duration of the processing, the nature and purpose of the processing, the type of [personal data](https://headlesslaw.com/definitions/gdpr/personal-data/) and categories of data subjects and the obligations and rights of the controller. That contract or other legal act shall stipulate, in particular, that the processor: 1. processes the personal data only on documented instructions from the controller, including with regard to transfers of personal data to a third country or an [international organisation](https://headlesslaw.com/definitions/gdpr/international-organisation/), unless required to do so by Union or Member State law to which the processor is subject; in such a case, the processor shall inform the controller of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest; 2. ensures that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality; 3. takes all measures required pursuant to [Article 32](/mica.wtf/gdpr/chapter-iv-controller-and-processor-art.-24-43/32.md); 4. respects the conditions referred to in paragraphs 2 and 4 for engaging another processor; 5. taking into account the nature of the processing, assists the controller by appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the controller's obligation to respond to requests for exercising the data subject's rights laid down in Chapter III; 6. assists the controller in ensuring compliance with the obligations pursuant to [Articles 32](/mica.wtf/gdpr/chapter-iv-controller-and-processor-art.-24-43/32.md) to 36 taking into account the nature of processing and the information available to the processor; 7. at the choice of the controller, deletes or returns all the personal data to the controller after the end of the provision of services relating to processing, and deletes existing copies unless Union or Member State law requires storage of the personal data; 8. makes available to the controller all information necessary to demonstrate compliance with the obligations laid down in this Article and allow for and contribute to audits, including inspections, conducted by the controller or another auditor mandated by the controller. With regard to point (h) of the first subparagraph, the processor shall immediately inform the controller if, in its opinion, an instruction infringes this Regulation or other Union or Member State data protection provisions. 4. Where a processor engages another processor for carrying out specific processing activities on behalf of the controller, the same data protection obligations as set out in the contract or other legal act between the controller and the processor as referred to in paragraph 3 shall be imposed on that other processor by way of a contract or other legal act under Union or Member State law, in particular providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that the processing will meet the requirements of this Regulation. Where that other processor fails to fulfil its data protection obligations, the initial processor shall remain fully liable to the controller for the performance of that other processor's obligations. 5. Adherence of a processor to an approved code of conduct as referred to in [Article 40](/mica.wtf/gdpr/chapter-iv-controller-and-processor-art.-24-43/40.md) or an approved certification mechanism as referred to in [Article 42](/mica.wtf/gdpr/chapter-iv-controller-and-processor-art.-24-43/42.md) may be used as an element by which to demonstrate sufficient guarantees as referred to in paragraphs 1 and 4 of this Article. 6. Without prejudice to an individual contract between the controller and the processor, the contract or the other legal act referred to in paragraphs 3 and 4 of this Article may be based, in whole or in part, on standard contractual clauses referred to in paragraphs 7 and 8 of this Article, including when they are part of a certification granted to the controller or processor pursuant to [Articles 42](/mica.wtf/gdpr/chapter-iv-controller-and-processor-art.-24-43/42.md) and [43](/mica.wtf/gdpr/chapter-iv-controller-and-processor-art.-24-43/43.md). 7. The Commission may lay down standard contractual clauses for the matters referred to in paragraph 3 and 4 of this Article and in accordance with the examination procedure referred to in [Article 93(2)](/mica.wtf/gdpr/chapter-x-delegated-acts-and-implementing-acts-art.-92-93/93.md). 8. A [supervisory authority](https://headlesslaw.com/definitions/gdpr/supervisory-authority/) may adopt standard contractual clauses for the matters referred to in paragraph 3 and 4 of this Article and in accordance with the consistency mechanism referred to in [Article 63](/mica.wtf/gdpr/chapter-vii-cooperation-and-consistency-art.-60-76/63.md). 9. The contract or the other legal act referred to in paragraphs 3 and 4 shall be in writing, including in electronic form. 10. Without prejudice to [Articles 82](/mica.wtf/gdpr/chapter-viii-remedies-liability-and-penalties-art.-77-84/82.md), [83](/mica.wtf/gdpr/chapter-viii-remedies-liability-and-penalties-art.-77-84/83.md) and [84](/mica.wtf/gdpr/chapter-viii-remedies-liability-and-penalties-art.-77-84/84.md), if a processor infringes this Regulation by determining the purposes and means of processing, the processor shall be considered to be a controller in respect of that processing. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.mica.wtf/mica.wtf/gdpr/chapter-iv-controller-and-processor-art.-24-43/28.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.