Two cookies, both necessary

This page is short because Agnetia uses few cookies: one to remember your language and one to keep your session open. There is no analytics, no tracking and no advertising, so there is nothing to consent to.

Version of 20 September 2026

The company's identifying details are not published yet. Nothing this page says about cookies depends on them, and it is accurate as it stands.

01 / 05

Why this page is so short

A cookie is a small file a site stores in your browser so it can recognise it on your next visit. The rules — article 22(2) of the Spanish LSSI-CE, transposing Directive 2002/58/EC — require consent before installing cookies, with one exception: those strictly necessary to provide a service the user has expressly requested.

Agnetia's two cookies fall within that exception. That is why you will not see a consent banner: there would be nothing to accept or reject, and a banner asking permission for something that does not need it is noise, not transparency.

If an analytics or advertising cookie were ever added, this page would change and a real banner would appear, with the option to refuse as visible as the option to accept.

02 / 05

The cookies Agnetia uses

Name	What for	Lifetime	Type
lal-lang	Remembers which language you want to read the site in, so you are not asked again or served another one	1 year	First-party, technical preference
__Host-agnetia_rt	Keeps you signed in without typing your password every time. It only exists if you have signed in	30 days, renewed each time it is used	First-party, technical authentication

The second is marked so that the page's own code cannot read it and it does not travel anywhere else. That is what stops someone taking your session from outside, and the reason it exists as a cookie rather than being stored some other way.

Outside your session this cookie says nothing about you: it is a random value checked against a record stored hashed.

03 / 05

What is not a cookie but is worth telling you

Besides those two cookies, the site keeps in your browser's local storage the short-lived session identifier — fifteen minutes — that the private area uses to talk to the API, together with your name, your email and your profile languages, so they do not have to be asked for on every screen.

That is not a cookie: it does not travel with every request and it is not sent to any third party, and it is cleared when you sign out. It is mentioned here because from your side it amounts to the same thing — information left on your device — and hiding it behind a technicality would be petty.

Your light or dark theme preference on the pages that offer one is stored there too.

04 / 05

Third-party cookies

Agnetia installs no third-party cookies on its own domain. There is no analytics, no advertising pixel and no social button that tracks you.
When you pay, you leave for a page belonging to the payment provider, on its own domain. Any cookies it installs there are its own and are governed by its policy, not this one.
The Sign in with Google button loads a Google component, which may install its own cookies on its domain to verify your identity. It only comes into play if you press that button.
The voice agent loads in a frame with its own origin inside your account, and installs no tracking cookies.

05 / 05

How to control them

You can block or delete any cookie from your browser's settings, and every browser lets you do it per site. Instructions are in the help pages of Chrome, Firefox, Safari, Edge and Opera.

Bear in mind the effect: blocking the session cookie means you cannot stay signed in and will have to identify yourself constantly. Deleting the language one means the site will choose the language again from your browser settings.

Deleting cookies does not delete your account or your data: it only makes this browser stop remembering you.