Data Processing Agreement (DPA)

Last updated: November 2026 — Version 2.1

This translation is provided for information only; in the event of any discrepancy, the Spanish version shall prevail.

This Data Processing Agreement (hereinafter, the "DPA") is incorporated by reference into the Agendio Service Terms and Conditions (hereinafter, "the Terms") and forms an integral part thereof. In the event of conflict between this DPA and the Terms with regard to the protection of personal data, this DPA shall prevail.

This DPA is deemed entered into between:

  • CEDESA DIGITAL SL, owner of the Agendio brand, with tax ID (NIF) B06684369 and registered office at Campus Universitario, Avda. de la Investigación S/N, Edificio PCTEX Oficina 2.1, 06006 Badajoz (Spain), hereinafter "Agendio" or "the Processor".
  • The Customer identified in the Agendio Account, hereinafter "the Controller".

(Together, "the Parties".)

1. Definitions

Capitalised terms not defined herein shall have the meaning given to them in the Terms. In addition:

  • GDPR: 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.
  • Data Protection Legislation: the GDPR, Ley Orgánica 3/2018 (LOPDGDD; Spanish Data Protection and Digital Rights Act) and any other applicable data protection legislation.
  • Personal Data: the personal data (within the meaning of Article 4(1) GDPR) that the Controller, its employees or its Data Subjects enter or generate when using the Service and that are processed by the Processor on behalf of the Controller.
  • Data Subject: the natural person to whom the Personal Data relate (typically, the Controller’s end customer who makes a booking).
  • Sub-processor: a third party engaged by the Processor to process Personal Data on behalf of the Controller.
  • SCCs: Standard Contractual Clauses approved by the European Commission by means of Commission Implementing Decision (EU) 2021/914.
  • Security Breach: a breach of security leading to the unauthorised destruction, loss, alteration, disclosure of, or access to, the Personal Data (Article 4(12) GDPR).

2. Roles and subject matter

The Controller determines the purposes and means of the processing of the Personal Data and acts as controller within the meaning of Article 4(7) GDPR. The Processor processes the Personal Data solely on behalf of the Controller and acts as processor within the meaning of Article 4(8) GDPR.

The subject matter, duration, nature, purpose, categories of data and categories of Data Subjects are described in Annex I.

3. Controller’s instructions

3.1. The Processor shall process the Personal Data only on the documented instructions of the Controller, unless required to do so by law (in which case it shall inform the Controller, unless the law prohibits it).

3.2. The Controller’s documented instructions are: (i) those set out in the Terms and in this DPA; (ii) the settings that the Controller establishes through the administration panel (retention policies, automations, templates, opt-ins, etc.); (iii) any additional written instruction communicated to the Processor through the official support channels.

3.3. The Processor shall inform the Controller if, in its opinion, an instruction infringes the Data Protection Legislation.

4. Obligations of the Processor

The Processor undertakes to:

  • a) Process the Personal Data only in accordance with the Controller’s instructions (clause 3).
  • b) Ensure that persons authorised to process Personal Data have committed themselves to confidentiality or are under a statutory obligation of confidentiality.
  • c) Implement the appropriate technical and organisational measures described in Annex III to ensure a level of security appropriate to the risk (Article 32 GDPR).
  • d) Respect the conditions for engaging Sub-processors set out in clause 5 and Annex II.
  • e) Assist the Controller, by appropriate technical and organisational measures, insofar as this is possible, in responding to requests from Data Subjects to exercise their rights (clause 6).
  • f) Assist the Controller in ensuring compliance with the obligations under Articles 32 to 36 GDPR (security, breaches, impact assessments and prior consultations), taking into account the nature of the processing and the information available to it.
  • g) At the choice of the Controller, delete or return all the Personal Data after the end of the provision of the Service, and delete existing copies, unless retention is required by law.
  • h) Make available to the Controller the information necessary to demonstrate compliance with the obligations laid down in this DPA and allow for and contribute to audits in accordance with clause 8.

5. Sub-processors

5.1. General authorisation. The Controller authorises the Processor to engage the Sub-processors listed in Annex II and to engage new Sub-processors to provide the Service, in accordance with Article 28(2) GDPR (general written authorisation).

5.2. Notification of changes. The Processor shall notify all its Customers, at least 30 days in advance, of the addition or replacement of Sub-processors that process Personal Data: by email to the Account owner and in the Platform’s public list of Sub-processors, stating the effective date. The new Sub-processor does not process Personal Data before that date. Annex II is updated accordingly.

