What's kept for a vote
- The question, the note for voters, the choices, how people vote, the closing time and when the vote was set up.
- Names the organiser types in for personal links. Only the organiser's page shows them.
- For each personal link, whether it has been used. Not when.
- For an open link, a scrambled copy of a random token your browser makes, so the same browser can't vote twice. It isn't stored with your ballot.
- Each ballot: the choices marked (in order, for a ranked vote) and a random code. Your name, your link, the time and your network address aren't saved with it.
Who sees what
Anyone with the voting link sees the question and the choices, and after voting closes, the result and every ballot. When a vote uses personal links, the organiser also sees who has voted. Nobody sees a count before voting closes, the organiser included.
In a vote with only a few ballots, the result itself can give away how people voted. With two voters, each can work out the other's ballot.
Database history
Cloudflare keeps 30 days of database history so it can be restored after a fault. Someone with access to the account that runs Ballot could use that history to see the order ballots arrived in and, for a vote with personal links, line it up with who voted when. Organisers don't have that access.
On your device
Your browser keeps the random token, your ballot codes, your personal link and the organiser links for votes you set up, in local storage. Clearing your browser data removes them. There are no cookies.
How long
A vote and everything in it is deleted 90 days after voting closes. The organiser can delete it sooner.
Network addresses
Cloudflare counts requests from each address for a minute at a time, to stop floods. Addresses aren't written to the database.
Analytics
Cloudflare Web Analytics counts page views without cookies.
Where it runs
Ballot runs on Cloudflare's servers.