Cookie Notice
Last updated:
Which cookies and local storage this website uses, what each one is for and why none of them needs your consent.
In short
- This site only uses essential cookies and local storage: the ones it needs to work, or to remember a preference you choose.
- We don't use analytics, advertising, social media or third-party cookies, or any measurement tool.
- We don't ask for consent because none is needed: there is no cookie banner, and nothing to accept or reject.
- The full inventory is below: each name, how long it lasts, what it is for and why it is exempt.
1.What they are and what the law says
A cookie is a small file a website stores on your device. The browser's local storage (localStorage) does a similar job. Article 22.2 of Spanish Law 34/2002 (LSSI-CE) treats both the same way: it requires information and consent to use them, unless they are strictly necessary to provide a service you expressly requested.
2.What this site uses
This is the complete inventory, checked against the site's code on October 8, 2026. There is nothing else:
ward-idioma
- Type
- First-party cookie
- Purpose
- Remembers the site's language (English or Spanish). It is needed so that forms, alerts and the service's replies come out in that language, and to return to it when you arrive without a language in the address.
- Duration
- 1 year.
- When it is created
- When a page is served: it stores the language of the page you asked for (the one in the address or, if it has none, your browser's) and changes it if you pick another with the language selector.
- Details
- First-party. Secure (in production), SameSite=Lax, path “/”. It only contains “es” or “en”.
- Category (AEPD guide)
- Preferences or personalization (language)
- Why it needs no consent
- The guide exempts personalization cookies when they respond to a person's choice, such as the language. This one only stores the language of the page you asked for or chose, isn't used for anything else and doesn't build profiles.
ward_sesion (en producción, __Host-ward_sesion)
- Type
- First-party cookie
- Purpose
- Keeps you signed in so you don't need a new link on every page.
- Duration
- 30 days, or until you sign out. You sign in with a one-time link, with no password, which is why it outlasts the visit.
- When it is created
- Only after you sign in with the access link (it doesn't exist before, nor on the public site).
- Details
- First-party. HttpOnly, Secure (in production), SameSite=Lax, path “/”. It holds a random code with no personal data; in the database we only store its hash.
- Category (AEPD guide)
- Essential: authentication and user identification
- Why it needs no consent
- It is needed to provide the service you asked for when you signed in (section 1 of the guide).
ward_nav
- Type
- First-party cookie
- Purpose
- Identifies the browser with a random code so that the free scan you run without an account stays yours: to reuse it and, if you create an account, move it there.
- Duration
- 7 days, as long as the scan can be moved to an account.
- When it is created
- Only when someone without an account runs a free scan. It doesn't exist while the site doesn't offer the scan (for example, during the pre-launch).
- Details
- First-party. HttpOnly, Secure (in production), SameSite=Lax, path “/”. A random code with no personal data; in the database we only store its hash.
- Category (AEPD guide)
- Essential: functionality you asked for
- Why it needs no consent
- It is created when you ask for the scan and only serves to deliver and link that scan to you. It isn't used for measurement, advertising or tracking you across pages.
ward-tema
- Type
- Local storage (first-party)
- Purpose
- Remembers whether you prefer the light or the dark theme.
- Duration
- No expiry, until you change it or clear the site's data.
- When it is created
- Only when you pick “light” or “dark” with the theme button. If you pick “system”, it is deleted.
- Details
- Browser local storage. It holds “claro” (light) or “oscuro” (dark). It is never sent to any server.
- Category (AEPD guide)
- Preferences or personalization (interface appearance)
- Why it needs no consent
- You choose it and it only changes the appearance (the guide's example is color contrast). It never leaves the device.
ward-explicacion-… (seguido de un identificador de usuario)
- Type
- Local storage (first-party)
- Purpose
- Remembers whether you left the detailed explanation open or closed on a finding's page in the dashboard.
- Duration
- No expiry, until you change it or clear the site's data.
- When it is created
- Only in the dashboard, signed in, when you open or close the explanation.
- Details
- Browser local storage. It holds “1” or “0”. It is never sent to any server.
- Category (AEPD guide)
- Preferences or personalization (interface appearance)
- Why it needs no consent
- You choose it, it only changes how the page is shown and it never leaves the device.
3.What we don't use
- Analytics or measurement cookies, or visitor statistics tools.
- Advertising or behavioral advertising cookies, or tracking pixels.
- Third-party cookies, social media buttons or content embedded from other sites.
- Browser fingerprinting.
- Fonts requested from Google: they are served from our own domain.
If we later add analytics with cookies or a third-party service that uses cookies, we will explain it here and, if consent is needed, ask for it before using them. If we ever measure visits, it will be with a cookie-free tool (for example, Vercel Web Analytics) and we will explain it here before turning it on.
5.How to delete or control them
- Language: change it with the language selector in the footer.
- Theme: change it with the theme button; “system” deletes the saved preference.
- Session: signing out deletes the session cookie.
- All of them: you can delete or block them in your browser settings. If you block the essential ones, parts of the site may stop working (for example, the language won't be remembered or you won't be able to sign in).
6.More information
For how we handle personal data, see the Privacy Policy. For any question about cookies, email onboarding@resend.dev. We will update this page when anything in the inventory changes.