Legal

Privacy

You never need an account to read this site. An account is only for posting, saving a forecast and keeping a visiting streak. This page says exactly what is measured, what your browser stores, and what choice you have.

The short version

Maps, results and seat polls need no sign-up and no password. You create an account only if you choose to post or save a forecast. Nothing about you is sold, rented or shared with a data broker.

Visitor numbers are counted using Cloudflare Web Analytics, which is cookieless — it stores nothing on your device, cannot follow you between websites, and reports only totals. It tells us that a page was read, never who read it.

Google Analytics and Microsoft Clarity run too, and they do use cookies — you can turn them off further down this page.

A few small things are remembered by your own browser, and one unavoidable thing is recorded by the server that delivers the pages. Both are described below, because “we collect nothing” would not be strictly true and we would rather be exact than reassuring.

What your browser stores

These values are written to your browser’s own storage. None of them is sent to us, none can identify you, and you can clear them at any time through your browser’s “clear site data” control.

Your light or dark theme choice

If you switch the site to the light theme, that preference is saved locally so the page does not flash back to dark next time. If you never touch the toggle, nothing is written.

A “seen it” marker for one animation

The home page’s emblem animates once when you arrive. A single flag is kept for the length of the browser session so it does not replay every time you return. It is discarded when you close the tab.

A “seen it” marker for the forecast tour

The first time you open a forecast page, a short guided tour shows you round. Once you finish or skip it, a single flag is kept on this device so it does not start again. It stays until you clear your site data and is never sent anywhere. The “Show me how” button on the map replays the tour.

Your sign-in

The sign-in session is kept in your browser itself, together with the value bb-community-signed-in, so a returning member is recognised, and your handle as bb-community-handle, so the menu at the top of the site can show it. While a tab is open, what the service told that tab about your account (email, handle, visiting streak) is kept in the tab’s session storage as bb-community-session, so each page does not have to ask again; it is gone when the tab closes. Signing out clears all of them.

While an email sign-in link is on its way

The address you typed (bb-community-signin-email) and the page you were on (bb-community-return) are kept until the link has finished signing you in, so you can be sent back there. The address is removed when sign-in completes.

Unsent drafts

A post you started but did not send is kept in your browser as bb-community-draft:<place> (one for each discussion, seat and reply) and cleared once it is posted. It is never sent anywhere.

Your poll token and choices

The first time you vote, a random token (bb-poll-token) and your choice in each poll (bb-poll-choice:<poll>) are kept in your browser so you can change your vote. Nothing is written before you vote.

Your cookie choice

If you allow, decline or turn off cookies, that choice is remembered locally so it sticks. It is not shared with anyone.

What is measured, and by whom

Cloudflare Web Analytics

A small script reports that a page was viewed, along with the referring site, approximate country, browser and device type, and how quickly the page loaded. It sets no cookies, writes nothing to your device, and assigns you no identifier, so it cannot recognise you on a second visit or follow you to another site. We see totals — which pages are read, roughly where from — and nothing that points at a person.

Ordinary server logs

This site is delivered through Cloudflare, which sits in front of a server hosted on Oracle Cloud; the map and result data files are also served through Cloudflare. Like every web host, both record ordinary request logs — the page requested, the time, your IP address, and the browser and operating system your request announces. This is how pages get delivered and how outages and abuse are diagnosed; it happens on any website you visit and is not something this site can switch off. We do not build profiles from those logs or combine them with anything else. Cloudflare processes the logs it records as our provider, under its own privacy policy and retention schedule; the server’s own logs stay on the machine we rent from Oracle Cloud and are rotated automatically.

Fonts and map files

Everything the pages load — typefaces, map geometry, result data — is served from this same domain apart from the services described under “Accounts, posts and polls”, which are contacted only when you use them. The fonts are downloaded when the site is built rather than fetched from Google while you read.

The search box

What you type into the search box is read inside your browser to choose the page that answers it: no request is made for that reading, and the analytics event that counts which kind of page the box opened never carries the words. The words do travel in the search page’s own address (/search/?q=), as on any website: that address appears in the ordinary server logs above and, where Google Analytics is on, in the page addresses it records below, and in those Microsoft Clarity records.

Voice search is done by your browser, not by this site; in Chrome the recording goes to Google to be turned into text.

Find my seat

If you use Find my seat, your browser asks whether to share your location. If you allow it, the location is used only inside your browser to work out which seat you are in. It is not sent to us or anyone else, and it is not saved. To do this, your browser downloads the seat maps for the whole country and for your state, the same files the map pages load. Coordinates you type in instead are handled the same way.

Your state on the Delimitation page

