Cookie policy
Last updated: 11 November 2026
This is a translation. In the event of any discrepancy, the Spanish version prevails.
A cookie is a small file that a website stores in your browser. Here we explain which ones we use, what for, and how you can manage them, in accordance with Article 22.2 of the LSSI-CE and the guidance of the Spanish Data Protection Agency.
1. Cookies we use
| Name | Owner | Purpose | Duration | Type |
|---|---|---|---|---|
| __Secure-better-auth.session_token | OX·IA | Keeping you signed in to the dashboard | Until you close the browser; 30 days if you tick “Remember me” | Technical, necessary |
| __Secure-better-auth.two_factor | OX·IA | Completing the second step when you sign in, if you have two-step verification enabled | 10 minutes | Technical, necessary |
| __Secure-better-auth.trust_device | OX·IA | Not asking you for the code again on this browser, if you choose this when you sign in | 30 days | Technical, necessary |
| oxia_consent | OX·IA | Remembering your cookie preferences | 12 months | Technical, necessary |
| __cf_bm, cf_clearance | Cloudflare | Telling people from bots and protecting the website (including Turnstile verification) | 30 minutes to 1 year | Technical, necessary |
We also use the browser’s local storage (these are not cookies, but the same rules apply) to remember preferences for using the dashboard, such as the selected assistant or light or dark mode. They are technical and do not identify you.
We do not currently use analytics or advertising cookies. If we add them in the future, they will only be activated if you accept them in the cookie panel, and we will add them to this table. The panel already includes Google Consent Mode (v2), so no Google tool would store cookies without your permission.
2. The assistant installed on other websites
The OX·IA widget that our customers install on their websites does not use cookies. When the visitor uses it, it only stores in the browser an anonymous identifier and the current conversation, so it can continue while they browse (and if they come back within 30 minutes). With that identifier, the visitor can open their previous conversations in that browser from the chat: depending on the business’s plan, those from the last 24 hours up to 30 days. The chat’s own “New conversation” button stops showing the current conversation, and clearing the browser data removes the identifier.
While the page is open and visible, the chat checks every few seconds whether someone from the business’s team has written to it, and remembers which team messages have already been seen, so that it only shows the notification for new ones. That check also lets the business know that the visitor is still on its website at that moment; no history of that presence is stored.
If the visitor uses voice chat, the chat remembers in their browser that they have already read the initial explanation and whether they prefer the assistant to speak more slowly. These are their own preferences, with no personal data.
3. How to manage them
You can change your choice at any time from . You can also delete or block them from your browser; if you block the technical ones, some parts of the website, such as access to the dashboard, will stop working.