5.3. Right to object. The Controller may object, on reasoned grounds, to a new Sub-processor within 30 days of the notification. In such case, the Parties shall negotiate a solution in good faith. If no solution is reached, the Controller may terminate the part of the Service that depends on that Sub-processor, with the right to a pro rata refund of the unused subscription.

5.4. Obligations imposed on Sub-processors. The Processor shall enter into a written contract with each Sub-processor imposing data protection obligations no less protective than those of this DPA, in accordance with Article 28(4) GDPR. The Processor shall remain liable to the Controller for any failure by a Sub-processor to fulfil its obligations.

6. Assistance to the Controller: Data Subjects’ rights

6.1. The Processor makes functionalities available to the Controller on the Platform to respond to Data Subjects’ requests for access, rectification, erasure, restriction, portability and objection, including the download of a Data Subject’s data in a structured, commonly used format (JSON).

6.2. If a Data Subject addresses a request directly to the Processor, the Processor shall forward it to the Controller without undue delay and shall refrain from responding to the Data Subject, unless instructed otherwise by the Controller.

6.3. The Processor shall provide reasonable assistance to the Controller in handling such requests. Additional assistance exceeding what can reasonably be automated may be invoiced to the Controller at standard support rates.

7. Security Breaches

7.1. The Processor shall notify the Controller of any Security Breach affecting the Controller’s Personal Data without undue delay, and in any event within 48 hours of becoming aware of it.

7.2. The notification shall include, to the extent known at that time: (i) a description of the nature of the breach, the categories and approximate number of Data Subjects and records concerned; (ii) the contact details of the Processor’s DPO; (iii) the likely consequences; (iv) the measures taken or proposed to mitigate its effects.

7.3. Where the information cannot be provided at the same time, it shall be provided in phases without further undue delay.

7.4. Notification of a Breach by the Processor does not constitute an acknowledgement of fault or liability in respect of the incident.

8. Audits

8.1. The Processor shall provide the Controller, upon request, with the most recent audit reports (for example, ISO 27001, SOC 2 or equivalents it is able to obtain), as well as up-to-date descriptions of the technical and organisational measures (Annex III).

8.2. If the above information is not sufficient to demonstrate compliance, the Controller may request an additional audit, which shall be carried out:

  • With at least 30 days’ prior notice.
  • No more than once a year, save for justified cause (for example, an instruction from a supervisory authority or following a Security Breach).
  • During the Processor’s business hours and in a manner that does not disrupt its operations.
  • By an independent auditor bound by a duty of confidentiality and agreed upon by both Parties (who may not be a competitor of the Processor).
  • At the Controller’s expense, unless a material breach of the DPA is found, in which case the cost shall be borne by the Processor.

9. International transfers

9.1. The Processor may transfer Personal Data outside the European Economic Area only to Sub-processors that provide appropriate safeguards in accordance with Chapter V GDPR: an adequacy decision, Standard Contractual Clauses (SCCs), the EU-U.S. Data Privacy Framework or another valid mechanism.

9.2. The SCCs are deemed incorporated into this DPA by reference with respect to the relevant transfers, with the following parameters:

  • Applicable module: Module 3 (processor to processor) where the Processor transfers data to a Sub-processor outside the EEA that does not incorporate the SCCs into its own terms of service (otherwise, clause 9.4 applies).
  • Clause 7 (docking clause): applicable.
  • Clause 9 (use of sub-processors): Option 2, general authorisation with 30 days’ prior notice.
  • Clause 11 (redress): without the independent dispute resolution body option.
  • Clause 17 (governing law): Spanish law.
  • Clause 18 (choice of forum and jurisdiction): Spanish courts.

9.3. Annex II identifies the Sub-processors located outside the EEA and the safeguard applicable to each of them.

9.4. Where a Sub-processor incorporates the SCCs into its own terms of service, the transfer to that Sub-processor is covered by the clauses so incorporated. This is the case of YCloud Pte. Ltd. (Singapore): its transfers are covered by the European Commission’s standard contractual clauses incorporated into YCloud’s terms of service.

10. Return and deletion of data

10.1. Upon termination of the provision of the Service (on termination of the Terms or at the express request of the Controller), the Processor shall make available to the Controller, for a period of 30 days, an export tool to download the Personal Data in a structured, commonly used format.

