We track as little as possible, and what we do track is built so no one — including us — can tie it back to you. Here's the actual code, not just the promise.
Zero-identity, by architecture — not just by policy.
No cookies, no user ID
Search and listing analytics carry no identity at all — not a cookie, not a session, not a fingerprint. There is nothing to tie an event back to a person.
Hashed IPs, rotating salts
Where an IP is touched at all, it's hashed with a salt that rotates — so even we can't reverse it back to an address after the fact.
K-anonymity thresholds
A number only ever surfaces once enough distinct events feed it. Rare searches and low-traffic listings don't get exposed as identifiable one-off signals.
This covers how we measure search and listing performance. For the full picture of what we collect and why, read the Privacy Policy.
The telemetry pipeline is public.
Don't take our word for what the tracker does — read it. Every piece of the pipeline that touches a visitor's activity is open source.
telemetry-js
Runs in your browser
Captures search and click events client-side, strips identifying headers, and fires a stateless payload — no cookies set, nothing stored locally.
View sourcetelemetry-go
The ingestion gateway
Accepts events, hashes IPs with a rotating salt, and rolls activity into HyperLogLog counters — built so raw, identifiable events never touch disk.
View sourcetelemetry-php
The receiver
Verifies each incoming batch with HMAC signatures and stores only the aggregated metrics this app actually uses — trending searches, listing performance, nothing per-person.
View sourceWhat we keep out, and why, in the open.
Being excluded from the Hawaiʻi index isn't a quality judgment — it just means a site isn't based here, even if it publishes content about the islands. Every domain we've excluded, and the reason, is public.
Found something that doesn't add up?
Read the indexing guidelines, or tell us directly — we read everything that comes in.