Privacy Policy
Last updated: 18 November 2026
This translation is provided for information only; in the event of any discrepancy, the Spanish version shall prevail.
1. Introduction and Controller
At Agendio we are committed to protecting your privacy and ensuring the security of your personal data. This Privacy Policy explains how we collect, use, disclose and protect your information when you use our automated booking platform, in accordance with Regulation (EU) 2016/679 (GDPR) and Ley Orgánica 3/2018 (LOPDGDD; Spanish Data Protection and Digital Rights Act).
Controller: CEDESA DIGITAL SL (owner of the Agendio brand)
Tax ID (NIF): B06684369
Address: Campus Universitario, Avda. de la Investigación S/N, Edificio PCTEX Oficina 2.1 — 06006 — Badajoz (Spain)
Telephone: (+34) 924 090 608
Contact email: soporte@agendio.es
Data Protection Officer (DPO): soporte@agendio.es — C/ Francisco Guerra 12, Portal 4, 1ºC, 06011 Badajoz (Spain)
Contact form: agendio.es/en/contact
2. Roles in data processing
Agendio acts in two distinct roles depending on the type of data:
- As Controller: in respect of the data of visitors to our website (agendio.es), of Customers who subscribe to the Service (registration, billing and support data) and of people who get in touch with us.
- As Processor (Article 28 GDPR): in respect of the data of the end customers that the Customer (the business using Agendio) processes through the Platform — for example, people who make a booking with the Customer’s business. In this case, the Customer is the controller and Agendio acts on its documented instructions set out in the Data Processing Agreement incorporated into the Terms and Conditions.
3. Data we collect
3.1. As Controller
- Contact and registration information: name, telephone number, email, business details, tax ID (NIF).
- Billing information: payment details (processed through the payment provider), invoice history.
- Device information: device type, operating system, browser, IP address (anonymised where possible).
- Agendio mobile app: installation identifier, operating system and app version, date of last use and, if the person accepts notifications, the identifier that Apple or Google assigns to their phone to send them push notifications.
- OAuth credentials: access and refresh tokens that the Customer grants us when connecting third-party services (Google), stored encrypted.
- Sales enquiries (Enterprise plan "Let’s talk" form): company, name of the contact person, email, telephone (optional), usage estimates and requirements, and the date and IP address of acceptance of this policy. The public form is protected against automated submissions with hCaptcha, which analyses technical browser data.
3.2. As Processor (data of the business’s end customers)
- End customer contact information: name, telephone number, email and, where the business requires it for the booking or contract, national ID number or tax ID (DNI/NIF).
- Booking information: date, time, amounts, payment method, notes and preferences.
- WhatsApp communication history: messages and attachments exchanged with the business and with its automated assistant (including images of the identity document that the end customer sends for the booking), date, time and delivery 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 for smart locks and a log of lock operations, where the business connects them.
- Notifications in the business’s app: when a member of the Customer’s team uses the Agendio app, the push notification may include the end customer’s name and the first words of their message or their booking details; with “Hide text” only a generic text is sent.
4. Purpose and legal basis of processing
| Purpose | Legal basis |
|---|---|
| Providing the SaaS service to the Customer | Performance of the contract (Art. 6(1)(b) GDPR) |
| Managing and confirming bookings (on behalf of the Customer) | Mandate from the Customer / Performance of the contract between the Customer and its end customer |
| Replying via WhatsApp with the automated assistant (artificial intelligence language model) on behalf of the Customer | Mandate from the Customer / Performance of the contract between the Customer and its end customer |
| Sending reminders and notifications via WhatsApp | Performance of the contract + end customer opt-in |
| Synchronising bookings with Google Calendar or iCloud Calendar | Customer’s consent when connecting its account (Art. 6(1)(a) GDPR) |
| Usage analytics for the agendio.es Website (Google Analytics 4, Microsoft Clarity) | Consent (Art. 6(1)(a) GDPR) |
| Handling Enterprise plan sales enquiries | Pre-contractual measures at the request of the data subject (Art. 6(1)(b) GDPR) |
| Protecting public forms against automated submissions (hCaptcha) | Legitimate interest (Art. 6(1)(f) GDPR) |
| Handling enquiries and support | Legitimate interest (Art. 6(1)(f) GDPR) |
| Sending push notifications to the Agendio app of the Customer’s team members | Performance of the contract (Art. 6(1)(b) GDPR); they can be turned off by type or entirely on the phone |
| Complying with legal obligations | Legal obligation (Art. 6(1)(c) GDPR) |
5. Use of Google APIs
Agendio integrates the Google Calendar API to allow Customers to synchronise the bookings managed on the Platform with their Google calendar.
5.1. Data and scopes we access
When a Customer connects its Google account via OAuth 2.0, Agendio requests the following minimum necessary scopes:
https://www.googleapis.com/auth/calendar.calendarlist.readonly— to show the Customer the list of its calendars so it can choose where events are created. It is read-only: it gives no access to the events in those calendars.https://www.googleapis.com/auth/calendar.events— to create, modify and delete events in the calendar selected by the Customer.
We do not request access to any other data in the Customer’s Google account (email, contacts, files in Drive, etc.).
5.2. How we use Google data
Data obtained from Google APIs is used exclusively to:
- Create events in the Customer’s calendar when a booking is confirmed.
- Update or delete events when a booking is modified or cancelled.
- Show the list of the Customer’s calendars so it can choose which one the bookings are synchronised with. We do not read the events the Customer has in its calendars.
5.3. Compliance with Google’s Limited Use Policy
Agendio’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
In particular, we expressly declare that:
- We do not sell Google data to third parties.
- We do not use Google data to serve advertising, or for retargeting or personalised or interest-based advertising.
- We do not transfer or use Google data to determine creditworthiness or for lending purposes.
- We do not use Google data to train generalised or non-personalised artificial intelligence or machine learning models.
- We do not allow humans to read the user’s Google data, except in the following cases permitted by the policy: (i) with the user’s express and specific consent, (ii) where necessary for security purposes (for example, investigating a bug or abuse), (iii) to comply with an applicable legal obligation, or (iv) with aggregated and anonymised data for internal operations in accordance with applicable law.
Sharing of Google user data. Agendio does not transfer Google user data to third parties, except: (a) our hosting provider, Amazon Web Services, which stores on our behalf, under a data processing agreement, the encrypted OAuth tokens, the calendar list and the IDs of the events Agendio creates; (b) when required by law; and (c) as part of a merger, acquisition or sale of assets, with prior notice to the user. Google user data is never sent to artificial intelligence or language-model providers: the WhatsApp assistant (OpenAI) does not receive any Google Calendar data. Agendio does not use Google user data, raw or aggregated, to develop, improve or train any AI or machine-learning model.
5.4. Storage and security of Google data
- OAuth tokens (access and refresh) are stored encrypted at rest on our servers, with access restricted to authorised personnel.
- Event identifiers (
event_id,calendar_id) are kept only for as long as necessary for the operational traceability of the associated booking. - We do not keep permanent copies or derived databases of the content of the user’s calendars beyond what is strictly necessary to provide the functionality.
5.5. Revoking access to Google
When the user disconnects the Google account in Agendio, we immediately delete the stored OAuth tokens, the calendar list and the links between bookings and calendar events, and we revoke the grant with Google. The user can also revoke access at any time from their Google account (myaccount.google.com/connections); Agendio then stops using the API and deletes the tokens within 7 days at most. Events already created in the user’s calendar stay there and belong to the user. Encrypted copies in backups are deleted when those backups expire (30 days for daily backups and 12 months for monthly backups) and are never used to restore access.
6. Communications through the WhatsApp Business Cloud API
Agendio integrates with the WhatsApp Business Cloud API (a service provided by Meta Platforms Ireland Limited) so that Customers can manage automated booking communications with their end customers through their own WhatsApp Business Account (WABA). The technical integration is carried out through YCloud, an official Business Solution Provider (BSP) authorised by Meta.
6.1. BYO-WABA model: the Customer owns its own WABA
Each Customer connects its own WhatsApp Business Account (WABA) to Agendio, of which it is the sole owner and administrator vis-à-vis Meta. Accordingly:
- The Customer is responsible for verifying its business in Meta Business Manager and for setting up and maintaining its WABA.
- The Customer decides the configuration of its WABA, including the storage region (Local Storage) for messages at rest on Meta’s servers, template approval, display name and its business’s messaging policy.
- The Customer is responsible for obtaining and maintaining the explicit opt-in of its end customers before sending them proactive messages.
- Agendio acts exclusively as an integration and automation layer between the Customer’s WABA and the Platform. Agendio is neither the owner nor the administrator of the Customer’s WABA and does not make decisions about its configuration or storage region.
6.2. Roles in processing
- The Customer is the controller in respect of the personal data of its end customers exchanged through its WABA.
- Agendio acts as the Customer’s processor, providing the orchestration platform that connects the Customer’s WABA with the Service logic.
- Meta Platforms Ireland Ltd. acts as the Customer’s processor under the WhatsApp Business Data Processing Terms accepted directly by the Customer when creating its WABA.
- YCloud acts as Agendio’s sub-processor under the corresponding DPA, providing the routing layer between the Customer’s WABA and the Platform.
6.3. Data processed through WhatsApp
Telephone number, name (if provided by the end customer), content of the messages exchanged, date and time of the message, and delivery/read status.
6.4. Prior consent (opt-in)
Before receiving any proactive message from the Customer or from Agendio via WhatsApp, end customers must have given an explicit opt-in, in accordance with Meta’s rules and the GDPR. The Customer is responsible for obtaining and keeping proof of such consent; Agendio provides tools to record and track the opt-in.
6.5. Unsubscribe mechanism (opt-out)
End customers may stop receiving messages at any time:
- Marketing messages: using the WhatsApp option to stop receiving marketing messages from that business. WhatsApp notifies us of the opt-out and the Platform stops sending them marketing messages.
- All messages: by blocking the Customer’s number in their WhatsApp application.
Service messages relating to a booking already made (confirmation, reminders, contract and access) continue to be sent unless the number is blocked, because they form part of the booking. The WhatsApp assistant does not process unsubscriptions or cancel bookings: to cancel a booking or object to processing, the end customer should contact the business, which is the controller.
6.6. International transfers relating to WhatsApp
- Meta Platforms Ireland Limited (Ireland) / Meta Platforms, Inc. (USA): the WhatsApp Business Cloud API processes data in the region configured by the Customer as owner of the WABA. Transfers to the USA are covered by the Standard Contractual Clauses and the EU-U.S. Data Privacy Framework, in accordance with the WhatsApp Business Data Transfer Addendum accepted directly by the Customer.
- YCloud (operated by YCloud Pte. Ltd., established in Singapore): transfers are covered by the European Commission’s standard contractual clauses incorporated into YCloud’s terms of service. Singapore does not benefit from an adequacy decision of the European Commission; the flow of data through YCloud is limited to the routing layer necessary for the technical integration.
For more information on how Meta processes data on the WhatsApp Business Platform, see the WhatsApp Business Data Processing Terms and the WhatsApp Privacy Policy.
7. Third parties and international transfers
We do not sell your personal data. We share information only with the following service providers acting as processors or sub-processors. The current list of the Platform’s sub-processors, with announced changes and their effective date, is published on the Platform’s "Sub-processors" page (app.agendio.es/legal/subprocesadores); changes are notified to all Customers 30 days in advance.
| Provider | Purpose | Location | Transfer safeguard |
|---|---|---|---|
| Amazon Web Services EMEA SARL | Platform hosting, backups and email delivery (Amazon SES) | EU (Frankfurt, Germany) | N/A (EEA) |
| MongoDB, Inc. (MongoDB Atlas) | Database for the assistant’s conversation memory | EU (Frankfurt, Germany) | SCCs + EU-U.S. DPF |
| OpenAI, L.L.C. | Language model for the WhatsApp assistant | USA | SCCs + EU-U.S. DPF |
| Stripe Payments Europe, Ltd. | Collection of the subscription and message bundle payments | Ireland | N/A (EEA) |
| YCloud Pte. Ltd. | WhatsApp Business API BSP (routing layer) | Singapore | European Commission SCCs incorporated into YCloud’s terms of service |
| Meta Platforms Ireland Ltd. / Meta Platforms, Inc. | WhatsApp Business Cloud API infrastructure (Customer-owned WABA) | Ireland / USA | SCCs + EU-U.S. DPF |
| Google LLC | Google Calendar API (when the Customer connects it via OAuth), Firebase Cloud Messaging (push notifications of the Agendio app on Android) and, on the Website, Google Tag Manager / Google Analytics 4 | USA | SCCs + EU-U.S. DPF |
| Microsoft Corporation | Microsoft Clarity (Website behavioural analytics) | USA | SCCs + EU-U.S. DPF |
| Cloudflare, Inc. | CDN, DNS and infrastructure | EU (where possible) | SCCs |
| Formspree | Contact form management | USA | SCCs |
| Apple Distribution International Ltd. | iCloud Calendar via CalDAV (when the Customer connects it) | Ireland | N/A (EEA) |
| Nuki Home Solutions GmbH | Smart lock access codes (when the business connects them) | Austria | N/A (EEA) |
| Apple Inc. | Push notifications of the Agendio app on iPhone (Apple Push Notification service) | USA | SCCs + EU-U.S. DPF |
| Intuition Machines, Inc. (hCaptcha) | Protection of public forms against automated submissions | USA | SCCs |
Business partners: the businesses where you make bookings, which act as independent controllers in respect of their own customers.
Legal obligations: we may share data with the competent authorities where required by law.
8. Retention period
| Data category | Period |
|---|---|
| Customer account data | For the duration of the contractual relationship + 5 years (LGT/LOPDGDD/commercial legislation) |
| Billing data | 6 years (Código de Comercio — Spanish Commercial Code, Art. 30) |
| Sales enquiries (Enterprise) | Those not converted into a contract, 12 months from closure; those still open with no activity, 24 months; those converted into a contract, for the duration of the contract. They are deleted earlier if you so request |
| Assisted WhatsApp onboarding requests | Cancelled or abandoned requests are deleted after 12 months; for completed requests, contact details and notes are deleted after 12 months |
| Data of the business’s end customers (bookings, contracts and access control) | In accordance with the instructions of the Customer, which is the controller; at the end of the service they are deleted in accordance with the Data Processing Agreement (clause 10). Lock operation logs are deleted after 12 months. If the Customer deletes an end customer, their signed contract and signature record are kept blocked, without their contact details, for 3 months as evidence (Art. 17(3)(e) GDPR) and then deleted |
| WhatsApp conversations on the Platform | Depending on the plan subscribed by the Customer, 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. Attachments are deleted together with their conversation |
| WhatsApp assistant memory | Deleted after 90 days of inactivity in the conversation, or earlier if the conversation is deleted |
| WhatsApp assistant technical logs | 30 days, with a monthly archive that is deleted after 365 days |
| Google OAuth tokens | Until revocation + 7 days for secure deletion |
| WhatsApp messages on Meta’s servers | In accordance with the configuration of the Customer’s WABA; a maximum of 30 days before automatic deletion if not delivered |
| Security and audit logs | 12 months |
| Backups | Daily for 30 days and monthly for 12 months; when a backup is restored, deletions made afterwards are applied again. Deleted files are permanently erased from storage after 91 days |
Once these periods have elapsed, the data is securely deleted or anonymised.
9. Data security
We implement appropriate technical and organisational security measures: SSL/TLS encryption in transit, encryption at rest of credentials and tokens, role-based access control, audit logs, backups and incident management procedures. In the event of a security breach that poses a risk to your rights and freedoms, we will notify the Spanish Data Protection Agency (AEPD) within 72 hours and you directly where appropriate.
10. Your rights (ARCO+)
You have the right to: access, rectification, erasure ("right to be forgotten"), restriction of processing, objection, portability, withdrawal of consent (without retroactive effect) and to lodge a complaint with the Spanish Data Protection Agency (AEPD) (aepd.es).
To exercise them, write to soporte@agendio.es stating the right you wish to exercise and enclosing a copy of your national ID card or other identity document.
If the data in respect of which you wish to exercise a right is processed by Agendio as a processor on behalf of a Customer (the business where you made your booking), we will refer you to the Customer as controller, unless otherwise required by law. The Platform gives the Customer the tools to deal with your request: download of your data in a structured format (access and portability), rectification, erasure, restriction and objection.
11. Cookies and similar technologies
On the Website (agendio.es) we use our own cookies (essential for its operation) and third-party analytics cookies (Google Analytics 4 and Microsoft Clarity, managed through Google Tag Manager with Consent Mode v2). Analytics cookies are only installed with your explicit consent, given through the cookie banner on equal terms (Accept / Reject) in accordance with the AEPD guidelines. The Platform (the Customers’ panel) only uses technical cookies: session, protection against request forgery, language and, if you use them, Stripe cookies on the payment screen and hCaptcha cookies on the "Let’s talk" form. You can withdraw your consent at any time using the "Manage cookies" button in the footer or from our Cookie Policy, where you will find the detailed table of cookies by provider, type and duration.
12. Protection of minors
Our services are designed for adults. We do not knowingly collect personal information from children under 14 without the verifiable consent of their parents or legal guardians (Art. 8 GDPR and Art. 7 LOPDGDD).
13. Changes to this policy
We may update this Privacy Policy from time to time. We will notify any material change by publishing the new version on this page and updating the "last updated" date. Where changes affect the way we process Google data, we will request new consent before applying the new processing, as required by the Google API Services User Data Policy.
14. Contact
If you have any questions about this Privacy Policy or wish to exercise your rights:
Email: soporte@agendio.es
DPO: soporte@agendio.es
Form: agendio.es/en/contact