What the AiRankia tag collects
Last updated 14 July 2026. This page describes the optimization tag (v.js) that AiRankia customers install on their own websites. It is written to be linked directly from a website’s cookie or privacy banner.
The short version
The tag measures how a page performs, not who visited it. It does not use cookies, does not build a profile, does not assign a visitor ID, and does not follow anyone across websites. Nothing it collects identifies a person, and nothing a visitor types into a form is ever read.
What it stores in the browser
No cookies are set. Two browser storage keys are used, both first-party:
| Key | Purpose | Lifetime |
|---|---|---|
uiux-v-<site> (localStorage) | Which version of the page this browser was shown, so a returning visitor keeps seeing the same one instead of the layout changing under them. | Until browser storage is cleared |
uiux-e-…, uiux-c-…, uiux-b-… (sessionStorage) | Flags so the same event is not counted twice in one visit. | The browser session |
What it sends
| Field | What it is |
|---|---|
| Page version | The identifier of the page version shown. Not tied to a person. |
| Event | One of: page shown, goal completed, scrolled halfway, repeated frustrated clicking, form left unfinished. |
| Device class | The word mobile or desktop, derived from window width. Not a device fingerprint. |
| Traffic source | The utm_source in the URL, or the hostname of the referring site (e.g. google.com). Never the full referring URL. |
| Language | A two-letter code, e.g. es. |
| Abandoned field | Only when a form is left unfinished: the name or label of the last field the visitor was in — for example phone_number. This tells the site owner which question people give up on. What the visitor typed is never read or sent. |
What our servers see, and what we keep
Like any web request, the tag’s request reaches us with an IP address and a user-agent. We use the IP only to rate-limit abuse and to derive a two-letter country code, and the user-agent only to discard bot traffic. Neither is written to our database.
What we store are counters — how many times a page version was shown, and how many times a goal was reached, grouped by device / source / language / country. There are no per-visitor records: no event log, no IP addresses, no user-agents, no timestamps per visit. We could not single out a visitor even if we were asked to.
Turning it off
- Global Privacy Control. If a browser sends the GPC signal, the tag does not run at all — nothing is read, written or sent.
- Consent mode. A site can install the tag with
data-consent="required". It then stays completely inert until that site’s consent platform callswindow.uiuxConsent(). - Clearing site data in the browser removes the two keys above.
Because the tag runs on our customers’ websites, the operator of the website you visited is the data controller. AiRankia processes this data on their behalf. Their privacy notice governs; this page explains the mechanics.