See the visitors other analytics miss.

The VeritaMetrics Fix

Our loader is about ~7KB and starts the moment your page does, so it never holds things up. It counts every interaction from the first click, with no cookies and no consent banner of our own. We don't record private data. For the rare visitor with JavaScript switched off, a 43-byte pixel still records the page view on our servers.

Both of our headline figures, the ~30% of traffic recovered and the ~99.5% of interactions captured, are estimates worked out from the loss rates above. Neither has been independently audited.

{ /* Answers the second objection raised in "The Compliance Trap" above, that European authorities have challenged sending EU data to a US company. The first objection (cookies and consent) is answered in the paragraph above. NO BACKTICKS IN THIS COMMENT. It had them, as markdown code spans around the filenames below, and prettier-plugin-astro stopped treating the whole block as a comment: it read them as template literals, swallowed the JSX after them, and then read the @ of the adapter package name as a decorator. "npx prettier --write ." died with "Leading decorators must be attached to a class declaration" at this line and took the wiggum autofix step with it. Same family as the plugin bug .prettierignore already records for src/pages/signup/check-email.astro, and cheaper to avoid than to ignore, since ignoring this file would stop formatting the most-read page on the site. THIS CLAIM DEPENDS ON A SETTING THE REPOSITORY CANNOT SEE. The Vercel function region is configured in the Vercel dashboard, not in vercel.json (which has no "regions" key) and not in the adapter options in astro.config.mjs (@astrojs/vercel 8.0.4 exposes none). Verified 1 September 2026 and re-checkable in ten seconds: curl -sI https://www.veritametrics.com/ | grep x-vercel-id The header reads edge::function::id. The SECOND segment is the function region and must be lhr1 (London); the database is separately pinned by the connection string, ep-fancy-sun-abfwnle0.eu-west-2 (also London). The first segment is the CDN edge nearest the visitor and varies, including US nodes for US visitors, which is why this sentence claims processing and storage rather than routing. Deliberately says "London", not "the EU": London is in Europe and outside the EU, and a compliance-minded reader will know the difference. */ }

Your visitors' data is processed and stored in London, not the United States.