Privacy notice

The script sends events to /api/collect on this site: a page view, how far down the page you scrolled, a tap on an App Store link, a visit to a page that does not exist, and the summary sent when you leave a page. Each event can store:

• Time: when it happened.
• Date: the date (UTC), used for daily totals.
• Event: the kind of event: a page view, how far down the page you scrolled, a tap on an App Store link, a visit to a page that does not exist, or the summary sent when you leave a page.
• Page: the address of the page on this site, without anything after a "?".
• Referring page: the address of the page that linked here, if your browser shares it. Most sites, search engines included, share only their domain.
• Referring site: the domain of that page, such as google.com.
• Country: the country your connection comes from, as determined by Cloudflare.
• Device type: phone, tablet, or computer, worked out from your browser's user-agent string. The string itself is not stored.
• Daily visitor code: a one-way hash of your IP address, your browser's user-agent string, and a random value that is replaced every day (UTC). It lets us count unique visitors per day; it can't be turned back into an IP address, and the same visitor gets a different code the next day.
• Scroll depth: how far down the page you scrolled (25, 50, 75, or 100 percent).
• Link type: which kind of link you tapped, such as an App Store link.
• Event details: extra details about the event, such as where on the page a tapped link sits and the address it opens.
• Page-load number: a random number created for each page load and never saved in your browser, used to group the records of one page view.
• Page type: home page, guide, guide list, or error page.
• Traffic source: a category such as search, AI assistant, social, campaign, or direct, worked out from the referring site and campaign tags.
• Campaign source: the utm_source (or src/ref) tag of the link that brought you here, if it had one.
• Campaign medium: the utm_medium tag of that link, if it had one.
• Campaign name: the utm_campaign tag of that link, if it had one.
• Ad-click marker: which ad network, if any, added a click identifier to the link you followed. The identifier itself is not stored.
• Linking page on this site: for pages that do not exist: the page on this site that linked to them, so broken links can be fixed.
• Network number: the number of the network your connection comes from, such as your internet provider, used to filter out traffic from data centers.
• Network name: the name of that network, such as your internet provider or a data-center operator.
• Browser family: such as Safari on iOS or Chrome on a computer (not the full user-agent string).
• Automation flag: whether the visit looked automated, and why.

When you leave a page, the script also sends one summary of that page view: how you engaged with it and how fast it loaded. Each summary can store:

• Date: the date (UTC), used for daily totals.
• Page-load number: a random number created for each page load and never saved in your browser, used to group the records of one page view.
• Time: when it happened.
• Page: the address of the page on this site, without anything after a "?".
• Page type: home page, guide, guide list, or error page.
• Device type: phone, tablet, or computer, worked out from your browser's user-agent string. The string itself is not stored.
• Daily visitor code: a one-way hash of your IP address, your browser's user-agent string, and a random value that is replaced every day (UTC). It lets us count unique visitors per day; it can't be turned back into an IP address, and the same visitor gets a different code the next day.
• Automation flag: whether the visit looked automated, and why.
• Update counter: lets a later summary of the same page view replace an earlier one.
• Time on page: how long the page was open and in the foreground.
• Time visible: how long the page was on screen.
• Furthest scroll: how far down the page you got, in percent.
• Reached the end: whether the end of the article came into view.
• Saw the answer: whether the short answer at the top of a guide came into view.
• App Store links seen: which of the page's App Store links came into view.
• Main content load time: how long the largest text or image took to appear (Largest Contentful Paint, a Core Web Vitals measure).
• Main content element: which kind of element that was, such as a heading or an image.
• Layout stability: how much the layout moved while the page loaded (Cumulative Layout Shift).
• Responsiveness: how quickly the page responded to taps and clicks (Interaction to Next Paint).
• First content: how long until the first text or image appeared.
• Server response: how long the site's server took to start answering.
• How the page opened: a new visit, a reload, or back/forward.
• Connection class: your browser's estimate of the connection, such as 4G or 3G.