VOSU — Vote or Shut Up
Member Zone
PRIVACY

Your politics are yours. We built the product that way.

This is not a legal shield written to be unreadable. It is a plain inventory of every piece of data VOSU touches, why it exists, and how to get rid of it.

Last updated 2 November 2026
THE SHORT VERSION
01
Browsing needs no account
Searching a ZIP, reading races, and comparing candidate records require no sign-in. With no account, nothing about you is stored in our database — your ZIP stays in your own browser.
02
Nothing is sold or brokered
No data sales, no data sharing for marketing, no advertising networks, and no third-party analytics or tracking pixels anywhere on this site.
03
Your answers are locked and encrypted
A signed-in member’s Clear-the-Fog answers are stored encrypted, readable back only by that member, and deleted 30 days after they were last analyzed. The short phrases you confirm from them are kept, unencrypted, in a row only you can read. The database enforces it row by row, not the app politely asking.
04
Identifiers are stripped before analysis
Before your answers are analyzed — and again when you edit a phrase before confirming it — links, emails, phone numbers, ID-like number runs, and street addresses are replaced with placeholders. The audit log keeps a fingerprint of the text, never the text itself.
WHAT WE NEVER DO
  • Sell, rent, or broker your data. Not to campaigns, not to parties, not to data brokers, not to advertisers — at any price.
  • Build a political profile of you. Your answers personalize how your own ballot is ordered. They are not used to target, score, or segment you.
  • Run ad or analytics trackers. There is no advertising SDK, no third-party analytics, and no tracking pixel in this application.
  • Nudge your vote. No persuasive copy, no psychological targeting. Any urgency you see in the product refers to a real, verifiable deadline.
  • Store a password. Sign-in is handled by Google, Apple, or a one-time emailed link. We never see or hold a password.
WHAT WE STORE

Everything VOSU holds, in five groups.

1. When you browse without an account

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.

2. When you create an account

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.

3. Clear the Fog (the reflection questions)

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.

4. Cohorts, War Rooms, and notifications

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.

5. Corrections and ballot lists you send

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.
WHO ELSE SEES IT

Six processors, each with one job.

VOSU shares data with service providers that operate part of the platform, and with nobody else. Each is listed with the only thing it receives.

Supabase — database, authentication, file storage, analysis
Holds the account and cohort data described above, and runs the Clear-the-Fog analysis.
Cloudflare — hosting and edge delivery
Serves the site and caches election lookups. Processes standard request logs.
BallotReady / CivicEngine — ballot data
Receives the ZIP you search in order to return the races on that ballot.
Google Civic Information API — voting logistics
Receives the ZIP you search in order to return polling places, drop boxes, early-vote sites, and deadlines.
Firebase Cloud Messaging — push delivery
Only if you opt in. Receives the device token and the notification content.
Google or Apple — sign-in
Only if you choose that sign-in method. They confirm your identity to us; they learn that you signed in to VOSU.
One more disclosure, stated plainly
We would disclose data if compelled by valid legal process. We have built the product so there is as little as possible to compel: no browsing profile, no political scoring, no ad-tech exhaust, reflection answers that are encrypted and deleted after 30 days, and audit records that hold fingerprints instead of text.
COOKIES & LOCAL STORAGE

Eight keys, no advertising cookies.

VOSU sets no advertising or cross-site tracking cookies. What it does use:

Session cookie (Supabase Auth)
Set only after you sign in, and refreshed as you navigate so your session does not drop. Signing out clears it. Without it, staying signed in is impossible.
vosu-country
Cookie. The country you picked, so the site opens on the right flag and postcode format. Cleared on sign-out.
vosu-lang
Cookie. The language you picked, so pages arrive in it. Cleared on sign-out.
vosu-state
Local storage. Your working state — ZIP, tracked items, notes, screen state — so a refresh does not lose your place. Never your Clear-the-Fog answers. Wiped on sign-out.
vosu-fog-draft
Session storage (this tab only). Your Clear-the-Fog answers while you type them, so a refresh does not lose them. Gone when the tab closes, and wiped on finishing or signing out.
vosu-last-user
Local storage. Records which account the local cache belongs to, so switching accounts on a shared device wipes the previous person’s state instead of showing it to you.
vosu-theme
Local storage. Whether you chose the light or dark theme. Nothing else.
vosu-install-dismissed
Local storage. When you last dismissed the “install the app” prompt, so it waits 14 days before asking again. Nothing else.
YOUR CONTROLS

