Cookie notice

Supabase sets it, since Supabase is what handles sign-in, and it does one thing: keeps you inside your account as you move between pages.

Its name begins with “sb-”. It renews itself as you browse and disappears when you sign out.

It is strictly necessary. Without it there is no way to keep you identified, so it cannot be refused without giving up signing in.

It is called “idioma” and it holds two letters: “es” or “en”.

It is only written when you press the language switch in the header yourself. Geolocation never writes it: if it did, “your choice” would really be a trace of where you first connected from.

It lasts a year, because a choice of language does not expire when you close the browser.

It is called “tema” and it holds one word: “claro” (light) or “oscuro” (dark).

It is only written when you press the sun and moon switch yourself. Without it the site shows by day, on a white background, whatever mode your system is in.

It lasts a year, like the language one.

It is called “consentimiento” and it holds one word: “si” or “no”. It is what you decided in the banner, and it exists so the banner does not come back on every page.

It lasts a year if you accepted and six months if you declined. When it expires, the banner asks again.

If your browser sends the Global Privacy Control signal, we take it as a “no” without asking: the cookie is written as “no” and the banner does not appear.

“referido” is written if you arrive through the link of someone who invited you. It holds eight characters — their code — and it exists so their credits are paid if you open an account. It had been written since the referral programme began without appearing on this list; it appears from 20 September 2026.

“sma_origen” is written if you arrive from an ad or from another page, and it holds where you came from: the campaign, the ad, and the domain that linked to you. It tells us which ad brings people who stay, which is the only way not to spend blind.

Neither is shared with anyone or follows you anywhere else, both last ninety days, and the origin one is not written if you decline the pixel: the moment you say no, it is erased.

It does one thing: it tells us which ad brought whom. Without it, advertising is paying blind. When you accept, your browser loads a Meta script that records that you visited the page, that you created an account if you just did, and, if you buy credits, that you bought and for how much.

What Meta receives with that: your IP address, details about your browser, and the “_fbp” cookie it writes itself. If you are signed in to Facebook or Instagram in that browser, Meta can link the visit to your account. Meta does that under its own terms, not ours, and we cannot see it.

What Meta does NOT receive: not your email, not your name, not a single word of what you write or generate here. The pixel does not enter the workspace.

If you decline, the script does not load. Not even the first request to Meta is made.

For California residents: sharing your visit with Meta for advertising counts as “sharing” under the CPRA. Declining here is how you say no, and the Global Privacy Control signal is honoured as such.

Beyond the above, nothing. Specifically:

Below the table on this page there is a control that shows what you chose and lets you change it. If you go from “yes” to “no”, the pixel stops recording from that moment.

Any “_fbp” cookie Meta had already written you delete from your browser settings, like any other. Ours too: delete the session one and you are signed out; delete the language one and the site goes back to deciding by the country you connect from; delete the appearance one and it goes back to day.

You can also block all cookies. The page still reads fine; what you will not be able to do is sign in.