Your ZIP and working state — in your browser only
Kept in this browser’s local storage so the app remembers where you were. Not sent to our database and not attached to any identifier. Clearing site data erases it completely.
Your ZIP — sent out to look up races
When you search, the ZIP goes to our election API and on to the data providers that answer it (BallotReady/CivicEngine for races, the Google Civic Information API for polling places and deadlines). Results are cached at the edge for up to an hour. The ZIP is not stored against a person.
An email for a launch notice — only if you ask
If you ask to be told when VOSU goes live in a coming-soon country, we store that email address and the country, and nothing else. It is used only to send that one notice, it can’t be read back through the site, and a country’s addresses are deleted once its notice has gone out.
Standard delivery logs
Like every website, our host processes request metadata (IP address, timestamp, page requested) to serve pages and block abuse. We do not join that to an account or use it for profiling.
Sign-in identity
Google or Apple sign-in returns your email address and, if the provider supplies it, your name. A magic link stores only the email address you typed. Authentication is handled by Supabase Auth.
Your profile
A display name; your country and language; the last postcode you entered and any you saved; whether you want election reminders; and your role (member or moderator). Readable and writable by you alone, except the role, which only an administrator can set.
Ballots you track
Which races you are tracking, their research status (needs research, researched, undecided), and when to remind you about each. Yours alone.
Your ballot notes
The private research notes you write on a race. Yours alone — sharing to a cohort copies only an excerpt you pick, never the note itself.
Your answers while you type — this tab only
Kept in this browser tab’s session storage so a refresh doesn’t lose them. Not encrypted on the device, never written to longer-lived storage, and gone when you close the tab, finish, or sign out.
Your two answers — encrypted, for 30 days
Once you send them for analysis they are stored encrypted (AES-256-GCM) with a key held by our analysis function, not stored in the database, so a copy of the database alone can’t read them. They are kept only so you can pick up where you left off, only you can load them back, and they are deleted automatically 30 days after they were last analyzed.
The phrases quoted back to you — kept until replaced
The one or two short phrases quoted from your answers, and the ones you confirm (in your own words, never a category label), are stored with the matching priority so your races can be ordered by them. They come from the redacted text, and if you edit one, your edit gets the same redaction before it is saved. They are not encrypted and are readable by you alone. The suggestions are replaced by your next analysis; the confirmed phrases stay until you choose “Stop personalizing”, confirm new ones, or delete your account.
The analysis itself
Runs inside our own infrastructure on a built-in embedding model — there is no third-party AI vendor and no external AI API involved. Before it runs, links, email addresses, phone numbers, ID-like digit runs, and street addresses are stripped from the text and replaced with placeholders.
An append-only audit record
For accountability, every analysis writes one entry: a keyed fingerprint of the redacted text (not the text) and its length, the model and method identifiers, the categories and confidence returned, fingerprints of the phrases picked, how long the analysis took, a timestamp, and success or failure. You can read your own entries; no client can edit or delete any entry, by design. This is what makes the neutrality claim auditable rather than promised.
A record of each personalized ordering
When your confirmed priorities reorder your races, one entry records the inputs — your postcode, your country and the categories you confirmed, never your words — the data source, the template version, and which offices were connected, so any ordering can be explained later. Append-only, and readable by you alone.
What fellow members can see
Joining a cohort is a social act. Your display name, the tasks you own, the signature counts you log, your activity entries, photos you post to the wall, and Black Book records you add are visible to that cohort’s members — and to nobody outside it.
What you share into a cohort
A race you share, or an excerpt you pick from your notes, is visible to that cohort’s members. With a private link, anyone holding the link sees the race, its election date and the excerpt — not who shared it, and not from which cohort.
Photo wall
Photos live in a private storage bucket. They are served through short-lived signed links that only a member of that cohort can obtain. They are not public and not indexable.
Meeting attendance
A per-cohort count, used only to unlock the Black Book at three meetings attended.
Push notifications (opt-in)
If you enable them, a device token from Firebase Cloud Messaging is stored on your own row so the platform can notify you about deadlines, cohort activity and — while reminders are on in Settings — the day before an election you saved. Revoking notification permission in your browser or OS stops delivery immediately, and signing out removes the device's token from your account.
Your correction and its source
What you wrote, the official source link, and your account reference — so a moderator can check it and so the daily limits work. The moderation queue shows the submission, not who sent it.
The public change log
If a moderator approves your correction, what you wrote and your source appear in the public change log — never your name or account. A turned-down suggestion appears there only as the decision and the moderator’s reason.
Official ballot lists you upload
The PDF, the ZIP code it’s for, where you got it and your account reference — so a moderator can check it against its source and so the daily limit (5 a day) works. Only moderators and you can open the file, and it is deleted once a moderator publishes it or turns it down. What gets published is offices, candidate names and parties — never addresses, phone numbers or emails from the document — plus a one-line summary in the public change log, without your name.