DATA PROCESSING AGREEMENT

Background

This Data Processing Agreement (hereinafter, the "Agreement") governs the conditions of the processing of personal data arising from the provision of the OPEREA Platform services. Its acceptance by the CLIENT during the contracting process is an essential precondition to the commencement of the provision of the Services. For the purposes of this Agreement, the CLIENT acts as CONTROLLER (Data Controller) and WORKSY TECH, S.L. (trading as OPEREA; hereinafter, "WORKSY" or the "PROCESSOR") acts as PROCESSOR (Data Processor).

This Agreement is based on the following facts:

  1. That the PROCESSOR is engaged in the development of its own software and its subsequent commercialisation through the corresponding SaaS Service Agreements.
  2. That the CONTROLLER and the PROCESSOR have entered into an OPEREA Platform Service Agreement (hereinafter, the "Agreement" or the "Service Agreement").
  3. That the provision of the services set out in the said Service Agreement requires access to personal data by the PROCESSOR, under the instructions of the CONTROLLER.
  4. That, in order to comply with the Personal Data Protection regulations, specifically 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 (hereinafter, "GDPR") and Organic Law 3/2018, of 5 December, on the Protection of Personal Data and the guarantee of digital rights (hereinafter, "LOPD-GDD"), both Parties agree to the following clauses.

Clauses

1. SUBJECT MATTER OF THE PROCESSING ASSIGNMENT

The purpose of this Agreement is to define, in accordance with the provisions of Article 28 of the GDPR and the remaining applicable data protection regulations, the conditions under which the PROCESSOR, on the instructions of the CONTROLLER, shall carry out the processing of personal data necessary for the provision of the services contracted under the Service Agreement.

The subject matter, nature and purpose of the data processing to be carried out by the PROCESSOR, as well as the type of personal data and categories of data subjects to which such processing relates, are those detailed in Appendix I of this Agreement, as well as, where applicable, in any subsequent updates that the Parties may agree in respect thereof.

2. IDENTIFICATION OF THE INFORMATION AFFECTED

For the execution of the services arising from the fulfilment of the subject matter of this assignment, the CONTROLLER makes available to the entity acting as PROCESSOR the information described below:

  • Employment and personal data of the CLIENT's employees, including: identification data, working-time and attendance data, remuneration data, employment contract documents and, where applicable, geolocation data for on-site attendance control, which the CLIENT has collected on the basis of Art. 6.1.c (legal obligation) for clock-in —Art. 34.9 of the Workers' Statute—, 6.1.b for payroll/contract management, 6.1.f + Art. 90 LOPD-GDD for geolocation, and 9.2.b for health data (sick leave / temporary disability).

The artificial intelligence features of the Platform are designed in accordance with Regulation (EU) 2024/1689 on Artificial Intelligence: people are informed when they interact with an AI system (the voice agent tells every person it speaks with that it is an AI), and AI outputs in recruitment or employment decisions are assistive and subject to human review and decision by the CLIENT, with no decisions based solely on automated processing that produce legal or similarly significant effects (Art. 22 GDPR).

Voice agent calls are not recorded by default. The CLIENT may enable call recording as an optional setting that is off by default; if enabled, recordings are kept for 30 days so the CLIENT can review them and are deleted afterwards, and the CLIENT is responsible for informing the people called of the recording.

Built-in AI assistant ("Nara"). When the CLIENT enables the Platform's AI assistant, it processes, on the CLIENT's behalf and only at the request of its manager users, the Platform data that the user can access, through Google Cloud Vertex AI (Gemini) in the EU multi-region. Files the user attaches are processed in isolated sandboxes on Google Cloud (EU). Conversations are kept for 90 days and attached files for 7 days, after which they are deleted. CLIENT data is not used to train AI models. Assistant actions that change data require the user's confirmation, unless the CLIENT's administrator turns that confirmation off. Use of the assistant counts against the CLIENT's credits.

3. DURATION

