Rawuser / Compare

Can a website personalize without cookies, and does it still need consent?

Short answer

Yes, from what the visit itself carries: a campaign tag, the site a visitor came from, the page they opened.

No cookies does not by itself mean no consent: EU guidance applies the same rule to anything stored on or read from the device, however briefly, and the UK regulator says any purpose relating to decisions about the content shown is outside its appearance exception and needs consent. Whether your setup needs consent is a call for your lawyer or DPO.

Last checked 25 October 2026 · Agshin Rajabov, founder of Rawuser

Can you personalize a website without cookies?

Yes. Anything the request already carries can choose the words: the campaign tags in the address, the referring site, the page opened, the browser's language, a country from your CDN.

Without some memory, a site cannot recognise a returning visitor or keep one version steady as the visitor moves between pages. That memory lives on the device (a cookie, local storage, session storage) or is rebuilt from the device itself (fingerprinting), and each comes with rules of its own.

Reverse IP lookup is a third route: it guesses the company behind the visit's IP address. Nothing has to be stored on the device, but the EDPB says tracking that relies on the IP address alone can fall under the same Art. 5(3) rule (paragraphs 54 and 55 of its Guidelines 2/2023).

What does each kind of personalization store?

Each vendor and regulator fact below was read on its own page on 25 October 2026.

Kind of approachWhat it stores or readsWhat its docs or the regulators say
A/B testing and personalization that remember visitorsOptimizely: the optimizelyEndUserId cookie, a visitor's unique identifier, kept six months from the last page visit, plus local storage keys for events and the variation shown. VWO: the _vwo_uuid cookie, a unique id for every visitor, 365 days. Webflow Optimize: recognises returning visitors and keeps a visitor's bucket number on later visitsOptimizely "does not hold a specific stance" on classifying its cookies and lists consent as one reading. VWO's maker lists its cookies as strictly necessary. Webflow leaves the consent decision to the site owner
Account-based personalizationMutiny, on the pages it hosts: session number, IP address, user agent, referrer, rough location from the IP, time on page and clicks, tracked by defaultMutiny says an opted-out visitor gets no identifier cookies, and "each page refresh/load will generate a new visitor"
Reverse IP company revealThe visit's IP address, matched to the company it may belong to; nothing has to be stored on the device. Webflow's Enterprise company rule uses reverse IP lookup to guess where a visitor worksThe EDPB says tracking based on the IP address alone can fall under Art. 5(3) (paragraphs 54 and 55)
FingerprintingDevice and browser attributes combined to recognise a browser again, with nothing stored to deleteThe EDPB says fingerprinting falls within Art. 5(3) (paragraph 2, from Opinion 9/2014). The ICO says it needs consent when used for online advertising. Banned by Rawuser's own rules, whatever a law allows
Server-side rules on what the request carriesYour server or CDN reads the address's campaign tags and the referrer and returns different words; nothing is stored unless it also sets a cookieThe EDPB counts a tracking link that carries an identifier in the address as in scope (paragraphs 49 to 51)
RawuserNo cookies. In tab storage: a random visit code, two labels for why the visit came and from where, and a copy of the version's text for up to eight of the site's pages; they expire after 30 minutes without activity and go when the tab closes. Reads campaign tags, the referring site's host, the names (never values) of click ids, the page path, the language and the browser's user agent; the user agent and the country are used and not storedNo fingerprinting and no identifier that survives the tab. Whether your site needs consent is your call; we give you the paragraph for your privacy notice

Is browser fingerprinting allowed under GDPR?

Regulators treat it as access to the device, the same as a cookie, and the ICO says it needs consent when used for online advertising.

The EDPB's guidelines recall that the Article 29 Working Party's Opinion 9/2014 already put fingerprinting within the scope of Art. 5(3). The ICO notes that users are often unaware of fingerprinting for advertising, and says device information used to adapt a site must not be reused to identify a user by fingerprinting.

A visitor can clear a cookie. Fingerprinting leaves nothing on the device to clear.

What does Rawuser store?

No cookies. The tab keeps a random visit code, two labels and a copy of the version's text, and the browser clears them when the tab closes.

The visit code is 32 random characters drawn by the browser, not derived from the device, and expires after 30 minutes without activity. It counts each visit once, ties the visit's counted clicks to the version it saw, and, while a test runs, decides which visits (1 in 5 by default) see your page as built. The two labels say why the visit came and from where, so the next page shows the same version.

On our side: one row per page view and counted click, with the page path (no query string, record ids as :id), the source and reason words, the version shown and its test arm, the time and the visit code. The visit code is cleared from those rows after 31 days. No names, emails or IP addresses are stored, and nothing follows a person to another site.

We claim no consent exemption for this tab storage: the labels and the copy exist to change the words a visit sees, a purpose the CNIL's and the ICO's exemptions as written do not cover. If your consent tool holds our tag back until a visitor agrees, a visitor who says no sees your page as built.

What you can do today, with no tool

  1. List what your scripts already store.

    Open your site in a private window, then your browser's developer tools: Application (Chrome) or Storage (Safari, Firefox). Note every cookie and every local and session storage key, and which script set it.

  2. Write down why each one is there.

    The usual purposes are measurement, a test split, a remembered version and ads. The purpose decides which exemption, if any, a lawyer can consider.

  3. Read each vendor's own storage page.

    Most publish one. Check the names, the lifetimes and whether the vendor takes a stance on consent or leaves it to you.

Sources

  1. EDPB, Guidelines 2/2023 on the technical scope of Art. 5(3) of the ePrivacy Directive (version 2.0, adopted 7 October 2024) read 25 October 2026
  2. CNIL, Cookies : solutions pour les outils de mesure d'audience (4 July 2025) read 25 October 2026
  3. ICO, Guidance on the use of storage and access technologies: What are the exceptions? read 25 October 2026
  4. Optimizely, Cookies and localStorage in snippets (updated 23 October 2026) read 25 October 2026
  5. Wingify (VWO), Cookies Stored by Wingify (updated 23 September 2026) read 25 October 2026
  6. Mutiny Help, Implementing Cookie Consent (updated 23 October 2026) read 25 October 2026
  7. Webflow Help, Analyze & Optimize tracking settings (updated 13 May 2025) read 25 October 2026
  8. Webflow Help, Build rules-based audiences (updated 23 May 2025) read 25 October 2026

Related questions

Start your pilot

See it on your site.

Free for 30 days. Leave your email and your page; we reply within a day with what your own page would say to a visitor from ChatGPT.

We use your email only to reply. Privacy

What happens next

  1. 01

    Within a day, your own page.

    What it would say to a visitor from ChatGPT, written from your page.

  2. 02

    We set it up with you.

    You see your page and its first version before anything goes live.

  3. 03

    Day 31, you decide.

    Keep it from $99 a month, or stop and owe nothing.