Privacy policy
Last updated: 11 November 2026
This is a translation. In the event of any discrepancy, the Spanish version prevails.
This policy explains how we process the personal data of those who use OX·IA and of those who visit this website, in accordance with Regulation (EU) 2016/679 (GDPR) and Spanish Organic Law 3/2018 (LOPDGDD).
1. Data controller
- Owner: Dalvia Tech, S.L.
- NIF: B05902259
- Registered address: Plaza del Gato, 3, Primero, 28817 Los Santos de la Humosa (Madrid)
- Website: dalvia.tech
- Email: info@dalvia.tech
- Phone: +34 691 737 863
For any data protection matter, write to us at info@dalvia.tech.
2. What data we process and why
| Purpose | Data | Legal basis | Retention |
|---|---|---|---|
| Creating and managing your account and your business’s account | Name, email, business, encrypted password, role in the team and, if you enable it, two-step verification (the key of your authentication app and recovery codes, encrypted). If you log in with Google or Microsoft, the name, email and profile photo they provide to us | Performance of the contract (Art. 6(1)(b) GDPR) | While the account is active and, afterwards, for the limitation period for legal claims |
| Providing the service: reading your website, generating the assistant’s answers, dashboard statistics | Content of your website, assistant settings, conversations | Performance of the contract | For as long as the service lasts. Conversations are deleted automatically according to the plan, counting from their last message: 90 days on Demo, 90 days on Bit, 1 year on Core, 2 years on Quantum and 2 years on Agency. Demos that are not activated are deleted 30 days after they expire |
| Replying in person to visitors in the chat on your website, if your business enables it (“Hand the conversation over to a person”) | Your name, your profile photo and your job title (the last two only if you add them), which the visitor sees when you reply to them; the messages you write; and whether you have the dashboard open at that moment, so your team knows who is available | Performance of the contract | The photo and job title, until you remove them or your account is closed. Your messages, with the conversation (periods in the previous row). The “online” status is not stored: it expires in less than a minute |
| Learning the content of your WordPress site, if you connect our plugin | Address, name, icon and colour of your website, the address of its API and the public content you choose (pages, posts, products); never content protected by a password or marked as “noindex”. For bookings, a secret key created by the plugin, which we store encrypted | Performance of the contract | While the website is connected. When you disconnect it or cancel your account, it is deleted together with the rest of your assistant |
| Bookings with your calendar, if you connect Google Calendar, Outlook, Calendly or Salesforce | The email of that account, the access permission (encrypted), the busy times in your calendar and the appointments entered in it | Performance of the contract | While the calendar is connected. When you disconnect it, we delete the permission |
| Connections, if you enable them: having the assistant handle your WhatsApp, your Telegram or your mailbox, and sending contacts and appointments to your CRM | The data needed to connect each service (identifiers, tokens, API keys, app passwords or the Microsoft permission), stored encrypted; the connected address or number and the status of the connection | Performance of the contract | While the connection exists. When you remove it, we delete its access data |
| Invoicing and payment | Tax details, address, payment history (the card is processed only by Stripe) | Performance of the contract and legal obligation (Art. 6(1)(c)) | The periods required by tax and commercial law |
| Sending you the link to your demo and the button to activate your account, and letting you know how it is going (if it runs out of messages, when it is about to end and when it has ended) | Email, the demo website, what you accepted, date, IP address and browser | Your request (Art. 6(1)(b) GDPR) for sending the demo and its notices. Proof that you accepted this policy: legal obligation (Art. 7(1)) | The notices end with the demo. The email and the proof of what you accepted, for the limitation period for legal claims; if you also agreed to receive news, until you withdraw that consent |
| Sending you news and offers from OX·IA | Name and email | Your consent (Art. 6(1)(a)), which you can withdraw at any time | Until you withdraw your consent |
| Security and abuse prevention | IP address, technical logs, anti-bot verification. In the chat, an encrypted and irreversible fingerprint of the connection (never the IP address), so that a business can block anyone who abuses its chat | Legitimate interest in protecting the service (Art. 6(1)(f)) | The minimum time necessary, generally days. Blocking a connection lasts 24 hours; blocking a browser, until the business removes the block |
| Keeping proof of your consents | What you accepted, version of the text, date, IP address and browser | Legal obligation to demonstrate consent (Art. 7(1)) | While the account exists and for the limitation period |
3. Data of visitors to our customers’ websites
When a visitor talks to the assistant installed on the website of one of our customers, or leaves their contact details with it, the controller of that data is the customer business. OX·IA processes it on the business’s behalf as a processor, under the Data processing agreement. To exercise their rights, the visitor must contact that business; if they write to us, we will forward their request to it.
If the business enables it, a person from its team can take over the conversation from the assistant, and the visitor sees their name, photo and job title. That person acts on behalf of the business.
If the business has not switched voice off (it is on by default), the visitor can dictate their questions or talk to the assistant. The microphone is only used when the visitor asks for it (and their browser asks them for permission). Their voice is sent at that moment to Google Cloud (Gemini), which processes it within the European Union, to convert it into text and to reply, including by voice; OX·IA does not store the audio or use it to identify anyone. What is kept is the text of what was said, like the rest of the conversation.
The same applies to anyone who writes to the business through the channels it connects: its WhatsApp, its Telegram or its mailbox. OX·IA receives those messages, the assistant replies to them (by email, either leaving a draft or replying directly, as the business chooses) and the conversation is stored in the same way as chat conversations. The phone number or Telegram username, the email address and the content of the messages are processed. If the person asks to talk to someone from the team, the reply reaches them through the same channel, with the name of the person handling it. If the business connects its CRM, the contacts and appointments collected by the assistant are sent to it, with a summary of what the person asked for and the link to the conversation.
Those services (Meta for WhatsApp, Telegram, the business’s email provider, its CRM, its calendar) are chosen and contracted by the business, under their own terms; they are not providers of OX·IA. What happens to the data within them is governed by the relationship between the business and that service.
4. Google and Microsoft data (sign-in, calendars and email)
If you log in with Google, OX·IA receives your name, your email and your profile photo from your account (Google’s openid, email and profile permissions) and uses them only to create your account and sign you in.
If you connect your Google Calendar (calendar.readonly and calendar.events permissions) or your Outlook calendar for bookings, OX·IA uses that access only to: see the list of your calendars, so you can choose which one to use; check the times when you are busy, so they are not offered to your customers; and enter in that calendar the appointments booked from the chat (and remove them if they are cancelled). Of your other events we only check when they start and end, never their content, and we do not store it; we do not change or delete them. OX·IA stores the email of the connected account to identify the connection. We do not access any other data in your Google or Microsoft account.
If you connect your Outlook or Microsoft 365 mailbox under Connections, OX·IA uses that access only to read the email that arrives in the inbox from the moment you connect it, leave drafts or send replies in the same thread, as you choose, and store a copy in Sent Items. It does not read earlier email or your other folders, and it does not reply to automatic replies, mailing lists or newsletters.
The permission is stored encrypted and you can withdraw it at any time by disconnecting the calendar (Bookings → Calendar) or the mailbox (Connections) in the dashboard, or from the security settings of your Google or Microsoft account.
The use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular: that data is not used for advertising, is not sold, is not used to train artificial intelligence models and is not read by any person, except with your express permission, for security purposes or where required by law.
5. WordPress plugin
Our WordPress plugin sends nothing until you connect your website to OX·IA. From then on, it sends the public content you choose when you synchronise and whenever you publish, change or remove something, so the assistant can answer with it. If you offer bookings through your booking plugin, OX·IA checks the free slots and creates appointments through your own website’s API, protected by a secret key; those appointments are stored in your WordPress, with your booking plugin’s notifications. When you uninstall the plugin, its settings are deleted from your website; your assistant and its conversations remain in your OX·IA account until you delete them.
6. Who we share data with
We do not sell data. We only share it with providers that help us provide the service, under a data processing agreement:
- Clouding.io (Clouding Networks S.L.): Server hosting, databases and backups. Location: Spain (Barcelona, EU).
- Cloudflare, Inc.: Content delivery network, security and bot verification (Turnstile). Location: 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. Location: 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. Location: United States; standard contractual clauses.
- Stripe Payments Europe, Ltd.: Subscription payments and invoicing. Location: Ireland (EU) and United States; EU-US Data Privacy Framework.
In addition, data reaches the services you connect (your calendar, your WhatsApp, your Telegram, your mailbox, your CRM or your webhook address), because you decide so and for the purposes you configure. Those services are yours, not our providers, and they process the data under your contract with them.
And to the authorities when required by law.
7. International transfers
Data that passes through artificial intelligence is processed within the European Union. Some of the other providers process data outside the European Economic Area, as shown by their location. They do so with the safeguards of the GDPR: the adequacy decision for the EU-US Data Privacy Framework or the standard contractual clauses of the European Commission.
8. Your rights
You can access your data, rectify it, erase it, object to its processing, restrict it, request its portability and withdraw your consent at any time, without affecting processing carried out before. Write to us at info@dalvia.tech stating which right you are exercising. You can also change your marketing preferences from your account, in the dashboard.
If you believe we have not handled your request properly, you can lodge a complaint with the Spanish Data Protection Agency (AEPD, www.aepd.es).
9. Security
We apply appropriate technical and organisational measures: encrypted connections, encrypted passwords, optional two-step verification for all accounts, databases not exposed to the internet, role-based access control and separation of each customer’s data.
10. Artificial intelligence
The assistant’s answers are generated by an artificial intelligence model from the content of the customer’s website, including when it answers by voice. The assistant identifies itself as such to visitors. No decisions producing legal effects on individuals are taken based solely on automated processing.
11. Changes
If we make significant changes to this policy, we will let you know and, where necessary, ask you to accept it again.