Data processing agreement
Last updated: 11 November 2026
This is a translation. In the event of any discrepancy, the Spanish version prevails.
This agreement, in accordance with Article 28 of the GDPR, forms part of the Terms and conditions and applies to the personal data that OX·IA processes on behalf of the customer. The customer is the controller and Dalvia Tech, S.L. is the processor. Communications about this agreement should be sent to info@dalvia.tech.
- Owner: Dalvia Tech, S.L.
- NIF: B05902259
1. Subject matter, nature and purpose
Providing the conversational assistant service on the customer’s website: receiving its visitors’ questions, generating the answers, storing the conversations and, if the customer enables it, collecting the contact details that visitors choose to leave, managing the appointments they book from the chat and allowing people from the customer’s team to take over the conversation. If the customer enables it, the assistant also handles the messages it receives through the customer’s WhatsApp, Telegram or mailbox, and sends contacts and appointments to its CRM or its webhook.
Appointments are stored in the OX·IA calendar and, if the customer has connected it, in its Google, Microsoft, Calendly or Salesforce calendar, or in its WordPress booking plugin. Those systems, like its WhatsApp Business account (Meta), its Telegram bot, its email provider and its CRM, belong to the customer, are contracted by the customer under their own terms and fall outside this processing: they are not sub-processors of Dalvia Tech, S.L. Sending them the data is an instruction from the customer, given when it configures the connection in its dashboard.
So that the assistant remembers long conversations, a summary of what was said is generated automatically, without contact details. From the Core plan upwards, if a visitor left their details, the assistant recognises their browser when they return and uses their name and the summary of the previous conversation to continue helping them. Conversations are deleted automatically when the period of the customer’s plan ends (90 days on Demo, 90 days on Bit, 1 year on Core, 2 years on Quantum and 2 years on Agency, from the last message). Contact requests are kept for as long as the service lasts or until the customer asks for them to be deleted, as are appointments.
Agency plan. When the customer is an agency that uses the service for its own clients (client businesses), the agency acts as processor for each client business and OX·IA as the agency’s sub-processor, with the same obligations as in this agreement. The agency authorises the sub-processors in section 5 and is responsible for having a processing agreement with each client business that allows this and for passing on to it the relevant instructions and notices.
2. Duration
The duration of the service contract. When it ends, section 8 applies.
3. Data and data subjects
- Data subjects: visitors to the customer’s website who use the assistant and, if the customer connects its channels, those who write to it via WhatsApp, Telegram or email.
- Data: the content of the conversations (which may include data the visitor writes on their own initiative), the page from which they write, an anonymous browser identifier, an encrypted and irreversible fingerprint of their connection (to block abuse, never the IP address), whether they are on the website at that moment (with no history) and, if they leave their details or book an appointment, name, email, phone, message or notes, the service and the date of the appointment. On the channels: the phone number (WhatsApp, or Telegram if the person chooses to share it), the Telegram username, the email address and the content of the messages.
- Voice: if the customer has dictation or voice chat enabled (they are, unless switched off), the visitor’s voice while they dictate or speak. It is processed in real time, through Google Cloud (Gemini) and within the European Union, to convert it into text and reply. The processor does not store it or use it to identify anyone. The text is kept as part of the conversation.
- Special categories of data are not expected to be processed. The customer must not use the assistant to collect them.
4. Obligations of the processor
- Process the data only on the documented instructions of the customer, which are this agreement and the settings it configures in its dashboard.
- Ensure the confidentiality of the persons authorised to process it.
- Apply the security measures of Article 32 of the GDPR: encryption in transit, access control, separation of each customer’s data, backups and access logs.
- Assist the customer in responding to data subjects’ requests and in complying with its security and impact assessment obligations.
- Notify the customer of any personal data breach affecting its data without undue delay, with the information available.
- Make available to the customer the information necessary to demonstrate compliance and allow reasonable audits, with prior notice.
5. Sub-processors
The customer authorises the following sub-processors, with which there are contracts providing equivalent safeguards:
- Clouding.io (Clouding Networks S.L.): Server hosting, databases and backups. Spain (Barcelona, EU).
- Cloudflare, Inc.: Content delivery network, security and bot verification (Turnstile). Global; transfers covered by the EU-US Data Privacy Framework and standard contractual clauses.
- Google Cloud EMEA Limited (Vertex AI): Artificial intelligence models that generate the answers and the search indexes, and that understand and generate voice when the customer switches it on. The main model is Google’s Gemini. If it is not available, chat answers, summaries and tags may be generated as a fallback by Anthropic’s Claude, which runs within the same Google Cloud. Voice and search indexes always use Gemini. European Union (company in Ireland; the data is processed in the Google Cloud EU multi-region, only in EU Member States). Google does not use this data to train or fine-tune any model and does not share it with Anthropic.
- Firecrawl (Mendable, Inc.): Reading the public pages of the customer’s website. United States; standard contractual clauses.
We will notify the customer in advance of any change of sub-processors, so that it can object on justified grounds.
6. International transfers
Data that passes through artificial intelligence is processed within the European Union, in the Google Cloud EU multi-region. If Google’s automated systems detect possible abuse, Google may keep those requests for up to 90 days, in the same multi-region, to review whether its usage policy has been breached (there may be human review); it never uses them to train models. The other sub-processors that process data outside the European Economic Area, according to the location stated in section 5, do so with the safeguards of Chapter V of the GDPR (adequacy decision or standard contractual clauses).
7. Obligations of the customer
- Have a legal basis for the processing and inform its visitors, in its privacy policy, of the use of the assistant and of this processor.
- Enter in its dashboard the link to its privacy policy, which is shown next to the contact form.
- Respond to its visitors’ requests to exercise their rights, with our assistance when needed.
- Ensure that the people in its team who handle the chat treat visitors’ data confidentially and only to assist them.
- If it connects its channels, its CRM or a webhook: have a legal basis for that use, inform those who write to it through those channels and comply with the terms of each service.
8. End of the processing
When the service ends, the customer can download its contacts from the dashboard. We will then erase the data within a maximum of 30 days, unless a law requires it to be kept, in which case we will keep it blocked.