What you can do right now.

01
Browse without an account
The strongest control is the default: no sign-in means no server-side record of you.
02
Sign out to wipe local state
Signing out clears the session cookie and erases the local cache from the device, including your ZIP, tracked races, notes and any Clear-the-Fog answers in progress.
03
Rewrite, replace, or stop personalizing
Re-run Clear the Fog from Settings at any time; the new answers replace the old ones. Once you have confirmed priorities, “Stop personalizing” appears under Civic priorities in Settings: it turns the ordering off and deletes the confirmed phrases without deleting your account.
04
Leave a cohort
Leaving removes your membership immediately, which ends your access to that cohort’s War Room and its members’ view of you as a member.
05
Turn off reminders and notifications
Switch election reminders off in Settings, or revoke notification permission in your browser or OS and delivery stops. Signing out removes this device’s token from your account.
06
Get a copy, or get deleted
In Settings, under Your data, “Download my data” saves a copy of everything your account holds, and “Delete my account” deletes it. You can also email team@voteorshutup.org from your account address for either.
RETENTION & DELETION

What is gone, and what honestly is not.

When your account is deleted, everything that is personally yours goes with it: your profile, your reflection answers, your tracked ballots, your notes, your cohort memberships, and your stored notification tokens are removed by the database itself. Even while you keep your account, your encrypted reflection answers are deleted 30 days after they were last analyzed.

Three things survive, and you should know about them before you sign up:

Your cohort’s shared record stays with the cohort — without your name
Tasks, logged signature counts, activity entries, photos, and Black Book research contributed to a group remain part of that group’s work, but the link to you is severed: the contribution no longer resolves to any account. A twelve-week sprint cannot be silently rewritten by one member leaving.
Audit entries remain, de-identified
The analysis log and the record of personalized orderings keep their fingerprints, categories, postcodes and outputs — the record that makes the neutrality claim verifiable — but the account reference is cleared, so an entry no longer points to you.
Corrections you sent stay in the record — without your name
A correction you sent stays in the moderation record, and an approved one stays in the public change log, but the link to your account is cleared.
Uploaded files are deleted after review
A ballot list you upload is deleted once a moderator decides on it. The record of the upload (file name, ZIP code, source, decision) stays; if you delete your account, the link to it is cleared.
HOW IT IS PROTECTED

The mechanisms, not the adjectives.

01
Row-level security on every user table
Access is enforced in the database. A request without your session cannot read your rows even if the application layer is wrong.
02
Cohort data gated by membership
Tasks, signature logs, activity, photos, and Black Book records are readable only by members of that cohort, checked server-side on every query.
03
Private files, short-lived links
Uploaded photos live in a private bucket and are reachable only through expiring signed URLs issued to members.
04
Append-only audit logs
Update, delete, and truncate privileges on the audit logs are revoked for application roles and blocked by database triggers. They can be added to, not edited.
05
Redaction and encryption
Personal identifiers are stripped from reflection text before it is analyzed, the stored answers are encrypted, and the audit log keeps only a keyed fingerprint. Over-redaction is accepted; leakage is not.
06
No password to steal
Authentication is delegated to Google, Apple, or a one-time emailed link. There is no password database here to breach.
CHILDREN, CHANGES & CONTACT

Children

VOSU is built for voters and for people preparing to vote. It is not directed to children under 13, and we do not knowingly collect their information. If you believe a child has created an account, write to us and we will remove it.

Changes to this page

When the product changes what it stores, this page changes in the same release, and the date at the top moves. Material changes to how existing data is used will be announced in the app, not quietly edited in.

Contact

Questions, data requests, and deletion requests go to team@voteorshutup.org. If you are writing about an account, send it from that account’s email address so we can verify the request without asking you for more personal information.

Email team@voteorshutup.orgFind your elections

Related: how the platform is built and the Mission Lock that binds it, including the zero-knowledge privacy and immutable-audit clauses this page implements.