This Agreement has a duration as defined and governed in the Service Agreement. Once the said Service Agreement ends, the PROCESSOR shall return to the CONTROLLER the personal data, as well as any copies in its possession.

4. OBLIGATIONS OF THE PROCESSOR

The PROCESSOR and all its personnel undertake to:

4.1. Use the personal data subject to processing, or that which it collects for inclusion, solely for the purpose of this assignment. Under no circumstances may it use the data for its own purposes or those of third parties, or for purposes other than the subject matter of the provision of the service governed by this Agreement.

4.2. Process the data in accordance with the instructions of the CONTROLLER.

If the PROCESSOR considers that any of the instructions infringes the GDPR, the LOPD-GDD or any other Union or Member State data protection provision, the PROCESSOR shall immediately inform the CONTROLLER.

4.3. Keep, in writing, a record of all categories of processing activities carried out on behalf of the CONTROLLER, containing:

  1. The name and contact details of the PROCESSOR and of each controller on whose behalf the PROCESSOR acts and, where applicable, of the controller's or processor's representative and of the data protection officer.
  2. The categories of processing carried out on behalf of each controller.
  3. Where applicable, transfers of personal data to a third country or international organisation, including the identification of that third country or international organisation and, in the case of transfers referred to in the second subparagraph of Article 49(1) of the GDPR, the documentation of suitable safeguards.
  4. A general description of the technical and organisational security measures relating to:
    1. The pseudonymisation and encryption of personal data.
    2. The ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services.
    3. The ability to restore the availability of and access to personal data in a timely manner in the event of a physical or technical incident.
    4. The process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing.

4.4. Not disclose the data to third parties, unless it has the express authorisation of the CONTROLLER, in the cases legally permitted.

The PROCESSOR may disclose the data to other processors of the same CONTROLLER, in accordance with the CONTROLLER's instructions. In this case, the CONTROLLER shall identify, in advance and in writing, the entity to which the data are to be disclosed, the data to be disclosed and the security measures to be applied in order to proceed with the disclosure.

If the PROCESSOR must transfer personal data to a third country or to an international organisation, under Union or Member State law applicable to it, it shall inform the CONTROLLER of that legal requirement in advance, unless that law prohibits such information on important grounds of public interest.

4.5. Sub-processing

