Privacy Policy

Last updated: May 15, 2026

Election Countdown collects information to operate the countdown experience, account features, vote-intent tools, analytics, and fraud/security protections. Political preference information can be sensitive. Do not submit information you do not want processed by this site.

Information We Collect

Account information such as email address, name, session records, and verification status.
Vote-intent information you submit, including support choice, state, optional city, age range, sex, and custom candidate field where available.
Change history when you update support, state, or related vote-intent fields.
Usage events such as page views, countdown changes, dwell time, visibility changes, heartbeats, CTA clicks, Vote.gov clicks, and share/referral interactions.
Technical data such as user agent, referrer, viewport size, timezone, and a hashed IP-derived identifier for security and abuse detection.

How We Use Information

We use the information to run the service, save your submitted intent, show your profile, measure countdown engagement, detect abuse, improve the product, and provide admin analytics/export tools.

Public Results and Segments

Public vote breakdowns remain hidden until the configured participation threshold is met. State and age segment analytics are hidden until each segment has enough records to reduce small-group exposure.

Cookies and Local Storage

The site uses an HttpOnly session cookie for sign-in. It also stores a random visitor identifier in the browser to support analytics. Vote intent and account records are stored by the backend, not browser-only storage.

Sharing

Admin export tools can include account and vote-intent data. Do not publish raw exports. We do not sell user data from this launch package.

Your Choices

You can avoid submitting optional demographic fields. Signed-in users may request account deletion through the backend account deletion endpoint. Deleted accounts remove account, session, vote-intent, history, verification, donation, and user-linked tracking records.

Security

The service uses hashed passwords, HttpOnly session cookies, D1-backed server persistence, no-store API responses, and privacy thresholds for public analytics. No system is perfect, so sensitive exports should be tightly controlled.

Contact

Use the contact path provided by the site owner for deletion, export, or privacy questions.