What we collect — and what we don't
PoliAgg is a static site with no accounts, no logins, and no server-side tracking. The data on the site is public-record polling and election data, not user data. The third-party scripts we load (analytics, ads, error tracking) do collect their own data — this page lists exactly which ones, what they capture, and how to opt out.
Nothing automatically. The site is delivered as static HTML / CSS / JSON from Cloudflare's CDN — there is no database lookup at request time, no user account system, no comments, no email signups, and no session tracking. Simply browsing the site stores no personal data on our end, and every page is identical for every visitor.
The one exception is the contact form. If you choose to usethe contact form, the name, email address, and message you enter are sent to a Cloudflare Pages serverless function and emailed to us via Resend (our email provider) so we can reply. We don't store submissions in a database — they live in our inbox and Resend's sending logs. Please don't include sensitive information you wouldn't otherwise email us.
The only piece of "data about you" that PoliAgg's own infrastructure handles is your IP address, which Cloudflare sees in order to route the request and apply DDoS / WAF protection. Cloudflare's logs are retained for routing and security purposes only and are not exported into any analytics or marketing system on our end.
PoliAgg loads scripts from third-party services for analytics, monetization, and error tracking. Each operates under its own privacy policy. The table below lists what we run and what each one captures.
- Google Analytics 4PurposePage-view counts, traffic sources, organic-search query data via Search Console.CapturesAnonymized IP, device type, browser, page paths, referrer. Sets analytics cookies, which load by default for all visitors (see “Cookies” below).
- Google AdSensePurposeServes contextual ads. Currently no ads serve until the application is approved.CapturesCookies for ad personalization, IP, ad-interaction events. Subject to Google's ad policies for personalized advertising.Opt outGoogle Ad Settings — turn off personalized ads.
- Cloudflare Web AnalyticsPurposeReal-user monitoring of Core Web Vitals (LCP / INP / CLS) + page views.CapturesAggregated, no cookies, no fingerprinting. Cloudflare commits to GDPR-compliant data handling without consent.Opt outBlock
static.cloudflareinsights.comin your ad blocker; there is no cookie to clear. - SentryPurposeCaptures unhandled JavaScript errors and stack traces so we can fix bugs.CapturesConfigured with
sendDefaultPii: false— no IPs, no request headers. Just the error message, stack trace, and the URL where it happened.Opt outBlockingest.us.sentry.ioin your browser. There is no persistent identifier we can offer you to opt out from.
Fonts (Source Serif 4, JetBrains Mono) are self-hosted from our own CDN, so loading them sends no request and no IP address to Google or any third-party font service.
PoliAgg itself does not set cookies. Some third-party scripts do (Google Analytics, and Google AdSense once ads are approved); these are listed in the table above. We do not currently display a region-specific consent banner — analytics loads by default for all visitors. Under Google Consent Mode v2 the ad-targeting signals (ad_storage,ad_user_data, ad_personalization) are denied by default, while analytics storage is granted. A consent banner with region-gated, deny-by-default behavior is planned before personalized ads are enabled; until then, EU / UK / EEA visitors who wish to opt out should use the per-service opt-outs listed above.
You can clear all PoliAgg-related cookies via your browser's site settings panel, or block the analytics/ad scripts in your browser to prevent them being set.
- GDPR (EU / UK / EEA) — you have the right to access, correct, and delete personal data we hold about you, plus the right to data portability. Aside from any message you send us through the contact form (which you can ask us to delete at the email below), PoliAgg holds no personal data on its own infrastructure (see “What PoliAgg directly collects” above), so these rights are primarily exercised against the third parties listed in the table above. Each one's privacy policy explains how.
- CCPA (California) — you have the right to know what personal information is collected, to delete it, and to opt out of "sale" or "sharing." PoliAgg does not sell or share personal information directly. AdSense's data may be considered "shared" under CCPA when ads ship; once that's live, a "Do Not Sell or Share My Personal Information" link will appear in the footer.
- Contact — the email below is the right place to reach us with privacy questions.
The site is not directed at children under 13 and we do not knowingly collect data from children. If you believe a child has used the site in a way that might have triggered third- party data collection, contact us via the email below and we'll work with the relevant providers to remove it.
Material changes are versioned in this file's git history. The "Last updated" date at the top reflects the most recent change. For substantive changes (a new tracker, a new data-collection surface, a regulatory shift), the previous version stays accessible via the repository atgithub.com/PositronicAI/poliagg.
Privacy questions, opt-out requests, or compliance disclosures:privacy@poliagg.com
For security-specific reports (vulnerabilities, suspected breach, abuse): security@poliagg.com