In connection with the provision of the service, the CONTROLLER authorises the PROCESSOR to engage the sub-processing detailed below:

  1. Sub-processing of cloud data storage services:
    • Company name: Google Cloud EMEA Limited
    • Tax ID: IE3668997OH
    • Contact details and address: 70 Sir John Rogerson's Quay, Dublin 2, Ireland
    • Service description: cloud data storage
    • The service involves a transfer of data to an environment with an adequate level of data protection, as a Google datacenter located within the Authorised Territory (EU) is used and therefore meets all GDPR requirements. Google defines its legal entity at: https://cloud.google.com/terms/google-entity
  2. Sub-processing of reverse proxy and CDN services:
    • Company name: Cloudflare, Inc. (contracting entity for the EEA: Cloudflare Ireland Limited)
    • Tax ID/Reg.: IE639765R (Ireland)
    • Contact details and address: 101 Townsend Street, San Francisco, CA 94107, USA — EU Representative: County Hall / The Riverside Building, Belvedere Road, London SE1 7PB, United Kingdom · [email protected]
    • Service description: Reverse proxy, content delivery network (CDN), DDoS protection and web application security.
    • The service involves a transfer of data to an environment with an adequate level of data protection. Cloudflare is certified under the EU-US Data Privacy Framework (DPF) and uses Standard Contractual Clauses (SCCs) approved by the European Commission for international transfers. Data may be routed through global network nodes, although Cloudflare offers an EU jurisdiction configuration to restrict processing to European datacenters. DPA available at: https://www.cloudflare.com/cloudflare-customer-dpa/
  3. Sub-processing of transactional email delivery services:
    • Company name: Mailgun Technologies, Inc., a subsidiary of Sinch AB (publ), a Swedish listed company with its registered office at Lindhagensgatan 112, 112 51 Stockholm, Sweden (commercial name of the service: Mailgun). Sinch Email is the Developer & Email business unit of Sinch and groups the Mailgun, Mailjet, Email on Acid and InboxReady brands.
    • Tax ID/Reg.: Mailgun Technologies, Inc. — a Delaware company, USA. Parent company: Sinch AB (publ), org. no. 556882-8433 (Sweden) · VAT: SE556882843301
    • Contact details and address: Mailgun Technologies, Inc., 112 E. Pecan St., Suite 1135, San Antonio, TX 78205, USA · Sinch group DPO: [email protected] · Mailgun privacy contact: [email protected]
    • Service description: Delivery of notifications and communications by transactional email to the CLIENT's users and employees through the OPEREA Platform (confirmations, operational alerts, shift notifications, employment documentation).
    • Sinch Email complies with European GDPR 2016/679 and all applicable data protection laws. For all transfers of personal data from the EU and the EEA, Sinch maintains EU Standard Contractual Clauses (SCCs) where necessary, ensures additional safeguards such as encryption and data minimisation, and carries out transfer impact assessments (TIAs), audits and controls over its sub-processors. Mailgun Technologies, Inc. is certified under the EU-US Data Privacy Framework (EU-US DPF) and the UK Extension to the EU-US DPF. The parent company Sinch AB is domiciled in Sweden (EU), which provides an additional layer of oversight under European law. DPA available at: https://www.mailgun.com/legal/dpa/
  4. Sub-processing of artificial intelligence model services:
    • Company name: Google Cloud EMEA Limited (the same provider and contract as in section 1)
    • Tax ID: IE3668997OH
    • Contact details and address: 70 Sir John Rogerson's Quay, Dublin 2, Ireland
    • Service description: Access to artificial intelligence models (Google Gemini through Google Cloud Vertex AI) for the AI functionalities of the OPEREA Platform, when available and enabled by the CLIENT: voice agent and real-time voice conversations with workers and client contacts, report generation, planning assistant, predictive analytics, CV screening, automated interviews, absenteeism and turnover prediction, and the built-in AI assistant described in section 2.
    • All AI processing takes place on Vertex AI within the EU (EU multi-region), and therefore within the Authorised Territory (EU), meeting GDPR requirements without any international transfer. Files attached to the assistant are also processed in isolated sandboxes on Google Cloud (EU). Customer data is not used to train Google's AI/ML models without prior authorisation or instruction: the specific service terms (section 17, "Training Restriction") make this an explicit contractual commitment. To prevent abuse, Google may retain prompts and responses that its automated systems flag as possible misuse for up to 90 days, within the EU, solely to detect and prevent abuse and in accordance with its terms of service. Google Cloud sub-processors available at: https://cloud.google.com/terms/subprocessors
    • OPEREA does not record or transcribe voice agent calls by default; it keeps their times, outcome and, for a decline, the reason given. A recording exists only if the CLIENT enables it (see section 2).
  5. Sub-processing of voice and SMS communication services:
    • Company name: Twilio Ireland Limited
    • Tax ID/Reg.: Reg. no. IE516075 (Ireland)
    • Contact details and address: 70 Sir John Rogerson's Quay, Dublin 2, D02 R296, Ireland
    • Service description: Delivery of SMS notifications and management of voice calls for the communication functionalities of the Platform.
    • If Regional Twilio is used for the supported products, customer content is stored and processed in the selected region (Ireland). Twilio Ireland Limited acts as the contracting entity for EEA customers, with voice data processed in Ireland. Processing is covered by SCCs and by Twilio's Binding Corporate Rules (BCR) approved by European data protection authorities. DPA available at: https://www.twilio.com/en-us/legal/data-protection-addendum
  6. Sub-processing of electronic signature services:
    • Company name: Firma (1600 Holdings LLC) (trading as Firma.dev), a Missouri (USA) limited liability company
    • Contact details: [email protected]
    • Service description: Electronic signature of documents through the Platform, starting with commercial proposals and SEPA direct debit mandates and, where the CLIENT enables it, employment and HR documentation. It processes signers' data (name, email address, signature and the audit trail of the signing process) and the signed documents.
    • Documents and signer data are stored and processed in the EU (AWS Paris, with a content delivery network in Stockholm). Firma is a US company; transfers of personal data to Firma are covered by the Standard Contractual Clauses (Module Two) incorporated in Annex 3 of its DPA. Firma acts as a processor and undertakes not to use the data to train AI/ML models. Its sub-processors are Amazon Web Services (infrastructure, EU), Supabase (database, EU), Jitbit (support, EU) and Resend (transactional email carrying signers' names and email addresses, US); the latter transfer is covered by the Standard Contractual Clauses (Module Two) of Decision (EU) 2021/914. OPEREA can disable the emails sent by Firma to avoid that transfer. DPA available at: https://firma.dev/legal/data-processing-agreement
  7. Sub-processing of payment processing services:
    • Company name: Stripe Payments Europe, Limited
    • Tax ID/Reg.: IE3206488LH (VAT) — Reg. no.: 513174 (Companies Registration Office, Ireland)
    • Contact details and address: 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland · [email protected]
    • Service description: Processing of payments and collection of the CLIENT's subscription fees by means of SEPA direct debit and other payment methods.
    • Processing takes place within the EEA. DPA available at: https://stripe.com/legal/dpa
  8. Sub-processing of product analytics services:
    • Company name: PostHog, Inc.
    • Tax ID/Reg.: Delaware company, USA
    • Contact details and address: 2261 Market Street #4008, San Francisco, CA 94114, USA
    • Service description: Product analytics and behaviour tracking of the Platform's users for product improvement, including automatic capture of interface interactions and, where enabled, session recording. Because these operate on the Platform's own screens and on the worker application, the data processed may include personal data of the CLIENT's employees displayed or entered on screen (for example name, assigned site and shift). Values entered into form fields are masked and are not recorded. Also provides the in-app support chat, processing the content of messages sent through it and the identity of the sender. All of the above is subject to the user's prior consent for analytics cookies.
    • OPEREA uses PostHog Cloud EU, a managed instance with servers located in Frankfurt (Germany), so the data remains in the EEA. PostHog is certified under the EU-US DPF. DPA available at: https://posthog.com/dpa
  9. Sub-processing of application monitoring services:
    • Company name: Functional Software, Inc. (trading as Sentry)
    • Tax ID/Reg.: Delaware, USA (no. 5214647) — EU Representative: Sentry Software Netherlands B.V., Schiphol Boulevard 359, 1118 BJ, Amsterdam Schiphol, Netherlands · [email protected]
    • Contact details and address: 45 Fremont Street, 8th Floor, San Francisco, CA 94105, USA
    • Service description: Application performance monitoring (APM) and management of technical errors of the OPEREA Platform. It may process technical session data of administrator users (stack traces, session IDs, IPs).
    • OPEREA uses Sentry's EU region (Germany), so the data is hosted in the EU. Sentry is certified under the EU-US DPF. DPA available at: https://sentry.io/legal/dpa/

To sub-contract with other companies or replace any of the sub-processors listed, the PROCESSOR must notify the CONTROLLER in writing at least fifteen (15) days in advance, clearly and unequivocally identifying the sub-contractor company and its identification and contact details. The CONTROLLER may object in writing within said fifteen (15) day period. If the objection is not resolved, the CONTROLLER may terminate the affected services without penalty. Continued use of the services after said period has elapsed without objection from the CONTROLLER shall constitute acceptance of the new sub-processor.

The sub-contractor, who also has the status of processor, is equally obliged to comply with the obligations established in this document for the PROCESSOR and the instructions issued by the CONTROLLER. It is the responsibility of the PROCESSOR to govern the new relationship, so that the new processor is subject to the same conditions (instructions, obligations and security measures) and the same formal requirements as itself, with regard to the proper processing of personal data and the safeguarding of the rights of the data subjects affected.

In the event of non-compliance by the sub-processor, the PROCESSOR shall remain fully liable to the CONTROLLER with regard to compliance with the obligations.

4.6. Maintain the duty of secrecy with respect to the personal data to which it has had access by virtue of this assignment, even after its subject matter has ended, indefinitely.

4.7. Ensure that the persons authorised to process personal data undertake, expressly and in writing, to respect confidentiality and to comply with the corresponding security measures, of which they must be duly informed.

4.8. Keep at the disposal of the CONTROLLER the documentation evidencing compliance with the obligation established in the preceding paragraph.

4.9. Ensure the necessary training in personal data protection for the persons authorised to process personal data.

4.10. Assist the CONTROLLER in responding to the exercise of the rights of:

  1. Access, rectification, erasure and objection.
  2. Restriction of processing.
  3. Data portability.
  4. Not to be subject to automated individual decision-making (including profiling).

The PROCESSOR must notify the CONTROLLER, within 2 business days, of requests to exercise the rights of access, rectification, erasure and objection, restriction of processing, data portability and not to be subject to automated individual decision-making, in relation to the data subject to the assignment.

4.11. Right to information: It is the responsibility of the CONTROLLER to provide for the right to information at the time the data are collected.

4.12. Notification of personal data breaches

The PROCESSOR shall notify the CONTROLLER, without undue delay, and in any event before the maximum period of 36 hours, by email or any other means evidencing receipt of the communication, of the personal data breaches in its charge of which it becomes aware, together with all relevant information for the documentation and communication of the incident.

It is the responsibility of the CONTROLLER, in any event, to notify personal data breaches to the Data Protection Authority. The notification shall contain, as a minimum, the following information:

  1. A description of the nature of the personal data breach, including, where possible, the categories and approximate number of data subjects affected, and the categories and approximate number of personal data records affected.
  2. The name and contact details of the data protection officer or other contact point where more information can be obtained.
  3. A description of the likely consequences of the personal data breach.
  4. A description of the measures taken or proposed to remedy the personal data breach, including, where appropriate, measures taken to mitigate its possible adverse effects.

Likewise, it is the responsibility of the CONTROLLER to communicate, where necessary, as soon as possible, the personal data breaches to the data subjects, where the breach is likely to result in a high risk to the rights and freedoms of natural persons. The communication must be made in clear and plain language and must, as a minimum:

  1. Explain the nature of the data breach.
  2. State the name and contact details of the data protection officer or other contact point where more information can be obtained.
  3. Describe the likely consequences of the personal data breach.
  4. Describe the measures taken or proposed by the controller to remedy the personal data breach, including, where appropriate, measures taken to mitigate its possible adverse effects.

4.13. Support the CONTROLLER in carrying out Data Protection Impact Assessments, where applicable.

4.14. Support the CONTROLLER in carrying out prior consultations with the supervisory authority, where applicable.

4.15. Make available to the CONTROLLER all information necessary to demonstrate compliance with its obligations, as well as for the conduct of audits or inspections carried out by the CONTROLLER or another auditor authorised by it.

For these purposes and by way of illustration only and without limitation, at the request of the CONTROLLER, the PROCESSOR shall provide the relevant information or documentation.

The CONTROLLER, upon four (4) business days' prior notice, where possible, may attend the premises of the PROCESSOR in order to carry out the on-site controls and audits it deems appropriate to verify compliance with data protection regulations. The maximum number of audits to be carried out shall be 1 per calendar year, unless the CONTROLLER demonstrates a legitimate interest justifying a greater frequency.

With regard to sub-processors, no on-site audits shall be carried out at their premises. Instead, at the CONTROLLER's request, the PROCESSOR shall provide the audit reports and certifications of such sub-processors (for example, SOC 2 or ISO 27001) and the documentation they make available to their customers.

4.16. Implement the following security measures:

  • Robust user authentication by means of passwords or biometric systems.
  • Logical access control to resources and personal data, so that only employees duly authorised by the processor can access the data.
  • Encryption of the most sensitive data, both on IT media and during transmission.
  • Logging of incidents and security events.
  • Performance of daily backups, with point-in-time recovery.

In any event, in accordance with the provisions of Art. 32 of the GDPR, it shall implement mechanisms to:

  1. Ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services.
  2. Restore the availability of and access to personal data in a timely manner in the event of a physical or technical incident.
  3. Regularly test, assess and evaluate the effectiveness of the technical and organisational measures implemented to ensure the security of the processing.
  4. Pseudonymise and encrypt personal data, where applicable.

Likewise, the PROCESSOR shall adopt all those technical and organisational measures that, in light of the risk analysis carried out by the CONTROLLER, the latter considers necessary to ensure an adequate level of security, taking into account the state of the art and the cost of implementation in relation to the risks and the nature of the personal data to be protected. In this case, it shall be the obligation of the CONTROLLER to communicate the additional measures to be implemented by the PROCESSOR.

Without prejudice to the foregoing, the PROCESSOR may carry out its own risk analysis and propose to the CONTROLLER the adoption of security measures additional to or substituting those proposed by the latter, provided that they result in an adequate level of security.

The PROCESSOR shall make available to the CONTROLLER the documentation evidencing the provisions of the preceding paragraph.

4.17. Data retention

The PROCESSOR shall retain the user's data for the duration of the contractual relationship. The data shall be stored following best security practices and shall be available to the CONTROLLER at no additional cost.

Upon expiry of this Service Agreement, the CONTROLLER shall have 15 days to recover the user data it needs to retain.

After this period, the PROCESSOR shall proceed to the total deletion of the CONTROLLER's user data, and may also store the data in blocked form for a period exceeding the term of this Service Agreement where there is a legitimate interest of legal compliance.

5. OBLIGATIONS OF THE CONTROLLER

It is the responsibility of the CONTROLLER:

5.1. To allow the PROCESSOR access to the data subject to processing in accordance with the provisions of this Agreement.

5.2. To carry out the analysis of the risks that may arise from the processing activity that is to be the subject of the assignment and, on the basis of such analysis, to indicate to the PROCESSOR the technical and organisational measures that it must implement for the provision of the service entailed by the processing assignment.

5.3. To carry out a Data Protection Impact Assessment of the processing operations to be carried out by the PROCESSOR, where necessary.

5.4. To carry out the relevant prior consultations.

5.5. To ensure, in advance and throughout the processing, compliance with the GDPR by the PROCESSOR.

5.6. To supervise the processing, including the conduct of inspections and audits.

5.7. To notify the security measures it deems necessary at any given time.

6. CONTROLLER'S DECLARATION

The CONTROLLER guarantees the truthfulness and accuracy of the information provided to the PROCESSOR in all respects and, specifically, declares that it has complied, prior to the acceptance of this Agreement, with its obligations as CONTROLLER. Specifically, it declares that it has provided the information required under Art. 13 of the GDPR to the data subject, as well as having obtained the informed consent of the data subject where applicable and, by legal obligation, pursuant to Art. 6.1.c for clock-in —Art. 34.9 of the Workers' Statute—, 6.1.b for payroll/contract management, 6.1.f + Art. 90 LOPD-GDD for geolocation, and 9.2.b for health data (sick leave / temporary disability), so as to be able to carry out the processing of the data in accordance with the Service Agreement. The CONTROLLER shall inform the PROCESSOR of any development, modification or alteration that occurs in respect of the information provided. The PROCESSOR may carry out periodic audits to verify compliance with the foregoing, and the CONTROLLER undertakes to provide the information evidencing such compliance.

7. LIABILITY

The Parties undertake to hold each other harmless and to assume all liability in relation to any claim, penalty or loss, damage to third parties or liability incurred arising, directly or indirectly, from the breach of the obligations recognised for each Party in this Agreement or arising from the regulatory provisions.

8. ENTRY INTO FORCE AND TERMINATION OF THE AGREEMENT

This Agreement enters into force on the date of its acceptance.

This Agreement may be terminated for the following causes:

  1. By mutual agreement of the Parties, expressed in writing.
  2. By supervening impossibility to carry out the activities provided for in this Agreement.
  3. By the breach of the commitments assumed in the Agreement by either Party.
  4. By the termination or completion of the term stipulated in the Service Agreement from which it derives.

9. AMENDMENT OF THE PROCESSING AGREEMENT

This Agreement may only be amended expressly by mutual agreement between the Parties, by signing the corresponding addendum.

10. COMMUNICATIONS AND NOTIFICATIONS

  1. Communications addressed to the CONTROLLER shall be sent to the contact email address designated by the CLIENT in the Particular Conditions or in its OPEREA Platform account.
  2. Communications addressed to the PROCESSOR shall be sent to: [email protected]
  3. Communications in cases of security breaches shall be addressed, with a copy to the relevant functional manager, to the following email address: [email protected]

11. JURISDICTION AND APPLICABLE LAW

In accordance with the provisions of the Service Agreement from which it derives, any dispute between the Parties arising from the interpretation, performance and termination of this Agreement shall be subject to the jurisdiction of the Courts and Tribunals of Barcelona and shall be governed by Spanish law.

By accepting the Terms of Use and License during the contracting process, the CLIENT (in its capacity as CONTROLLER) and WORKSY TECH, S.L. (in its capacity as PROCESSOR) express their agreement to this Agreement, which takes full effect from the moment of such acceptance.

APPENDIX I: DATA SUBJECT TO PROCESSING

SERVICE DESCRIPTION

The contracted functionalities are determined in the Particular Conditions. The following tables describe areas of data processing, rather than commercial packages or a catalogue of contracted functionalities. Only the processing operations, purposes, data and categories of data subjects necessary to provide the contracted functionalities shall apply, in accordance with the CLIENT's instructions. References to these areas identify the corresponding processing activities in the following tables and notes.

Processing areaDescription
Personnel and contractsRecording and management of the complete employee record, clients, work sites and employment and service contracts. Centralisation of employment documentation.
SchedulingPlanning and management of shifts and work rosters, allocation by site and service contract, production control and coverage for absences.
AttendanceWorking-time recording and attendance control by means of GPS, geofencing and mobile app, in accordance with Art. 34.9 of the Workers' Statute. Import of external clock-ins.
Absences and documentsManagement of absences (holidays, temporary disability, leave), electronic signature of employment documentation and employee portal for consulting payslips and documents.
CommunicationInternal communication between office and field: direct and institutional messaging, push notifications, notice board and broadcasting by groups and sites.
ReportingOperational reporting and analytics: KPIs for attendance, absenteeism, staff cost and productivity. Configurable dashboard and export to Excel/PDF.
RemunerationCalculation of variable remuneration (hours, overtime, supplements and collective-agreement bonuses), management of payroll incidents and export/integration with third-party payroll software (Sage, A3Nom, etc.).

PROCESSING OPERATIONS

Processing operationPersonnel and contractsSchedulingAttendanceAbsences and documentsCommunicationReportingRemuneration
Collection☒☒☒☒☒☐☒
Recording☒☒☒☒☒☐☒
Structuring☒☒☒☒☐☒☒
Modification☒☒☐☒☐☐☒
Storage☒☒☒☒☒☒☒
Retrieval☒☒☒☒☐☒☒
Consultation☒☒☒☒☒☒☒
Disclosure by transmission☐☐☐☒☒☐☒
Dissemination☐☐☐☐☒☐☐
Interconnection☐☒☒☒☐☒☒
Matching☐☒☒☒☐☒☒
Restriction☒☐☐☒☐☐☐
Erasure☒☒☒☒☒☒☒
Destruction☒☒☒☒☒☒☒
Others☐☐☒¹☒²☐☒³☒⁴

¹ Attendance: Employee location recorded at clock-in and clock-out and, where the CLIENT enables it, geofence (site perimeter) checks solely during the scheduled duration of the shift, to know whether the employee is at the site. On route workdays (specialist services with several visits in one day), location is recorded continuously from clock-in to clock-out, to mark arrival at and departure from each visit and to give the receiving client the estimated arrival time and, where applicable, the team's approximate position on its way to the site. Location is never processed outside the shift or the route workday. Legal basis: Art. 34.9 of the Workers' Statute, Art. 90 LOPD-GDD and Art. 6.1.f GDPR; the CLIENT must inform employees beforehand. ² Absences and documents: Electronic signature of documents with legal validity (eIDAS). Employee access to their personal file. ³ Reporting: Generation of aggregated and anonymised reports for Platform improvement, in accordance with Art. 6.1.f GDPR. ⁴ Remuneration: Transfer of remuneration data to sub-processors (third-party payroll software: Sage, A3Nom, etc.).

PURPOSE OF PROCESSING

PurposePersonnel and contractsSchedulingAttendanceAbsences and documentsCommunicationReportingRemuneration
Client, accounting, tax and administrative management☒☐☐☐☐☒☒
Payroll management☐☐☒☒☐☐☒
Human resources☒☒☒☒☒☒☒
Occupational risk prevention☐☐☒☒☐☐☐
Building security and access control☐☐☒☐☐☐☐
Employment details / labour management☒☒☒☒☐☒☒
Economic and financial services☐☐☐☐☐☒☒
Statistical and historical purposes☐☐☐☐☐☒☐
Internal electronic communications☐☐☐☐☒☐☐
Health management and control (sick leave/disability)☐☐☐☒☐☐☐
Compliance with legal obligations (Workers' Statute, Social Security, income tax)☒☐☒☒☐☐☒

DATA TYPES

Data typePersonnel and contractsSchedulingAttendanceAbsences and documentsCommunicationReportingRemuneration
Identification data (name, DNI/NIE, date of birth, photograph)☒☒☒☒☒☐☒
Personal characteristics (marital status, nationality)☒☐☐☒☐☐☒
Academic and professional data (category, qualification, seniority)☒☒☐☒☐☐☒
Employment details (position, site, working time, contract)☒☒☒☒☒☒☒
Economic and financial data (salary, IBAN, income tax, Social Security)☐☐☐☐☐☒☒
Social circumstances☐☐☐☒☐☐☐
Transactions (payroll transfers)☐☐☐☐☐☐☒
Communications content☐☒☐☐☒☐☐
Start and end date of sick leave☐☐☐☒☐☐☐
Location data at clock-in, geofence and on route workdays☐☐☒☐☐☐☐

CATEGORIES OF DATA SUBJECTS

CategoryPersonnel and contractsSchedulingAttendanceAbsences and documentsCommunicationReportingRemuneration
CLIENT employees☒☒☒☒☒☒☒
CLIENT's clients (companies contracting the cleaning service)☒☒☐☐☐☒☐
Contact persons (site managers, supervisors)☒☒☒☐☒☒☐
Legal representative / proxy☒☐☐☒☐☐☒
Suppliers (sub-processors: Sage, A3Nom, etc.)☐☐☐☐☐☐☒

General note on the legal bases applicable to all processing areas:

Legal basisGDPR ArticleProcessing areas
Performance of the employment contractArt. 6.1.bAll processing areas
Legal obligation (Workers' Statute, Social Security, income tax, LISOS)Art. 6.1.cPersonnel and contracts, Attendance, Absences and documents, Remuneration
Legitimate interest of the employerArt. 6.1.fScheduling, Communication, Reporting
Legal obligation in labour and Social Security matters (health data)Art. 6.1.c + 9.2.bAbsences and documents (sick leave/disability)