SERENSIA Data Processing Addendum (Article 28 of the GDPR)
SECTION I.
Clause 1 - Purpose and scope
a) The purpose of these Standard Contractual Clauses (the “Clauses”) is to ensure compliance with Article 28(3) and (4) of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation).
b) The controllers and processors listed in Annex I have agreed to these Clauses in order to ensure compliance with Article 28(3) and (4) of Regulation (EU) 2016/679 and/or Article 29(3) and (4) of Regulation (EU) 2018/1725.
c) These Clauses apply to the processing of personal data as specified in Annex II.
d) Annexes I to IV are an integral part of the Clauses.
e) These Clauses are without prejudice to obligations to which the controller is subject by virtue of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.
f) These Clauses do not by themselves ensure compliance with obligations related to international transfers in accordance with Chapter V of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.
Clause 2 - Invariability of the Clauses
a) The Parties undertake not to modify the Clauses, except for adding information to the Annexes or updating information in them.
b) This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a broader contract, or from adding other clauses or additional safeguards provided that they do not directly or indirectly contradict the Clauses or detract from the fundamental rights or freedoms of data subjects.
Clause 3 - Interpretation
a) Where these Clauses use the terms defined in Regulation (EU) 2016/679 or Regulation (EU) 2018/1725 respectively, those terms shall have the same meaning as in that Regulation.
b) These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679 or Regulation (EU) 2018/1725 respectively.
c) These Clauses shall not be interpreted in a way that runs counter to the rights and obligations provided for in Regulation (EU) 2016/679 / Regulation (EU) 2018/1725 or in a way that prejudices the fundamental rights or freedoms of the data subjects.
Clause 4 - Hierarchy
In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties existing at the time when these Clauses are agreed or entered into thereafter, these Clauses shall prevail.
Clause 5 - Docking Clause
a) Any entity that is not a Party to these Clauses may, with the agreement of all the Parties, accede to these Clauses at any time as a controller or a processor by completing the Annexes and signing Annex I.
b) Once the Annexes in (a) are completed and signed, the acceding entity shall be treated as a Party to these Clauses and have the rights and obligations of a controller or a processor, in accordance with its designation in Annex I.
c) The acceding entity shall have no rights or obligations resulting from these Clauses from the period prior to becoming a Party.
SECTION II. OBLIGATIONS OF THE PARTIES
Clause 6 - Description of the processing
The details of the processing operations, in particular the categories of personal data and the purposes of processing for which the personal data is processed on behalf of the controller, are specified in Annex II.
Clause 7 - Obligations of the Parties
7.1 Instructions
a) The processor shall process personal data only on documented instructions from the controller, unless required to do so by Union or Member State law to which the processor is subject. In this case, the processor shall inform the controller of that legal requirement before processing, unless the law prohibits this on important grounds of public interest. Subsequent instructions may also be given by the controller throughout the duration of the processing of personal data. These instructions shall always be documented.
b) The processor shall immediately inform the controller if, in the processor’s opinion, instructions given by the controller infringe Regulation (EU) 2016/679 / Regulation (EU) 2018/1725 or the applicable Union or Member State data protection provisions.
7.2 Purpose Limitation
The processor shall process the personal data only for the specific purpose(s) of the processing, as set out in Annex II, unless it receives further instructions from the controller.
7.3 Duration of the Processing of Personal Data
Processing by the processor shall only take place for the duration specified in Annex II.
7.4 Security of Processing
a) The processor shall at least implement the technical and organisational measures specified in Annex III to ensure the security of the personal data. This includes protecting the data against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to the data (personal data breach). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purposes of processing and the risks involved for the data subjects.
b) The processor shall grant access to the personal data undergoing processing to members of its personnel only to the extent strictly necessary for implementing, managing and monitoring of the contract. The processor shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
7.5 Sensitive Data
The processing activities covered by this Agreement do not involve special categories of personal data within the meaning of the GDPR. Accordingly, such data may not be processed by the Processor for the purposes agreed under the main agreement initially entered into between the Parties.
7.6 Documentation and Compliance
a) The Parties shall be able to demonstrate compliance with these Clauses.
b) The processor shall deal promptly and adequately with inquiries from the controller about the processing of data in accordance with these Clauses.
c) The processor shall make available to the controller all information necessary to demonstrate compliance with the obligations that are set out in these Clauses and stem directly from Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725. At the controller’s request, the processor shall also permit and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or an audit, the controller may take into account relevant certifications held by the processor.
d) The controller may choose to conduct the audit by itself or mandate an independent auditor. Audits may also include inspections at the premises or physical facilities of the processor and shall, where appropriate, be carried out with reasonable notice. Audits may be carried out subject to compliance with a minimum prior notice period of fifteen (15) days. In the event of an existing conflict of interest involving the third-party auditor, the processor may refuse the audit provided that it justifies such refusal in writing to the controller. In such case, the controller may propose another third-party auditor or conduct the audit itself.
e) The Parties shall make the information referred to in this Clause, including the results of any audits, available to the competent supervisory authority/ies on request.
7.7 Use of Subprocessors
a) GENERAL WRITTEN AUTHORISATION: The processor has the controller’s general authorisation for the engagement of subprocessors from an agreed list. The processor shall specifically inform in writing the controller of any intended changes of that list through the addition or replacement of subprocessors at least twenty-five (25) days in advance, thereby giving the controller sufficient time to be able to object to such changes prior to the engagement of the concerned subprocessor(s). The processor shall provide the controller with the information necessary to enable the controller to exercise the right to object.
b) Where the processor engages a subprocessor for carrying out specific processing activities (on behalf of the controller), it shall do so by way of a contract which imposes on the subprocessor, in substance, the same data protection obligations as the ones imposed on the processor in accordance with these Clauses. The processor shall ensure that the subprocessor complies with the obligations to which the processor is subject pursuant to these Clauses and to Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.
c) At the controller’s request, the processor shall provide a copy of such a subprocessor agreement and any subsequent amendments to the controller. To the extent necessary to protect business secrets or other confidential information, including personal data, the processor may redact the text of the agreement prior to sharing the copy.
d) The processor shall remain fully responsible to the controller for the performance of the subprocessor’s obligations in accordance with its contract with the subprocessor. The processor shall notify the controller of any failure by the subprocessor to fulfil its contractual obligations.
7.8 International Transfers
a) Any transfer of data to a third country or an international organisation by the processor shall only be carried out on the basis of documented instructions from the controller or in order to comply with a specific requirement of Union law or the law of the Member State to which the processor is subject, and shall be carried out in accordance with Chapter V of Regulation (EU) 2016/679 or Regulation (EU) 2018/1725.
b) The data controller agrees that where the processor engages a subprocessor in accordance with clause 7.7 to carry out specific processing activities (on behalf of the data controller) and where such processing activities involve a transfer of personal data within the meaning of Chapter V of Regulation (EU) 2016/679, the processor and the subprocessor may ensure compliance with Chapter V of Regulation (EU) 2016/679 by using the standard contractual clauses adopted by the Commission on the basis of Article 46(2) of Regulation (EU) 2016/679, provided that the conditions for the use of those standard contractual clauses are met.
Clause 8 - Assistance to the Controller
a) The processor shall promptly notify the controller of any request it has received from the data subject. It shall not respond to the request itself, unless authorised to do so by the controller.
b) The processor shall assist the controller in fulfilling its obligations to respond to data subjects’ requests to exercise their rights, taking into account the nature of the processing. In fulfilling its obligations in accordance with points (a) and (b), the processor shall comply with the controller’s instructions.
c) In addition to the processor’s obligation to assist the controller pursuant to Clause 8(b), the processor shall furthermore assist the controller in ensuring compliance with the following obligations, taking into account the nature of the data processing and the information available to the processor:
the obligation to carry out an assessment of the impact of the envisaged processing operations on the protection of personal data (“data protection impact assessment”) where a type of processing is likely to result in a high risk to the rights and freedoms of natural persons;
the obligation to consult the competent supervisory authority/ies prior to processing where a data protection impact assessment indicates that the processing would result in a high risk in the absence of measures taken by the controller to mitigate the risk;
the obligation to ensure that personal data is accurate and up to date, by informing the controller without delay if the processor becomes aware that the personal data it is processing is inaccurate or has become outdated;
(d) the obligations in Article 32 of Regulation (EU) 2016/679. The Parties shall set out in Annex III the appropriate technical and organisational measures by which the processor is required to assist the controller in the application of this Clause as well as the scope and extent of the assistance required.
Clause 9- Notification of Personal Data Breach
In the event of a personal data breach, the processor shall cooperate with and assist the controller for the controller to comply with its obligations under Articles 33 and 34 of Regulation (EU) 2016/679 or under Articles 34 and 35 of Regulation (EU) 2018/1725, where applicable, taking into account the nature of processing and the information available to the processor.
9.1 Data Breach Concerning Data Processed by the Controller
In the event of a personal data breach concerning data processed by the controller, the processor shall assist the controller:
a) in notifying the personal data breach to the competent supervisory authority/ies, without undue delay after the controller has become aware of it, where relevant, unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons;
b) in obtaining the following information which, pursuant to Article 33(3) of Regulation (EU) 2016/679, shall be stated in the controller’s notification, and must at least include:
the nature of the personal data including where possible, the categories and approximate number of data subjects concerned and the categories and approximate number of personal data records concerned;
the likely consequences of the personal data breach; and
the measures taken or proposed to be taken by the controller to address the personal data breach, including, where appropriate, measures to mitigate its possible adverse effects. Where, and insofar as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay;
c) in complying, pursuant to Article 34 of Regulation (EU) 2016/679, with the obligation to communicate without undue delay the personal data breach to the data subject, when the personal data breach is likely to result in a high risk to the rights and freedoms of natural persons.
9.2 Data Breach Concerning Data Processed by the Processor
In the event of a personal data breach concerning data processed by the processor, the processor shall notify the controller without undue delay after the processor having become aware of the breach. Such notification shall contain at least:
a) a description of the nature of the breach, including, where possible, the categories and approximate number of data subjects concerned and the categories and approximate number of personal data records concerned;
b) the details of a contact point where more information concerning the personal data breach can be obtained;
c) its likely consequences and the measures taken or proposed to be taken to address the breach, including to mitigate its possible adverse effects. Where, and insofar as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
The Parties shall set out in Annex III all other elements to be provided by the processor when assisting the controller in complying with the controller’s obligations under Articles 33 and 34 of Regulation (EU) 2016/679.
SECTION III. FINAL PROVISIONS
Clause 10 - Non-compliance with the Clauses and Termination
a) Without prejudice to any provisions of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725, in the event that the processor is in breach of its obligations under these Clauses, the controller may instruct the processor to suspend the processing of personal data until the processor complies with these Clauses or until the contract is terminated. The processor shall promptly inform the controller in case it is unable to comply with these Clauses, for whatever reason.
b) The controller shall be entitled to terminate the contract insofar as it concerns processing of personal data in accordance with these Clauses if: (1) the processing of personal data by the processor has been suspended by the controller pursuant to point (a) and compliance with these Clauses is not restored within a reasonable time and in any event within one month following suspension; (2) the processor is in substantial or persistent breach of these Clauses or its obligations under Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725; (3) the processor fails to comply with a binding decision of a competent court or the competent supervisory authority/ies regarding its obligations pursuant to these Clauses or to Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.
c) The processor shall be entitled to terminate the contract insofar as it concerns the processing of personal data under these Clauses where, after having informed the controller that its instructions infringe applicable legal requirements in accordance with Clause 7.1(b), the controller insists on compliance with the instructions.
d) Following termination of the contract, the processor shall, at the choice of the controller, delete all personal data processed on behalf of the controller and certify to the controller that it has done so, or return all personal data to the controller and delete existing copies unless Union or Member State law requires storage of the personal data. Until the data is deleted or returned, the processor shall continue to ensure compliance with these Clauses.
ANNEX I: List of parties
Data controller(s):
Name: Customer, as identified in the Agreement.
Name, position and contact details of the contact person for data protection matters: as specified in the Agreement.
Data processor:
Name: SERENSIA
Address: 15 rue des Mathurins, 75009 Paris, France
Function and contact details of the contact person for data protection matters: Data Protection Officer (France), privacyteam@quadient.com.
ANNEX II: Description of the processing
Categories of data subjects whose personal data are processed:
Serensia Accredited Platform (formerly PDP) / SIG / Safe:
The data subjects may vary depending on the nature of the documents processed: customer, supplier, employee of the Customer.
Serensia Supplier Portal:
Supplier of Serensia’s customer.
Categories of personal data processed:
The nature of the data may vary depending on the documents processed and the Customer’s ERP.
Identification data: surname, first name, contact details, etc.;
Economic and financial information: IBAN (micro-enterprise), invoice amounts, etc.
Nature of the processing:
Serensia Accredited Platform (formerly PDP) and SIG:
Access, hosting, extraction, use, modification, transmission.
Serensia Supplier Portal:
Collection.
Serensia Safe:
Hosting.
Purposes for which the personal data is processed on behalf of the Controller:
Serensia Accredited Platform (formerly PDP):
Management of e-invoicing and e-reporting;
Interoperability with other Accredited Platforms;
Directory interfacing.
Serensia SIG (Dematerialisation Operator “OD”):
automatic recovery of data from PDF/scanned invoices and paper invoices by means of OCR and integration into the ERP and/or business software;
Exchange of electronic invoices between supplier/customer information systems through EDI flows;
Automatic consultation of the supplier reference database to match invoices with existing purchase orders through integrated connectors;
Implementation of workflows for dematerialised approval circuits;
Automation or simplification of accounting allocation for invoices.
Serensia Supplier Portal:
Supplier portal to upload, track and correct invoices addressed to Serensia customers;
Automated reading with the Reader module (OCR);
Invoices are then hosted by the SIG solution.
Serensia Safe:
Legally probative archiving.
Duration of the processing: Duration of the Agreement signed with the Customer and any backups in accordance with the signed Agreement.
ANNEX III: Technical and Organisational Measures, Including Measures to Ensure the Security of the Data
Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of the processing, as well as the risk — the probability and severity of which vary — to the rights and freedoms of natural persons, the data importer has implemented appropriate technical and organisational measures designed to ensure a level of security appropriate to the risk.
Domain | Practices |
Organisation of information security | Security responsibility. Each Party shall appoint one or more security officers responsible for coordinating and overseeing security policies and procedures. Security roles and responsibilities. All personnel of each Party with access to data are subject to confidentiality obligations. Risk management programme. Each Party shall carry out a risk assessment before processing the data or launching the relevant service. Each Party shall retain its security documentation in accordance with its retention requirements after such documentation ceases to be in force |
Asset management | Asset inventory. Each Party shall maintain an inventory of all assets on which the data is stored. Access to such asset inventories must be limited to personnel who have been authorised in writing to access them. Asset management. Each Party shall classify data in order to identify it and appropriately restrict access to it. |
Human Resources Security | Security training. Each Party shall inform its personnel of the applicable security procedures and their respective roles. Each Party shall also inform its personnel of the possible consequences of breaching security rules and procedures. |
Physical and environmental security | Physical access to premises. Each Party restricts access to premises housing information systems processing data to identified and authorised persons. Protection against disruptions. Each Party uses different systems in line with industry standards to protect against data loss due to power outages or line disruptions. Component disposal. The controller uses standard procedures to delete data when it is no longer required. |
Communications and operations management | Data restoration procedures. Each Party stores data backups and data restoration procedures in a location separate from the main IT equipment used to process the data. Malware. Each Party shall implement anti-malware controls to prevent malicious software from obtaining unauthorised access to the data, including malware originating from public networks. Cross-border data: - Each Party shall encrypt data transmitted over public networks; - Each Party restricts access to data stored on media leaving its premises. Event logging. Each Party logs access to and use of information systems containing data, recording the access identifier, time, authorisation granted or denied, and corresponding activity. |
Access Control | Access policy. Each Party shall maintain a record of the security privileges of persons having access to the data. Access authorisation: - Each Party shall disable authentication credentials that have not been used for a period not exceeding six months; - Each Party shall identify personnel who may grant, modify or revoke authorised access to data and resources; - Each Party shall ensure that persons have unique identifiers/logins. Need-to-know - Technical support personnel are authorised to access data only on a need-to-know basis. Each Party shall limit access to data to those persons who need such access to perform their duties. Integrity and confidentiality: - Each Party shall require its personnel to close administration sessions when leaving premises under its control or when computers are left unattended; - Each Party shall store passwords in a manner that renders them unintelligible when used. Authentication: - Each Party shall use industry-standard practices to identify and authenticate users attempting to access information systems; where authentication mechanisms rely on passwords, - Each Party shall require passwords to be changed regularly; - Each Party shall ensure that disabled or expired identifiers are not assigned to other persons; - Each Party shall maintain standard procedures for disabling passwords that have been compromised or inadvertently disclosed; - Each Party uses industry-standard password protection practices, including practices designed to preserve the confidentiality and integrity of passwords when assigned and distributed, and when stored. Network design. Each component includes controls designed to prevent persons from obtaining access rights that have not been granted to them in order to access data they are not authorised to view. |
Information Security Incident Management | Incident response process: - Each Party maintains a record of security breaches, including a description of the breach, the period concerned, the consequences of the breach, the source of the report, and the main mitigation and recovery measures. - For each breach constituting a security incident, the processor shall notify the controller without undue delay. Service monitoring. Operational personnel of each Party regularly review logs in order to propose corrective actions where necessary. |
Business continuity management | The controller maintains contingency and disaster recovery plans for premises housing its information systems that process data. |
ANNEX IV: List of SERENSIA Subprocessors
Nature of the operations | Name of the Subsequent Subcontractor | Address | Certifications | Personal Data Processed |
Hosting of personal data of the Serensia Accredited Platform (formerly PDP) solution | Thales Cloud Sécurisé (S3NS) | 54-56 avenue Hoche, 75008 Paris, France | SecNumCloud 3.2, ISO/IEC 27001/22301 | Solution data |
Hosting of personal data of the Serensia SIG, Supplier Portal and Safe solutions | OVH SAS | 2 rue Kellermann, 59100 Roubaix, France | ISO 27001, SecNumCloud | Solution data |
Sending emails from the solution to users | Sendinblue SAS (Brevo) | 9-17, rue Salneuve, 75017 Paris, France | ISO 27001 | Surname, first name, email address |











