← Back to ADAQNO

Cookie Policy

Last updated 22 October 2026

We use cookies to keep you signed in and, if you choose a language, to remember it. Nothing else. No advertising cookies, no analytics cookies, no third-party trackers, no fingerprinting.

That is why you do not see a cookie banner. The law only requires consent for cookies that are not strictly necessary for something you asked for, and we do not set any — so a banner would be a box that does nothing.

The rule we are working to

Storing information on your device, or reading what is already there, is governed in the European Union by Article 5(3) of the ePrivacy Directive as each country has implemented it — in Hungary, where we are based, section 155(4) of Act C of 2003 on Electronic Communications; in Spain, article 22.2 of the LSSI. Other countries have similar rules, such as PECR in the United Kingdom.

They all say the same thing: we must tell you what we store and ask permission, unless it is strictly necessary for a service you actually asked for. Staying signed in is the textbook example: you asked to sign in, and it cannot be done without storing something. Remembering a language you picked yourself is another: European regulators treat a preference the user chose as part of the service they asked for.

Everything on this page falls inside that exemption. We are telling you anyway, because you are entitled to know what is on your device.

Cookies we set

All of these are ours, on our own domain. All except the language cookie are HttpOnly, so scripts running in your browser cannot read them, and all are marked Secure in production so they only travel over an encrypted connection.

CookieWhat it doesHow long
sb-<project>-auth-tokenHolds your sign-in session. Without it you would be signed out on every page. Sometimes split across two cookies ending .0 and .1 when it is too large for one.Until the session expires or you sign out
sb-<project>-auth-token-code-verifierA one-time value that lets us complete a Google sign-in securely. Useless on its own.10 minutes
oauth_return_toRemembers which page to bring you back to after signing in with Google.10 minutes
oauth_terms_acceptedCarries the fact that you ticked the age and terms box across the trip to Google, so a new account created that way records your acceptance.10 minutes
adaqno-pw-recoveryMarks a session as having come from a password-reset link, so the page that sets a new password knows it may.15 minutes
adaqno_localeRemembers the language you chose with the EN / ES switch, so the site does not change back on your next visit. Set only if you use the switch; until then we follow your browser’s language setting and store nothing. It holds two letters and nothing about you. Scripts on our own pages can read it, because the switch itself sets it.1 year, or until you clear it

<project> is a fixed identifier for our authentication project. The exact names come from our authentication provider and would change if we changed provider; the purposes would not.

Other things we store on your device

Cookies are not the only kind of browser storage, and the same rules cover all of it. We also use session storage, which your browser clears the moment you close the tab.

  • mainAnswers — your answers as you move between questions, so a refresh does not lose your progress.
  • topClusters — carries your top career clusters from the assessment into the follow-up questionnaire.
  • lastAssessmentId — remembers which assessment the follow-up belongs to, including after the trip out to the payment page.
  • checkoutReturnPath — remembers which page you were on before going to pay, so you come back to it afterwards.

We use no local storage, which is the kind that survives after the tab is closed.

Our analytics store nothing at all

We do count things — how many people start the questionnaire, how many reach the payment page, how many finish. Knowing where people give up is how the product gets better.

None of it involves storing anything on your device. The identifier that groups one visit together is generated in memory when the page loads and disappears when you close the tab. No cookie, no local storage, no session storage — so the rules above are not engaged at all, and there is nothing for you to consent to.

The events record that a step happened. They never contain the content of your answers, and the values they can carry are restricted to a short list of pre-approved ones rather than free text. We use no third-party analytics product: nothing about your visit goes to Google Analytics, Meta, or any advertising network.

Third parties

Stripe, when you pay. Paying takes you to a page hosted by Stripe on Stripe’s own domain. Stripe sets its own cookies there — typically __stripe_mid and __stripe_sid — which it uses for fraud prevention. They belong to Stripe, under Stripe’s privacy policy. We do not set them, cannot read them, and receive nothing from them.

Google, if you sign in with Google. You visit Google’s sign-in page, and Google uses its own cookies there under its own policies. If you would rather not involve Google, sign in with an email address and password instead.

Nothing embedded. We do not embed videos, maps, social widgets, comment systems, chat widgets or advertising. That is the usual route by which third-party trackers arrive on a website, and we have kept it closed deliberately.

Controlling cookies yourself

You can block or delete cookies in your browser settings. Instructions are on each browser maker’s help pages, and data protection authorities publish guidance for the public — NAIH in Hungary at naih.hu, and the AEPD in Spain at aepd.es.

Worth knowing first. Because the cookies we set are the ones that keep you signed in, blocking them will stop you signing in at all — you will bounce back to the sign-in page each time. That is not a fault, and it is not us pressuring you into accepting tracking, because there is none to accept. Deleting the language cookie only means the site follows your browser’s language again. Blocking session storage will lose your answers on a refresh.

Some browsers and privacy tools block third-party cookies aggressively. That will not affect our cookies, but it can interfere with the return trip from Google sign-in or from Stripe. If sign-in fails once and then works, that is usually why.

“Do Not Track” and Global Privacy Control signals change nothing here, because we are not tracking you in the first place.

If this changes

If we ever add something that stores information on your device, we will update this page before it goes live. If the new item is not strictly necessary, we will ask your permission first, with a real choice and a real “reject all”.

Questions about anything here: privacy@adaqno.com.

This page is part of the agreement between you and ADAQNO. If anything here is unclear, ask us before you buy rather than after — we would rather explain it than argue about it later.