Privacy Notice
This page is maintained by AI Race Facts to answer common privacy questions about the airacefacts.com website and newsletter.
What we collect
When you subscribe to the newsletter we store the email address you provide, the source of the signup (which form you used), the consent text you agreed to, and the timestamp of that agreement. We also collect anonymous analytics (page views, section views, link clicks, share clicks) to understand which stories are useful. Analytics events do not include your name, email, or raw IP address.
How we use it
- Sending the weekly digest you subscribed to.
- Occasional updates from AI Race Facts: new stories, site releases, supporter notes, and the rare offer.
- Aggregated analytics to decide what to write next and to fix broken pages.
We only email what is described in the consent checkbox at signup. We do not sell or share your email address.
Unsubscribing
Every newsletter email includes a one-click unsubscribe link. You can also email us to be removed from the list and to have your subscriber record deleted.
Cookies and analytics
We use Google Analytics 4 to measure traffic in aggregate. We do not use advertising cookies. Analytics on gated admin pages is suppressed so internal activity is not mixed into public metrics.
Survey responses and dedupe
When you submit a story survey (for example the Energy Bill Survey) we store your answers along with the country you selected and a random visitor ID kept in your browser. We do not store your name, email, raw IP address, or user-agent string with the response.
To keep results honest we need a way to tell whether two submissions came from the same person without keeping identifying data. We do this with salted one-way hashes:
- Your IP address is combined with a server-side secret salt and hashed. IPv6 addresses are truncated to a network prefix first. The raw IP is discarded — only the hash is stored.
- A lightweight browser fingerprint (things like screen size, timezone, and language) is also salted and hashed on the server. The raw fingerprint values are not stored.
- These hashes are only used to reject duplicate submissions within a 30-day window and to flag suspicious skew clusters for admins. They cannot be reversed back into an IP address or a device profile, and they are never exposed publicly or in analytics.
Admin dashboards show only aggregate counts (for example "3 visitors shared a network signal") — never the underlying hashes.
Contact
Questions or removal requests: reach out via the contact form on the site.