You keep seeing “cookieless” on analytics tools, often next to a hint that you can drop your consent banner. A cookieless tool tells visitors apart from what every request already carries, the IP address and the browser, scrambled with a secret that gets thrown away daily. It counts people within a day and forgets them overnight.
That trade buys privacy and keeps the data in your own database. It also narrows the consent question without settling it, because the EU rule covers more than cookies. The worked example below is Vireo Analytics, the free cookieless WordPress plugin from RebelCode.
How a tool counts you without a cookie
The tracker sends the page’s path, the referrer and the post ID. The server sees the IP address and the browser (the user agent) that arrive with every request.
Vireo mixes the IP address and browser with a secret and keeps only the scrambled result. Technically that’s an HMAC-SHA256 hash. The same reader on the same day produces the same result, which is how Vireo knows they’ve already been counted.
The secret is random and changes every day. It rolls over at midnight in your site’s own timezone, the one set under Settings, General in WordPress. Vireo keeps today’s secret and yesterday’s, so a visit that straddles midnight still works, and deletes anything older. Once a day’s secret is gone, even someone holding a copy of your database can’t work out which IP address a hash came from.
The tracker stores nothing on the visitor’s device: no cookies, no local storage, no session storage. On your server, the records that tell visitors apart within a day are deleted after two days.
Vireo writes the raw IP address to a buffer file on your server while a view is processed and uses it to look up the country. The file is deleted when the view reaches the database, usually within a minute. Raw IPs never land in the analytics tables. Country lookups are cached for 30 days under a keyed hash made with your site’s own WordPress secret, not the IP itself.
What stays long term is daily totals: pageviews, visitors, time on page, bounce rate, referrers, countries and devices. You choose how long to keep them, from 90 days to 5 years or never purge, with 2 years as the default. Time on page and bounce rate are daily counts per page.
Google Analytics 4 recognizes the same person across visits with its _ga cookie, which Google says is used to distinguish users, so over a month a reader who visits on ten days is one user in GA4 and ten in Vireo. Why analytics tools show different numbers goes through the gap.
What you get
The visitor’s device holds nothing, so the cookie part of the consent question doesn’t arise for Vireo. Your own database holds no cross-day profile of anyone either.
The data stays in your WordPress database. No visitor data goes to RebelCode or anyone else, including the outside services you choose to connect, such as Search Console or an import.
Visitors whose browsers send Do Not Track or Global Privacy Control aren’t counted at all. It’s always on.
Because visitors can’t be identified, there’s no per-person data to export or erase. The privacy docs still recommend mentioning Vireo in your privacy policy.
Does cookieless mean no consent banner?
The rule that produced cookie banners is Article 5(3) of the EU’s ePrivacy Directive. It covers “the storing of information, or the gaining of access to information already stored, in the terminal equipment of a subscriber or user,” and allows it only with consent. There are two narrow exceptions: technical storage for carrying out the transmission of a communication, and what’s strictly necessary to provide a service the user explicitly asked for. Being cookieless doesn’t put a tool outside it automatically.
The rule reaches past cookies. In October 2024 the European Data Protection Board adopted its final Guidelines 2/2023 on the scope of that article. They say it “does not exclusively apply to cookies, but also to ‘similar technologies’.” They also say that information sent through protocol mechanisms such as the IP address or the HTTP user agent, when relied on to collect information (fingerprinting is the example), “can lead to the application of Article 5(3).” Those are the same inputs a cookieless tool uses.
The guidelines add that applicability “does not systematically mean that consent needs to be collected.” Each case has to be assessed for whether an exemption applies.
Regulators do accept that some audience measurement can run without consent. France’s regulator, the CNIL, says in its analytics guidance from June 2020: “Subject to a number of conditions, cookies used for audience measurement are exempt from consent.” The conditions include informing users and letting them object, limiting the purpose to audience measurement, and not cross-checking the data with other processing. They also cover keeping the tracker to a single publisher, truncating the last byte of the IP address and limiting tracker lifetime to 13 months.
The sheet is written about cookies and comes from one country’s regulator. It says itself that it “may be subject to national variation” and advises contacting your local data protection authority. It shows what an exemption can look like for audience measurement.
National regulators and courts in each country decide, not the analytics vendor. Whether you can drop your banner also depends on everything else your site loads, such as ads, embeds and other scripts. If it matters for your site, ask your own adviser. This is a summary of what the rules say, not legal advice. WordPress analytics without a cookie banner goes further into the rule.
By default Vireo counts without waiting for consent, because it stores nothing on the device. If you or your adviser want it to wait, it works with consent plugins that use the WP Consent API, such as Complianz, Cookiebot and Real Cookie Banner. One filter makes it wait for statistics consent:
add_filter( 'vireo_require_consent', '__return_true' );
Views made before consent are held in the page and sent once the visitor agrees. The consent plugin docs have the setup.
Questions to ask any cookieless tool
Put these to any vendor. Vireo’s answers follow.
- What identifies a visitor? A keyed hash of the IP address and browser. Nothing is stored on the device.
- How often does the secret change, and are old ones deleted? Daily, at midnight in your site’s timezone. Vireo keeps today’s and yesterday’s and deletes the rest.
- Where does the data live? In your own WordPress database. No visitor data goes to RebelCode or anyone else.
- Is the raw IP address stored? Only in a buffer file for the country lookup, usually for under a minute. It never reaches the analytics tables.
- Can it wait for consent? Yes, through a WP Consent API plugin and the filter above.