10.2. Once that period has elapsed, the Processor shall delete the Personal Data from its production systems within a maximum of 30 additional days: the Controller’s database, its files (contracts, signatures, WhatsApp attachments) and the assistant’s memory. Data disappears from backup systems in the normal rotation cycle (daily backups for 30 days and monthly backups for 12 months); if a backup is restored, subsequent deletions are applied again. Deleted files are permanently erased from storage after 91 days.

10.3. The Processor may retain Personal Data beyond the above periods only where required by applicable law (for example, tax or commercial legislation), for as long as strictly necessary and with appropriate security measures.

10.4. Deletion of a Data Subject. When the Controller deletes a Data Subject from the Platform, the Processor anonymises their record and their bookings, deletes the content of their conversations and their attachments and the assistant’s memory of those conversations, and keeps blocked, without their contact details, the signed contract and its signature record as evidence (Article 17(3)(e) GDPR) for 3 months from deletion; once that period has elapsed, it deletes them (the signature record and the PDF of the signed contract).

10.5. Periods during the Service. For as long as the Service lasts, data is retained in accordance with the Controller’s instructions, subject to the automatic periods set out in Annex I, section F.

11. Liability

11.1. Each Party’s liability arising from this DPA shall be subject to the limitations of liability set out in the Terms.

11.2. The foregoing does not limit each Party’s liability towards Data Subjects under Article 82 GDPR or towards supervisory authorities.

12. Term and termination

12.1. This DPA shall enter into force upon acceptance of the Terms and shall remain in force for the duration of the contractual relationship.

12.2. Obligations which by their nature should survive termination (in particular those relating to confidentiality, return/deletion and cooperation with authorities) shall remain enforceable.

13. Final provisions

13.1. Amendments. The Processor may amend this DPA to reflect regulatory changes or operational adjustments. Material changes shall be notified 30 days in advance.

13.2. Governing law and jurisdiction. This DPA is governed by Spanish law and, where applicable, by the GDPR. For any dispute, the Parties submit to the courts and tribunals of the Processor’s registered office.

13.3. Acceptance. This DPA applies to all Customers with an Account, whatever their plan. The Controller expressly accepts it by accepting the Terms when signing up for the Account and confirms it on the Platform (Compliance → DPA), where acceptance of each new version is requested again. Customers who require a physical signature may request a signable copy from soporte@agendio.es.

Annex I — Description of the processing

A. Subject matter and duration

  • Subject matter: provision of the Agendio Service described in the Terms (booking management, WhatsApp messaging with an automated assistant, contracts and signature, access control and calendar synchronisation).
  • Duration: for the duration of the contractual relationship between Agendio and the Customer, plus the retention periods set out in clause 10.

B. Nature and purpose of the processing

Collection, storage, organisation, consultation, disclosure by transmission, modification, erasure and blocking of Personal Data, for the purpose of providing the Service to the Controller: managing Data Subjects’ bookings, sending and receiving messages through the WhatsApp Business Cloud API, replying automatically with an assistant based on an artificial intelligence language model when the Controller activates it, generating and signing contracts, generating access codes for smart locks, synchronising events with external calendars (Google Calendar, iCloud) if the Controller configures it, sending push notifications to the Agendio mobile app of the Controller’s authorised users through Apple’s and Google’s notification services, and providing operational analytics and reports to the Controller.

C. Categories of Personal Data

  • Data Subject identification data: name, telephone number, email (if provided) and national ID number or tax ID (DNI/NIF) where the Controller requires it for the booking or contract.
  • Booking data: date, time, amounts, payment method, notes and preferences.
  • Content of communications: messages and attachments exchanged via WhatsApp with the Controller and its assistant (including images of the identity document that the Data Subject sends for the booking), date, time and status.
  • Contracts and signature: booking contract, digitised handwritten signature, signatory’s IP address and browser, date and time of signature.
  • Access control: temporary access codes and a log of lock operations.
  • Technical metadata: WhatsApp identifiers, internal Platform identifiers and the phone identifiers of the Controller’s users for push notifications.
  • Push notifications: the Data Subject’s name and the first words of their message or their booking details in the notification received by the Controller’s user in the app, unless “Hide text” is enabled.

The Controller undertakes not to enter into the Platform special categories of data (Article 9 GDPR) or data relating to criminal convictions (Article 10 GDPR), unless expressly configured in advance with the Processor.

D. Categories of Data Subjects

  • End customers of the Controller who make bookings or communicate with the business.
  • Employees or collaborators of the Controller authorised to use the Platform.

