Privacy

This page describes exactly what this site collects. Nothing here is aspirational or a template — it matches how the site is actually built.

What we do not do

We do not use advertising or cross-site tracking scripts of any kind. We do not sell personal data. The only third parties that receive usage data from this site are Google Analytics and Ahrefs Web Analytics (Ahrefs Pte. Ltd., Singapore). Without your say-so Google Analytics receives a cookieless count only (see below), Ahrefs sets no cookies at all (see below), and we set no cookies.

Analytics cookie (only if you accept)

A banner asks whether we may use an analytics cookie. Before you decide, and if you decline or ignore the banner, the page sends Google Analytics a cookieless measurement request: no cookie is set and no identifier is stored on your device. Like any request to a web server, Google receives the page address, device details and IP address. If you accept, Google Analytics 4 also sets its analytics cookies (_ga, _ga_HRP6VQWGF6) and tells us how people use the site: which pages are viewed and how visitors arrive. Google processes this data for us. Ad storage, ad personalisation and sharing data for ads stay switched off. The event beacon and the server-side signal described below work either way. You can change your choice at any time with the "Change your cookie choice" button at the foot of this page; declining removes the analytics cookies.

Ahrefs Web Analytics

We also use Ahrefs Web Analytics (Ahrefs Pte. Ltd.) to count visits and see which pages are read and where visitors come from. It sends the page address, page title, referrer, screen size and language. It also records which links you click (the link address) and which forms you submit (the form's target address, not what you typed), and it counts a new page view when you move between pages without a full reload. Ahrefs receives your IP address and browser details as with any web request. It sets no cookies and stores nothing on your device, and it runs for all visitors, whatever you choose on the analytics banner. It does not honour Global Privacy Control or Do Not Track, so those signals do not switch it off. Pages whose address carries a private link or credential (a token, login or account link, for example) do not load it. Ahrefs is based in Singapore and, under its privacy policy, stores this data in the United States, relying on Standard Contractual Clauses for transfers from the EU.

First-party event beacon

Pages on this site load a small (under 1 KB) inline script that reports a handful of interaction events directly to our own server, with no cookie attached: operator_impression, cta_click, table_sort, filter_use and search. Each event carries only: an event name, a page id (which page it happened on), and, where relevant, a placement id (which component or slot on the page) and an operator id. Nothing about you as an individual is included — no IP address is stored against the event, no device fingerprint, no identifier that follows you across visits.

Clicking through to an operator

Links to an operator's site go through /go/[operator]/ on our domain first. That route logs a click record before redirecting you: a randomly generated click id, the time, the operator id, a campaign id (only when a tracked commercial relationship applies — see how we make money), a placement id, a page id, and the path (not the full URL) of the page you clicked from, if any. This route is excluded from search indexing.

Server-side page-view analytics

Separately from the event beacon above, our server itself records a basic page-view signal for most page loads, so we have an accurate visit count even for visitors who block scripts or cookies. No cookie is set and nothing is stored against your identity: your IP address and browser user agent are immediately reduced to a short pseudonymous hash that changes every calendar day (UTC); we never store the IP address or user agent themselves. We keep the raw form of this signal (page path, referring site, hashed device signals) for 90 days, after which it is either deleted or folded into aggregate counts (for example, "visits per page per day") with no per-visitor detail retained.

You can opt out of this signal without changing any setting on our site: if your browser sends the Global Privacy Control signal (Sec-GPC: 1) or Do Not Track (DNT: 1), we do not record it at all for that visit. We also never record it for /go/ exits (covered separately above), known automated/bot traffic, or requests that are not a real page view (for example, a page-transition prefetch).

Server logs

Like any web server, our hosting infrastructure keeps standard server-level access logs (for example, request timestamps and status codes) for operational and security purposes. These are not linked to the event or click data described above.

Contact

Questions about this policy: partners@avenmarkmedia.com — see contact.

Related: about us, how we make money, editorial policy.