Cookieless, and specific about what that means.

The mechanism, the guarantee it buys, and the accuracy it costs.

Not a cookie banner removed from the same tracking

Plenty of tools call themselves cookieless while keeping a stable identifier derived from the request instead — same tracking, fewer disclosures. FunnelSights derives a hash from the user agent, IP and domain under a salt that rotates every 24 hours and is deleted after 48. The IP and user agent are never stored, and once the salt is gone the hashes cannot be recomputed even by us.

Cross-site joining is designed out of the stored data

The tracked domain goes inside the hash. The same person visiting two sites you own produces two different identifiers, so the data we hold cannot be joined across sites by matching it against itself. That is a property of the scheme rather than a policy on top of it.

That is a statement about the data at rest, and we will not stretch it into a cryptographic guarantee it does not support. The inputs are low-entropy: somebody holding a current salt could compute candidate hashes for both domains from the same user agent and IP and match them. Nothing in the scheme prevents that — the 48-hour salt deletion is what closes the window, which is the real guarantee and the one worth checking us on.

What it costs, stated plainly

• Visitor counts are per-day. A multi-day total sums daily distinct counts rather than deduplicating across them.
• Someone who changes network or browser counts twice.
• There is no cross-day user journey, because there is no identifier that survives the night.
• Visits, pageviews and events are exact. The estimate is only in "visitors".

Any product claiming both no identifiers and precise returning-visitor counts is misrepresenting one of them.