How we count

We count visits, never people

This is the whole method, for the developer installing Pagebee and the person who has to approve it. If something here is vague, tell us and we'll fix the page.

  1. RequestA pageview arrives with an IP and a user agent
  2. CheckedGPC, DNT, bots and unknown hosts stop here
  3. Hashed at your midnightIP, user agent, property and environment, keyed with today's salt
  4. CountedThe visit is counted. The hash and salt are deleted when the day closes

The short version

  • No cookies, no device storage

    The script sets no cookies and never touches local storage or session storage.

  • IP addresses never stored

    The IP is used in memory to make a hash and never written to a table or a log.

  • One day, then gone

    The visitor hash lasts for one day of the property's own time, then it and its salt are deleted.

  • GPC and DNT respected

    If the browser asks not to be measured, we record nothing at all.

Step by step

Here is what happens to one pageview from a browser, in order. App events from the Swift and Kotlin SDKs follow the same path.

  1. 1. The request arrives at our API with the page, the referrer, the screen width and the user agent. The query string has already been cut back to campaign tags in the browser, so tokens or emails in your URLs never leave it.
  2. 2. It's checked. If the browser sends Sec-GPC: 1 or DNT: 1, it's dropped. So are known bots, prefetches and headless browsers. The site key picks the property, and your hostname rules pick the environment. A host you haven't named is dropped, so a copied key can't add traffic to your numbers.
  3. 3. The day's salt is fetched. Each property and environment gets 32 random bytes for each day, created at the first event after midnight in the property's timezone. A London site rolls over at London midnight, not UTC's.
  4. 4. A hash is made in memory. HMAC-SHA256 of the IP, user agent, property and environment, keyed with the salt and our master key, cut to 16 bytes. The full IP is used, because hashing a truncated IP merges everyone on the same mobile network and browser into one visitor.
  5. 5. The visit is counted. The hash tells us whether this browser has been seen today, so a visitor is counted once and a visit (30 minutes of activity) is stitched together for bounce rate and duration.
  6. 6. The day closes. About an hour after the property's midnight, the day's totals are computed, the hash is cleared from every event of that day, and the salt is deleted, in one transaction. After that, nobody can work out the hash again, us included.

This is what the raw events table keeps once a day has closed. There is no IP column, and the hash column is empty:

events (one row, after the day closes)
ts                2026-11-19 14:02:11+00
day               2026-11-19          -- the property's local day
name              pageview
path              /pricing
referrer_host     news.ycombinator.com
channel           Referral
country           DE
device            desktop
browser           Firefox
visit_id          8c1f…                -- random, not derived from the visitor
new_visitor       true
visitor_hash_day  NULL                 -- cleared when the day closed

What we can't tell you, and why

Because the hash is gone at the end of each day, someone who visits on Monday and again on Wednesday counts as two visitors. Visitors over a week are the sum of each day's visitors, and the dashboard says so beside multi-day numbers.

We can't tell you who anyone is, where they went on other sites, or whether the person on your iPhone app is the person on your website. Retention cohorts need a stable identifier, so they aren't available at this level. If you need to follow individuals across devices, Pagebee is the wrong tool, and that's on purpose.

Global Privacy Control and Do Not Track

The script checks both before sending anything, and the API checks the headers again. Either one means the event is never recorded: no hash, no count, no log line. Owners can also switch on “Ignore my visits” for their own browser.

Bots

Known crawler user agents, prefetch requests and automated browsers (navigator.webdriver) are dropped before counting. Bot traffic doesn't count toward your usage.

How long we keep things

IP addressNever stored
Visitor hashUntil the day closes, about 25 hours at most
Daily saltDeleted when the day closes
Raw events25 months (12 on Free)
Daily totalsFor the life of the account
Live feed items90 days

Where data lives, and who touches it

Everything runs on Google Cloud in Belgium (europe-west1): the API, the database and the backups. Pagebee is operated by Never Before Seen Ventures Limited in London. The full list of subprocessors, and what each one sees, is in our privacy policy.

The line for your privacy notice

Copy this into your own privacy notice, and adjust it if your setup differs.

We use Pagebee to measure visits to this site. Pagebee doesn't use cookies or store anything on your device, doesn't store your IP address, and can't identify you. It counts each visitor once a day using a code that is deleted within about a day. If your browser sends Global Privacy Control or Do Not Track, nothing is recorded.

This is a starting point, not legal advice. Your own notice depends on everything else your site does.

Feed events and redaction

Live feed events come from your server or your app, so they can contain anything you put in them. Before a feed item is stored or pushed, we mask email addresses in the text and the values of properties named email, name or phone. Pushes carry the emoji, the event name and the fields you allow, such as amount, plan and country.

If your app sends a user id for signed-in features, the SDKs hash it on the device with your own salt before it leaves, and it's never joined to anonymous web visits.

Questions

Why not truncate the IP before hashing, like some tools do?

Because it undercounts. Everyone behind the same mobile network block with the same browser version becomes one visitor. We hash the full IP in memory, never store it, and delete the hash within a day, which protects the same thing without the error.

How is this different from Fathom's method?

Fathom rotates its salt at UTC midnight and keeps the signatures with the events. We rotate at each property's own midnight, so daily visitors are right in your timezone, and we clear the hash when the day closes. Their description is on usefathom.com/data.

Do you sell or share the data?

No. Your data is used to run Pagebee for you and nothing else. It isn't used to train models and isn't shared beyond the subprocessors listed in the privacy policy.

Can I get a data processing agreement?

Yes. Our processing terms are in the privacy policy, and we sign a DPA on request. Email hey@neverbeforeseen.co.

Analytics you can explain to anyone who asks

Free to 10,000 events a month. No card.