Why your Liite page has no cookie banner

You've seen it a thousand times. You tap a link, and before you see anything, a box slides up asking you to accept cookies. On a link-in-bio page, where people arrive from a phone and want one link, that box is often the first and last thing they see.

Your Liite page doesn't have one, because it doesn't need one. Here's why, and exactly what we do count.

Cookie banners exist because of tracking

In the EU and the UK, a site has to ask before it stores anything on a visitor's device that isn't strictly needed to show what they asked for. Most analytics tools set a cookie with an ID for each visitor, so they can follow them from visit to visit. That needs consent, so the site needs a banner.

The simplest way to avoid the banner is to not store anything on the visitor's device. That's the approach Liite takes.

What happens when someone opens your page

Your page loads one small script from Liite. It does two things:

1. When the page opens, it sends one message saying "this page was viewed".
2. When someone taps a link or a button on your page, it sends one message saying "this block was clicked".

That's all it does. The script doesn't set cookies, doesn't use local storage, and sends its messages without any cookies attached. It doesn't follow visitors to other sites, and there's no advertising pixel on your page.

What we count

Each view message carries:

• The page address, so we know which page or tab was viewed.
• The referrer: the site the visitor came from. We keep only the domain, like instagram.com, not the full address.
• The utm_source tag, if your link had one, so you can tell your newsletter from your Instagram bio.
• Whether it came from your QR code. Your page's QR code adds a small marker to the address, so a scan counts as a QR scan.

From the request itself, we also note:

• The country, from the network the request came through. Only the two-letter country code is kept.
• The device, operating system and browser, reduced to broad groups like "mobile", "iOS" and "Safari".

All of this goes into one set of totals per page, per day. Your dashboard shows views, unique visitors, clicks, QR scans, views per day, and your top referrers, countries, devices and links.

What we don't keep

• No cookies and nothing else stored on the visitor's device.
• No IP addresses in your stats. The IP address is used for one thing, explained below, and never stored with your numbers.
• No visitor profiles. There's no record of "this person saw these pages". There are only daily totals.
• No bots. Known crawlers and bots are ignored, so they don't inflate your views.

So how do you count unique visitors?

This is the clever bit. To know whether today's view is someone's first or fifth, you'd normally need an ID cookie. We do it differently.

When a view arrives, we mix together a secret, today's date, your page, the visitor's IP address and their browser's user agent, and run it through a one-way hash. That gives a short code that can't be turned back into the IP address. If we've seen that code today, it's a repeat view. If not, it's a new unique visitor.

Those codes are kept in a separate list that deletes itself within a day and a half. They're never stored with your stats. Because the date is part of the mix, tomorrow's code for the same visitor is completely different, so nobody can be followed from one day to the next.

The trade-off is that a "unique visitor" means unique per day. Someone who visits on Monday and again on Tuesday counts once each day. For a page like yours, that's the number that matters.

How long your stats are kept

Stats are daily totals with nothing personal in them. On Free you can see the last 7 days. Pro shows 90 days and Business 2 years.

The small print, honestly

A few things on a page can still come from somewhere else, and it's fair to say so:

• Embeds. If you add a Spotify player, a SoundCloud track or a Google map, that player is loaded from the other service, inside its own frame, and that service's own rules apply to it. YouTube videos use YouTube's privacy-enhanced address (youtube-nocookie.com). If you want a page with nothing from anyone else, use links instead of embeds.
• Theme fonts. Some themes load their typeface from Google Fonts. Google Fonts doesn't set cookies.
• Password pages. If you put a password on your page (Pro), visitors who type it in get one cookie that remembers they've unlocked it. That's strictly needed for the feature to work, so it doesn't need a banner either.

None of this is legal advice, and your own situation may need more thought, for example if you add other tools to an uploaded site. But for a Liite page built from blocks, the default is simple: we count, we don't track, and your visitors get straight to your links.

Uploaded sites too

The same script runs on the HTML pages of your uploaded sites at yourname.liite.site, with the same rules. If your own code adds a tracker, that part is up to you.

Want a page that opens straight to the good stuff? Sign up and claim your name.