What this site is
PoliVion is built from plain HTML, CSS, and JavaScript files — no server-side code, no database, no content management system. Every page you visit is a pre-built file served as-is. There is no login system, no comment section, no newsletter signup, and no payment processing. There is nothing here to hack into, because there is nowhere to log in and nothing stored about you.
What we collect: nothing
The district finder (“Find your district”) runs entirely in your browser — your town or ZIP search never leaves your device. The “Where do you vote?” preference is saved in your browser’s own local storage, not sent to us. The one exception: the district finder’s map background tiles load from CartoDB’s tile servers (standard map imagery) — your location is never transmitted, because the search happens against data files on polivion.com, not against your GPS.
Outbound links (like the Vote.org voter-registration buttons) simply take you to those sites — this site doesn’t track whether you click them.
Who builds it — and who has access
PoliVion is built and run by an independent creator working with Muse — an AI assistant by Meta — which writes the code, researches the data, and maintains the pages. Every editorial decision is the creator’s; Muse does the building.
Muse publishes site updates over encrypted connections, and only ever with the site owner’s explicit go-ahead for each update. That access is limited to this site alone — it can’t reach anything else on the hosting account.
One thing our host adds
Our hosting provider appends its own performance-monitoring script to every page as it’s served. That code is theirs, not ours — it isn’t in our files, and it reports to them, not to us. Their own notice on the snippet says you can opt out by contacting web hosting support. (We’re asking our hosting provider to remove it, and we’ll update this page when they do.) We disclose it here because “no trackers” should mean no surprises.
Checked every day
PoliVion’s data is refreshed by a daily automated audit — and part of that audit verifies the live site itself. Every day it fetches key pages and compares them against the known-good deployment, and scans for any script that shouldn’t be there. If a file were ever altered or injected on the server, the next day’s check would flag it — so tampering can’t sit unnoticed.
Deliberate, not accidental
None of this is secure by accident. We’re fully aware of what’s out there — from phone-hijacking spyware like Pegasus that can take over a device without a single tap, to the everyday compromises baked into the modern web. That’s exactly why this site is built the way it is: the less it holds, the less there is to take, and the less there is that could ever be turned against the people reading it.
This information matters, and getting it shouldn’t require trusting us blindly. We aim to give you the most secure experience we can — so you never have to wonder whether the site itself is trustworthy.
The honest limits
No one can promise a website is unhackable, so here’s the plain version of what we can and can’t verify:
- We can verify everything about the site itself: the code is static, there’s no database to breach, no credentials stored anywhere, and every deployment is checked file-by-file.
- We can’t audit the hosting company’s servers themselves — polivion.com runs on shared hosting, like most small sites. What we can say is that even a compromised server would find nothing here: no user data, no passwords, no payment info — because none of it exists.
- We can’t vouch for the hundreds of campaign and other external websites this site links to. We verify that each link goes to the right candidate’s real site before publishing it — but we have no control over how those sites are built or secured, so browse them with the usual care.
The site’s simplicity is its security model. The less a site holds, the less there is to take.
Keep reading
How this project works.