UX Surgery · Legal
Cookie policy
The cookies and browser storage used on uxsurgery.com and app.uxsurgery.com, what each one is for and how to change your choice.
Last updated:
What this policy covers
This policy explains the cookies and similar technologies (local storage, session storage and IndexedDB in your browser) used on uxsurgery.com and app.uxsurgery.com, operated by LIQUIDTIC, S.L.. Storage that is strictly necessary for a service you ask for does not need your consent; analytics cookies are used only if you accept them.
This website
uxsurgery.com sets no cookie of its own except the one that remembers your cookie choice. It sets analytics cookies (Google Analytics) and records your session only if you accept analytics in the cookie banner, and never sets advertising cookies.
Your choice is kept in your browser’s local storage (uxs.consent, with the date and the version of this notice) and in the strictly necessary first-party cookie uxs_consent (the same choice, date and version; shared by uxsurgery.com and app.uxsurgery.com, kept for 12 months) so that neither of them asks again. It is not sent to us. If the purposes change, we will update this page and ask again (we did so on 24 October 2026, when session recordings were added).
uxs.replay (session storage, only after you accept analytics): a random identifier of your recording session, with nothing about you in it, kept for up to 30 minutes of inactivity. Deleted when you close the tab or reject analytics.
Google Analytics
Purpose: to count visits and understand, in aggregate, which pages and buttons of uxsurgery.com and app.uxsurgery.com are used, so we can improve them. We do not use the advertising features of Analytics: Google signals, remarketing and ad personalization are turned off, and events never include your email or the addresses of the sites you test.
Google Ads: our Analytics property is linked to our Google Ads account only to measure, in aggregate, which ads lead to sign-ups and purchases (Analytics sends those two events to Google Ads as conversions). Personalized advertising is disabled on that link, we build no audiences and we set no advertising cookies. When you arrive from one of our ads, the click identifier Google adds to the address (gclid, gbraid or wbraid) and the campaign parameters (utm_…) stay in the links to our pages and to the application; they are read by Analytics only if you accept analytics.
Cookies, set only after you accept: _ga (tells browsers apart; expires after 2 years) and _ga_<ID> (keeps the state of the visit; expires after 2 years). They are first-party cookies of uxsurgery.com and app.uxsurgery.com.
Retention: Google Analytics keeps event-level data for 14 months and then deletes it; only aggregated reports remain. Google Analytics 4 does not log or store IP addresses.
Data processor: Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland), under Google’s data processing terms. Data may be transferred to Google LLC in the United States under the EU–U.S. Data Privacy Framework and standard contractual clauses.
Legal basis: your consent (art. 6.1.a GDPR and art. 22.2 of the Spanish LSSI). Until you accept, or if you reject, Google Analytics runs in Google’s “consent mode” without cookies: no analytics cookie is set and no identifier is stored in your browser; Google only receives anonymous, cookieless signals (the page and the event, with no user or session identifier) that it uses to estimate aggregate figures. Only after you accept can it set the cookies above.
How to withdraw: choose “Cookie settings” at the bottom of any page of this site or of the application and select Reject. You can also delete the _ga cookies in your browser. If your browser sends Global Privacy Control or Do Not Track, we do not load Google Analytics at all.
Session recordings
Purpose: to see how visitors actually use uxsurgery.com and app.uxsurgery.com (where they click, scroll, hesitate or get lost) so we can improve the pages. Unless you reject analytics in the cookie banner, your browser records the pages you see and your mouse, keyboard and scroll activity with the open-source rrweb library, and sends it to our own servers. Nothing is sent to a session-recording company.
What is not recorded: everything you type is masked in your browser before it leaves it (passwords, email addresses, site addresses and search terms appear as asterisks); the pages of shared reports are not recorded, nor are our own visits. The recording may show the text on screen, which in the application can include your account email and the sites and results of your studies.
Your IP address is not stored: only a keyed hash of it, to tell sessions apart. A random session identifier is kept in your browser’s session storage (uxs.replay) for up to 30 minutes of inactivity and disappears when you close the tab. The web addresses in a recording lose their query string, so the address of a site you test is never part of it.
Retention: recordings are deleted automatically 30 days after they are made, and earlier when storage runs out (the oldest first). They are watched only by our own team.
Legal basis: our legitimate interest in understanding and improving how our pages are used (art. 6.1.f GDPR), with everything you type masked and no third party involved. You can object at any time by rejecting analytics in the cookie banner, and nothing is recorded after that; if your browser sends Global Privacy Control or Do Not Track, nothing is recorded either.
How to object: choose “Reject” in the cookie banner, or “Cookie settings” at the bottom of any page and select Reject. Recording stops at once and the part not yet sent is discarded. You can ask us to delete your recordings by writing to the address above.
The application
app.uxsurgery.com asks for your consent separately and uses Google Analytics and session recordings on the same terms (the uxs.replay session identifier above included). It also uses this storage, which is strictly necessary and is kept in your browser (only the device identifier below is ever sent to us):
- firebase:authUser:… (local storage): keeps you signed in. Deleted when you sign out. The Firebase sign-in library may also keep technical data in IndexedDB (for example, firebase-heartbeat-database).
- uxs.emailForSignIn (local storage): your email, between asking for a sign-in link and opening it. Deleted when you sign in.
- uxs.lang (local storage): the language you chose.
- uxs.consent (local storage) and the uxs_consent cookie (12 months, shared with uxsurgery.com): your cookie choice, with its date and the version of this notice.
- uxs.device (local storage of app.uxsurgery.com; it is not a cookie): a random identifier of this browser, with nothing about you in it, and its expiry date. It is created the first time you ask for the free first UX test and kept for 12 months from then: using it does not extend that period. Once it expires it is no longer sent, the application deletes it the next time you open it, and a new one is created only if you ask for the free test again. It leaves your browser only in the free-test request (the X-UXS-Device header), never with other requests, to keep that test to one per person (fraud prevention). Storing it is strictly necessary for the free tier you ask for (art. 22.2 LSSI), so it does not depend on your analytics choice; using it is based on our legitimate interest in preventing abuse of the free tier (art. 6.1.f GDPR). We store only a keyed hash of it, for 90 days. Earlier versions also kept it in a uxs_device cookie; the application now deletes that cookie.
- uxs.firstLookUrl and uxs.androidDesc.<project> (session storage): the address of the site for your free first test while you sign in, and an app description you have not sent yet. Deleted when you close the tab.
- uxs.ga.purchases (session storage, only when analytics is set up in the application): avoids counting the same purchase twice in the statistics. It holds only the product code, no identifier. Deleted when you close the tab.
Third-party pages
Payments run on Stripe’s own pages (Stripe Checkout and the Stripe customer portal), where Stripe uses the cookies it needs for the payment and to prevent fraud, under its own cookie policy. If you sign in with Google, Google’s sign-in page uses its own cookies under Google’s policy. We do not control those cookies.
How to change your choice
Use “Cookie settings” at the bottom of any page, or delete cookies and site data in your browser settings. If you block the strictly necessary storage of the application, you will not be able to sign in.