E. BYO-WABA model and the Controller’s third-party connections

The Controller connects to the Platform its own accounts with third-party services, of which it is the sole owner and administrator vis-à-vis the respective providers. In particular:

  • WhatsApp Business Account (WABA): the Controller is the owner of its WABA vis-à-vis Meta. It accepts the WhatsApp Business Data Processing Terms directly with Meta when creating the WABA. The Controller decides the configuration of its WABA, including the storage region (Local Storage) for messages at rest, template approval, Data Subjects’ opt-in and its business’s messaging policy.
  • Google account (Google Calendar): the Controller is the owner of its Google account and grants Agendio access via OAuth 2.0 with the strictly necessary scopes (calendar.events, to create, change and delete the booking events, and calendar.calendarlist.readonly, read-only, to choose the calendar).
  • iCloud Calendar: the Controller connects its calendar via CalDAV with an app-specific password, which is stored encrypted.

The Processor acts exclusively as an orchestration and integration layer between these accounts of the Controller and the Platform. The Processor is neither the owner nor the administrator of the Controller’s accounts and does not make decisions about their configuration. Decisions on storage region, retention and the policies of each third-party service rest with the Controller as owner of the accounts.

F. Retention on the Platform

  • WhatsApp conversations and their attachments: depending on the plan subscribed, from the last message of each conversation: 30 days during the trial period, 90 days on the Basic and Basic with smart locks plans, 365 days on the Basic with assistant plan and, on Enterprise, for the duration of the contract.
  • Assistant memory: deleted after 90 days of inactivity in the conversation.
  • Assistant technical logs: 30 days, with a monthly archive that is deleted after 365 days.
  • Lock operation log and audit: 12 months.
  • Bookings, customer records and contracts: until the Controller deletes them, and at most until the end of the Service (clause 10).
  • Signed contract and signature record of a deleted Data Subject: blocked, without their contact details, for 3 months from deletion; deleted thereafter (clause 10.4).

Annex II — Authorised Sub-processors

The authorised Sub-processors are those on the list of Sub-processors that the Processor publishes on the Platform ("Sub-processors" page), with the service they provide, the data they process, their country, their processing agreement and the date from which they process Personal Data. The PDF version of this DPA reproduces that list at the end. Announced additions are shown with their effective date (clause 5.2).

Transfers outside the European Economic Area are covered by the Standard Contractual Clauses and, where the Sub-processor has self-certified, by the EU-U.S. Data Privacy Framework. In the case of YCloud Pte. Ltd., by the European Commission’s standard contractual clauses incorporated into YCloud’s terms of service (clause 9.4).

Annex III — Technical and organisational measures (Article 32 GDPR)

The Processor implements, as a minimum, the following measures:

A. Encryption and communications

  • Encryption in transit using TLS 1.2 or higher for all external communications and internal communications between services.
  • Encryption at rest of databases and storage volumes (AES-256 or equivalent).
  • Specific encryption of stored credentials and OAuth tokens (Google Calendar and others).

B. Access control

  • Least-privilege, role-based access control policy (RBAC).
  • Mandatory multi-factor authentication (MFA) for staff with access to production environments.
  • Periodic review of privileges (at least quarterly).
  • Bastion host and infrastructure access logs.

C. Pseudonymisation and minimisation

  • Anonymisation or pseudonymisation of data in non-production environments.
  • Minimisation policy: only data strictly necessary for the provision of the Service is collected.

D. Continuity and resilience

  • Encrypted daily backups, with periodic restoration tests.
  • Business continuity and disaster recovery plan (documented RTO/RPO).
  • Redundancy of critical infrastructure.

E. Operational security

  • Vulnerability management: periodic scans and patching according to severity.
  • Security testing (including penetration testing at least annually) of critical components.
  • Security monitoring and alerting (SIEM or equivalent).
  • Incident management policy and documented response plan.

F. Personnel

  • Confidentiality agreements signed by all staff with access to Personal Data.
  • Periodic training in data protection and information security.
  • Formal onboarding and offboarding procedures for employees, including revocation of access.

G. Physical security

  • Data hosted with certified cloud providers (ISO 27001 or equivalent) with physical access controls, 24/7 surveillance and power redundancy.

H. Sub-processor management

  • Selection of Sub-processors with security and privacy due diligence.
  • Contracts with data protection clauses equivalent to those of the DPA.
  • Periodic review of compliance.

Need a copy for signature or have questions about this DPA?

Write to us at soporte@agendio.es