The Delimitation page uses the approximate region of your connection, worked out by Cloudflare from your IP address, to open on your state. The page does not save it (no cookie, storage, address or history) and sends it nowhere else, apart from showing it on your screen, which the Clarity recording described below can capture. The request that asks for it is recorded, with that region, in the ordinary server logs described above.

Short share links

When you open Share on a forecast you have changed, your browser asks this site for a short version of its link (even if you then close the menu without sharing). The short link is made on this site’s own server and is not sent to any other service, and no copy of it is kept when it is made. It is the same settings you chose, including any names you typed, packed into a shorter form rather than looked up. Opening it takes you to the full-length page, whose address holds those settings and is recorded like any other page address: in the ordinary server logs above and, where Google Analytics is on, in the page addresses it records below, and in those Microsoft Clarity records. If a short link cannot be made, the full-length link is shared instead. When a short link is pasted into a chat or a post, the app that receives it fetches the link, and this site draws the preview picture under it on the spot from the settings in the link: it shows the swing you set and the seats that gives. Like any image, that picture may be kept for a while in caches, here and in the app that receives it; no other copy is made.

Accounts, posts and polls

What an account keeps

Your sign-in id and email address (so you can sign in, and so we can reach you about your account), the handle you choose, your posts, your saved forecasts, and the day you last visited while signed in. We do not keep your name, phone number, birth date or location. You confirm that you are 18 or older, and the time you confirmed is kept. Posts are public and show your handle.

Signing in

Sign-in is run by Google. When you tap Sign in, your browser contacts Google and, for the Google option, accounts.google.com. Nothing is contacted before you tap, unless this browser was already signed in here.

Your data

Account records are kept until you delete the account. On your profile page you can download everything we hold (export) or delete the account. Deleting it removes your forecasts, your profile and everything you wrote in your posts; each post leaves only an empty “deleted” marker, so the replies other people wrote to it can still be read. Your handle then stays reserved for 90 days so nobody else can take it over.

A saved forecast you mark public is shown with your handle on your profile and, once the result is in, its score on the prediction leaderboard. A private forecast is never shown to anyone; on the leaderboard it only counts towards the number of entries, without a name.

If the account is banned when you delete it, a scrambled (hashed) form of your email address is kept for as long as the ban lasts, so the ban still applies to a new account made with the same email. The address itself is not kept, the scrambled form is never shown, and it is deleted when the ban ends or is lifted.

Seat polls

Voting in a seat poll needs no sign-in. A vote is stored with a random token kept in your browser (so you can change your vote) and a scrambled, hashed form of your address that is deleted after 24 hours. A vote is never linked to an account. To block automated voting, Cloudflare’s Turnstile check runs when you tap Vote; it is a third party, contacted only then.

Complaints and removal requests

To complain about a post or ask for one to be removed, write to hello@billionballots.com.

Analytics and your account

The analytics tools never receive your account id or handle. Session recording does not run on your profile or the sign-in page, and what you type into the post box is hidden from it.

Cookies, Google Analytics and Microsoft Clarity

This site uses Google Analytics, which sets cookies to count visits and see which pages are read — roughly where from, on what device, and how you arrived. How Google uses information from sites or apps that use its services.

It also uses Microsoft Clarity, which records how pages are used — where people click, tap and scroll, and a replay of what was on screen — so that confusing or broken parts can be found and fixed. It sets two cookies (_clck and _clsk) and sends what it records to Microsoft. Text you type into a box is masked and not sent. It does not run on the Find my seat page. How Microsoft uses information collected by its services.

Visitors in Europe are asked first. You can turn them off or change your choice here:

Advertising

No advertising runs on this site today. Ads from Google AdSense may be added later to help pay for hosting. If they are, they will load only if you allow them: you will be asked first, and this section will be updated in the same release.

Once advertising is switched on, this is how it works:

Third-party vendors, including Google, use cookies to serve ads based on your previous visits to this website or to other websites. Google's use of advertising cookies lets it and its partners serve ads to you based on your visits to this site and/or other sites on the internet.

You can opt out of personalised advertising in Google's Ads Settings. You can also opt out of some other vendors' use of cookies for personalised advertising at www.aboutads.info.

Sharing, changes and contact

Nothing is sold, rented or shared with a data broker or a marketing list. Your email address is never shown to anyone, posted, or used for marketing.

If what is measured ever changes, this page is updated in the same release as the change — an automated check fails the build if a tracking script appears on the site without being described here, so the two cannot quietly drift apart. The date below is the last time this text was reviewed.

Questions, or a request to have something explained, go to hello@billionballots.com. See also the terms of use and the data sources and credits.

Last updated 14 November 2026