Cookieless website personalization and GDPR: what consent rules require
Personalizing a landing page from the campaign in its URL is much easier to justify under EU privacy law than identifying companies by IP address or building profiles across visits. But a tool that sets no cookies is not automatically exempt from consent: Article 5(3) of the ePrivacy Directive covers storing or reading any information on the visitor's device, which includes localStorage and sessionStorage. Check what a script stores, and when, and have your data protection officer assess it.
What Article 5(3) covers
Article 5(3) of Directive 2002/58/EC allows storing information, or gaining access to information already stored, on a user's device only with consent based on clear and comprehensive information. The rule is about the device, not about cookies: a value written to sessionStorage is stored information just as a cookie is.
There are two exemptions: storage whose sole purpose is carrying out the transmission of a communication, and storage that is strictly necessary to provide a service the user explicitly requested. Whether a personalization script qualifies is decided case by case. The EDPB's Guidelines 2/2023 on the technical scope of Article 5(3) also discuss URL and pixel tracking, IP-based tracking and unique identifiers.
Separately, any processing of personal data needs a GDPR legal basis, a processing agreement under Article 28 GDPR with the vendor, and safeguards for transfers outside the EEA. Each country implements Article 5(3) in its own law:
Four kinds of personalization
| Kind | What happens | Usual assessment |
|---|---|---|
| Campaign parameters, nothing stored | The script reads utm_term or utm_campaign from the URL and changes the text. | No access to the device beyond the page itself; usually the easiest to justify. |
| Campaign parameters, stored for the tab | As above, and the script also keeps values in sessionStorage. | Within Article 5(3): check whether an exemption applies, or ask for consent. |
| Company identification by IP address | The visitor's IP address is matched to a company. | Processing of personal data; needs a GDPR legal basis. |
| Profiles across visits | Behavior is stored and recognized from one visit to the next. | Usually requires consent. |
This overview is not legal advice. The assessment depends on the tool and how you configure it.
What the GetIntent script does
- It sets no cookies.
- For the current tab it keeps the site configuration, the personalized copy, the landing UTM parameters and a random tab ID in sessionStorage. The browser deletes them when the tab closes. Before the consent check it stores only the site configuration, no visitor data.
- While it waits for consent, it also reads (never writes) the consent record that the GetCookies consent banner keeps in localStorage, so it notices when the visitor agrees.
- The consent check is on by default: when Google Consent Mode v2 reports that analytics storage is denied, GetIntent starts neither personalization nor tracking until consent is granted. On a page without Google Consent Mode, the script starts straight away.
- Experiments assign visitors by the random tab ID, not by IP address or user agent. IP addresses stored with personalization data have the last octet removed first.
- Servers and the database run in the EU. AI copy is generated by Anthropic in the US, covered by the data processing agreement and listed as a subprocessor.
- GetIntent is not SOC 2 or ISO 27001 certified.
Details: cookie and storage notice, security and data location, data processing agreement and subprocessors.
Questions to ask any vendor
- What does your script store on the visitor's device, and when?
- If the visitor declines consent, does the script wait until consent is given?
- Do you process IP addresses or identify companies?
- Where are your servers and database, and which subprocessors are outside the EEA?
- Do you offer a data processing agreement and a list of subprocessors?
Questions
Does website personalization need consent under the GDPR and ePrivacy rules?
Not always, but often. As soon as a script stores or reads information on the visitor's device, Article 5(3) of the ePrivacy Directive applies unless the storage is strictly necessary for a service the visitor asked for. Profiles across visits usually need consent.
Is a tool that sets no cookies automatically compliant?
No. Article 5(3) is about information stored on the device in general. localStorage and sessionStorage are covered as much as cookies are, so ask what a cookieless tool stores instead.
Is personalizing by UTM parameters processing personal data?
The UTM value describes a campaign, not a person. It becomes personal data when a tool links it to an IP address, a visitor ID or a profile, so ask what else is processed alongside it.
Is GetIntent cookieless?
Yes, the GetIntent script sets no cookies. It does keep the site configuration, personalized copy, landing UTM parameters and a random tab ID in sessionStorage for the current tab, so being cookieless does not by itself make it consent-free. Your data protection officer should assess it for your site.
Does GetIntent run before the visitor gives consent?
If your page uses Google Consent Mode v2 and the visitor declines, no: GetIntent waits for consent. Without Google Consent Mode on the page, the script starts straight away. You can turn the consent check off per site, but it is on by default.
Sources
Personalization that waits for consent
The consent check is on by default. Try it on one landing page: free plan, no credit card.