← Live scorecard
Legal

Privacy policy

Last updated: August 6, 2026

This page explains what data agiscorecard.com collects and how it is used. The short version: this is a static informational site with no accounts, no comments, and no data sold to anyone.

Analytics

Google Analytics 4

We use Google Analytics 4 to understand aggregate traffic — which pages are visited, roughly where visitors come from, and which site features are used. GA4 sets cookies and collects pseudonymous usage data (such as page views, approximate location at city level, and device type). We do not use this data to identify individuals. You can opt out with the Google Analytics opt-out browser add-on or by blocking analytics cookies in your browser.

First-party log (added August 5, 2026)

Alongside GA4, and not instead of it, the site keeps its own small log so that the public experiment results on /experiments can be reported from numbers we control rather than from a third-party dashboard. It is stored in a Cloudflare D1 database owned by this site and has two parts.

Page counts, recorded at the server. When this site's Cloudflare Worker serves a page, it adds one to a counter for that day, page path, referring site's hostname, country, campaign tag, and whether the request looked like a bot. That is the whole record: a tally, not a log of visits. No JavaScript is involved, so — unlike the parts below — a content blocker does not switch it off.

Interaction events, recorded from the page. A short script mirrors the same interaction events GA4 already receives (for example: which subscribe button was clicked, which quiz answer was picked) to /api/e on this domain, with the page path, referring hostname, country, browser language and any campaign tag. Only a fixed list of event names is accepted; anything else is discarded on arrival. Blocking JavaScript, or any content blocker that blocks /api/e, prevents this part.

Sets no cookie and stores no identifier. Neither part stores a cookie, a session ID, a device fingerprint, an IP address, or anything that links one visit to another. (The one exception on this whole site is an email address you type into a subscribe form yourself — see Newsletter below.) Referring sites are stored as a hostname only, never the full referring URL, which can carry query strings that identify people; of the query string on our own pages, only utm_source, utm_medium and utm_campaign are read. Rows cannot be traced back to a person, which also means we cannot single out and delete "your" rows — there is nothing there to identify.

Newsletter

The email briefing is operated on beehiiv. If you subscribe, your email address is stored by beehiiv and used solely to send the newsletter; every issue includes a one-click unsubscribe link. See beehiiv's privacy policy for details of their processing.

Signing up on this site (added August 6, 2026)

Subscribe buttons used to send you to a form on beehiiv.com. You can now enter your address without leaving the page, so this site itself receives and stores your email address — that is a real change from the position described above, and it is the only personal data anywhere in this policy.

Stored with the address: which button you used and, where it applies, which prediction's alert you asked for (so a "tell me if this verdict flips" signup can actually be honoured), the page you signed up from, your browser language, a two-letter country code from Cloudflare's edge, the referring site's hostname, and any campaign tag in the link. No password, no account, no profile — there is nothing to log in to.

It is used to send you the briefing and the alerts you asked for, and for nothing else. It is not sold, rented, or shared with anyone beyond beehiiv, which sends the mail. Where beehiiv is connected, the address is passed to it immediately and you get a confirmation mail; where it is not, the address waits in our database until it is imported, and the page says so rather than promising a mail that will not arrive.

Getting it removed. Every issue has a one-click unsubscribe. To have the address deleted from this site's own database as well, reply to any issue and ask — deletion means deletion, including the signup record described above.

Hosting

The site is served via Cloudflare, which may process standard technical request data (IP addresses, request logs) to deliver and secure the site, per Cloudflare's privacy policy.

Advertising

The site currently shows no advertising. If that changes, this policy will be updated first, and any advertising partner's required disclosures will be added here before ads are served.

Your rights

Depending on your jurisdiction (e.g. GDPR, CCPA), you may have rights to access or delete personal data. For newsletter data, use the unsubscribe link or contact beehiiv. GA4 data is pseudonymous; blocking cookies prevents collection going forward. The first-party log holds no identifier at all, so there is no record tied to you to retrieve or erase. Blocking JavaScript or /api/e stops the interaction events being written; the server-side page counter is a per-day tally with nothing personal in it and is not blockable, which is stated here rather than glossed over.

Contact

Questions about this policy: reply to any issue of the email briefing.