Legal & About › Privacy Policy
Privacy Policy Version 1.1.0
If you read nothing else, read this. It is accurate on its own. The sections below are more specific, and where they are more specific they govern.
You type your address in once. We use it to work out which districts you live in, and then it is gone — never written to our database, not in a log, not in a backup, not on your phone. There is no record of it to breach, subpoena, or sell, because there is no record of it.
We delete your coordinates too. Your address becomes a latitude and longitude in memory for a moment, only to derive two coarse area labels, and those coordinates are never stored anywhere.
We keep the answer, not the address. What survives is which districts you are in. A congressional district holds around 760,000 people. Knowing which one you are in does not tell anyone where you live — which is exactly why we keep that and delete the rest.
| What | Why it exists |
|---|---|
| Your phone number | It is your account. There is no password to keep instead. |
| Your districts | Determines which representatives are yours. Without it there is no product. |
| Two coarse area labels | Lets us describe an area in aggregate without holding a location |
| The five issues you pick, and where you stand | Your score is a comparison between these and voting records |
| Scores we compute | The thing you came for |
| Subscription status | To know whether you have Pro, and to honour a purchase you made |
| A notification token | Only if you turn notifications on |
| An email address | Only if you give us one |
| A random install ID | In the iOS app, to learn how many people who start signing up finish. The website creates no lasting identifier. |
| Usage events | To find where the app is broken |
Everything is encrypted in transit. Data is encrypted at rest at the storage-volume level. Access is controlled at the database, so your information is reachable only by your own account.
What we do not have: your issue positions are not protected by field-level encryption. They are stored as ordinary readable values behind those access controls. Our own engineering requirements list field-level encryption as something we should build, and we have not built it. We would rather tell you that than describe a protection we do not have.
When you tap a representative's phone number, we record which representative. It is a tap on a published public number, not a message — but the record exists, and someone with full access to our systems could connect it to the fact that you drafted a message in the same session. We do not do that and we do not publish it. We are also not going to tell you it is impossible.
Deleting your account removes almost everything, but not quite everything. Section 16 names exactly what outlives it, and why.
Part One
You enter a street address once, when you sign up, and again only if you move. Here is exactly what happens to it, in the order it happens.
Your street address is never written to our database. Not in a table, not in a column, not encrypted and filed, not in a log, not in a backup, and not in the app's storage on your phone or in your browser's storage.
It exists only in the memory of a single request. We read it, we work out which districts it falls in, and it is discarded when that request ends — seconds later.
Your coordinates are treated the same way. The address is briefly converted to a latitude and longitude in memory, purely to compute the two coarse area labels in Section 5. Those coordinates are never stored, never sent back to the app, and never written to any log.
One consequence, and it is a real cost to us. Because the address is gone, we cannot go back to it. If we later need finer geography, or a district boundary is redrawn, we have to ask you again. It is captured at sign-up or not at all. We accept that trade because the alternative is keeping the thing you would least want us to keep.
Deleting it is not the same as nobody ever seeing it, and we would rather be precise than let the sentence above do more work than it should.
Three companies receive your address while it is being converted, because they are what does the converting. None is given your name, phone number, email, or account number — only the address text.
Google (Places) receives what you type as you type it. In the iOS app, it is sent from your phone directly to Google. The address field offers autocomplete, and to do that it sends the partial address every 300 milliseconds once you have typed three characters. So a series of progressively longer pieces of your address reaches Google during a single entry, not one finished string. Because the request leaves your device rather than our servers, Google also sees your device's IP address. On the website, the same partial text is relayed to Google through our servers, so Google does not see your IP address. We attach no account identifier, and we neither request nor receive coordinates from this service.
Geocodio receives the completed address from our servers and returns your districts.
Google (Civic Information) receives the completed address from our servers and returns civic information such as polling places and registration links.
What those three do with your address afterwards is governed by their terms, not ours. We can tell you what we do, and we do not keep it.
Address entry happens before the screen where you accept this policy. So the transmissions above occur before you accept. No political preference data is collected before you accept — the issue screens come afterwards — but we would rather tell you the real order than imply a different one.
We do not collect your name, your date of birth, your party registration, your voter file record, your contacts, your photos or camera, your precise location, any biometric data, or any health, financial, or employment information.
There is no advertising in Citizen. No ads, no ad software, no ad network, no advertising identifier. We do not use Apple's advertising identifier, and neither the app nor the website asks for tracking permission, because there is nothing to track for.
There is no third-party analytics or tracking software in the app or on the website. Our usage measurement is entirely first-party. A third-party analytics component that once existed in our codebase was removed, and reintroducing one would require changing this policy first.
On the website we use first-party cookies and your browser's storage only to keep you signed in, remember that you passed the age check, and hold a usage-session identifier that ends when you close the tab. None is used for advertising or shared with third parties.
We do not sell your personal information. Not to data brokers, not to researchers, not to anyone. There is no export mechanism in the product that could do it — this is not only a commitment; the machinery does not exist.
We do not share your information with any political party, candidate, campaign, or political committee. We take no money from any of them.
We never send a message for you. Citizen can draft one, but it is handed to your own email app or the official contact form, and you send it yourself.
We never send anything identifying you to an AI company. No name, phone number, email, address, or account number goes to xAI, OpenAI, or Anthropic, and nothing links two requests to the same person.
There is no Face ID or Touch ID sign-in. Earlier materials described one. It does not exist and this policy does not claim it.
Part Two
Everything here exists because the product cannot work without it. Where something is optional, it says so.
Citizen Scorecard LLC is a Texas domestic limited liability company. This policy covers the Citizen iOS app and the website at citizenscorecard.com. Citizen is available in the United States only, for people 18 or older.
Contact: support@citizenscorecard.com
Citizen has no password and no username. You sign in with your phone number and a six-digit code, which expires after 90 seconds.
Why we keep it: it is your account. There is no other identifier, and no password we could store instead.
We use it to sign you in and for nothing else. We do not text you marketing, and we do not share it. We use Twilio to send the code; Twilio receives your phone number and nothing else.
This section describes what is left after your address is deleted. None of it is your address, and none of it is a location. It is a set of labels for areas you are inside.
Why we keep them. Districts determine which representatives are yours and are the basis of your score. Without them there is no product. The two coarse labels let us produce area-level figures without holding a location.
Why none of this is your address. A district is not a place you are — it is a region you are inside, shared with a great many people. A congressional district holds roughly 760,000. The grid cell and block group are smaller but still shared, and neither converts back into a street.
What we will not claim. We are not going to tell you these make you impossible to identify. A block group plus a legislative district plus your issue positions is a combination whose re-identifiability is an empirical question, not a settled fact. What we can tell you is what we deliberately do not hold: the address, the coordinates, and anything finer than the labels above.
You choose five issues from twelve and set your position on each on a five-point scale. The twelve are: Economy & Inflation, Immigration, Healthcare, Government Spending, Crime & Public Safety, Abortion Policy, Gun Policy, Energy, Climate & Environment, Military & Foreign Policy, Housing, and Education.
Why we keep them: your score is a comparison between these and voting records. There is no version of the product without them.
These are the most sensitive information Citizen holds, and we treat them accordingly:
From your positions and your representatives' recorded votes we compute an overall score, a score per issue, a score per representative and term, and a history of how they moved.
Why we keep them: they are the product.
How AI does and does not enter this. The formula is fixed arithmetic containing no model. It consumes a value that AI produced — which way each bill leans — so AI shapes an input to your score without computing your score. Both halves are true and neither is complete alone.
The formula is mirror-symmetric in the bill's position: if a bill is classified wrongly, two users holding exactly opposite views move by the same amount in opposite directions. A classification error makes a score less accurate; it cannot make our scores favour one side. Full detail is in our AI Use and Methodology Disclosure.
Citizen Pro is sold through Apple in the iOS app and through Stripe on the website. We never see your card; Apple and Stripe process payment and do not give it to us.
Why we keep it: to know whether you have Pro, and to honour a purchase you already made.
We store your subscription tier, when it expires, the Apple or Stripe transaction and customer identifiers needed to validate and restore purchases, and a ledger of your AI action allowance and any query packs. Purchase records are kept as long as we need them for tax and accounting. Refunds for App Store purchases are handled by Apple; refunds for website purchases are handled by us through Stripe.
Only if you turn them on. Your device gives us a push token, which we store.
The push token goes to Expo, which operates the push service we use, and Expo passes the notification to Apple for delivery. Earlier materials described Google Firebase; that is a legacy name in our own database, not the service in use. There is no Android delivery path at launch. The website does not send push notifications; notifications appear in your inbox when you sign in.
We store notifications we have sent so they appear in your inbox, and we record whether one was opened. We measure open rate as opened divided by dispatched — Apple cannot tell us whether something was seen, and we will not describe it as though it could.
Optional, and offered after sign-up. It is used for two things:
Earlier versions of this policy said the optional email was for account recovery only. That was wrong, and the Daily Brief is not a minor nudge — it contains personalised civic content about you.
Sending it requires a separate, recorded opt-in. Holding your address is not enough; our system checks for a consent record and will not send without one.
Your address and the brief's contents go to Resend, our email delivery service. This was not previously disclosed and should have been.
An unconfirmed email address is never written to our database.
Turning it off. Every brief carries an unsubscribe link. That link does one thing: it turns off the Daily Brief switch in your settings. You can turn it back on in the app or on the website. It does not delete your address or change anything else about your account.
We measure app usage ourselves. There is no third-party analytics software and no advertising software in Citizen.
Why we do it: to find where sign-up breaks, which features go unused, and whether a notification was worth interrupting someone for.
This begins the first time you open the app, before you have an account. In the iOS app, on first launch the app creates a random identifier — an install ID — and stores it on your device. From that moment we record a small set of events: the app was opened, a session ended, a link was followed, which sign-up step you reached, and whether the age gate was passed or failed. These carry the install ID and a timestamp and are not connected to any account, because no account exists yet. If you later create an account, the install ID is attached so we can tell how many people who begin sign-up finish. The website creates no lasting identifier; it uses a session identifier held in your browser that ends when you close the tab.
The install ID is ours alone. It is not Apple's advertising identifier, it is never shared, and it is not used for advertising.
Once you have an account we record a fixed, published list of about forty event types — screens opened, bills viewed and followed, searches run, notifications opened, paywall views, sign-up steps. Each event type has a declared list of permitted fields, and anything else is discarded when the event is recorded, including free text.
What we deliberately do not record, enforced by that mechanism rather than by policy alone:
One thing we will not overstate. When you tap a representative's phone number or contact link, we do record which representative — a tap on a published public contact detail, not a message. Because those records and drafting records share a session identifier, someone with full access to our database could connect them and work out which representatives you contacted. We do not do that, we do not publish it, and aggregate figures suppress any group smaller than 25 people. But that is a limit on what we publish, not on what is stored, and an earlier version of this policy described it as though the connection could not be made. It can.
Turning it off. Settings has a switch that stops usage measurement. It is honoured on our servers, not just in the app, and it applies to both the account and pre-account paths.
Part Three
| Company | What it receives, and why |
|---|---|
| Supabase | Everything we store; our servers, database and logs run there. Hosting and infrastructure. |
| Twilio | Your phone number. To send your sign-in code. |
| Google (Places) | Partial street address as you type, and your device IP. Address autocomplete. |
| Geocodio | Your street address, once. To determine your districts. |
| Google (Civic Information) | Your street address, once; or city and state. Polling places and civic information. |
| xAI | Your search question; your scores, priority issues, representatives' names and match scores; when drafting, the issue or bill, your stated position, and the words you write. AI search and message drafting. |
| OpenAI | Your search question, and bill text. Converts text into search vectors. |
| Anthropic | Bill text only. Nothing about you. Independent audit of bill classification. |
| Resend | Your email address and your Daily Brief. Email delivery. |
| Expo | Your push token and the notification text. Push delivery. |
| Apple | Notification delivery; purchase receipts and transaction identifiers. Delivery and App Store purchases. |
| Stripe | Your email address if you have given us one, your Citizen account identifier, and the payment details you enter on Stripe's checkout page. Website subscription billing. |
| Vercel | Standard request data, such as your IP address and browser type, in its request logs. Serving the website. |
None of these receives your name, your address as stored data, or your account number, except as stated.
Sentry. Earlier versions of this policy said an error-reporting service called Sentry receives technical error reports from the app. That is not accurate. The software is present as a dependency but has never been switched on; it has no configuration and receives nothing. Error reporting in the released app is currently inactive.
Companies that receive nothing about you. LegiScan, OpenStates, the Congressional Bioguide, and state legislature websites supply us with bills, votes, and information about legislators. We read from them and send them nothing about any user. They are credited in our Data Sources and Attribution page rather than listed here.
Part Four
In transit: everything between your phone and our servers is encrypted.
At rest: data is encrypted at the storage-volume level by our hosting provider.
Access: every table containing your data is restricted to your own account by rules enforced at the database itself, not by application code that could be bypassed. Access to production systems is restricted.
What we do not have. Your issue positions are not protected by field-level encryption. They are stored as ordinary readable values behind the access controls above. Our own product requirements list field-level encryption of political preference data as a requirement, and it has not been built. We would rather say so than describe a protection we do not have.
No absolute guarantees. No system is perfectly secure. We have described what we do rather than promising an outcome, because a promise you cannot check is worth less than a description you can.
We use it carefully, and in two places it does not yet apply.
Genuinely aggregate and non-identifying: the usage rollups in Section 11, which carry no account identifier, no install ID and no entity reference, and which suppress any group below 25 people.
Designed to be non-identifying, but not proven: the two coarse area labels in Section 5. We designed them to be too coarse to point at a household. We have not proved they cannot be combined with other information to narrow you down, and we are not going to claim we have.
Not yet anonymous, and we are fixing it: the record of your issue positions that survives account deletion, described in Section 16. It carries no account identifier, but as currently built we could internally link those records back to a deleted account. That is a defect, it is scoped for repair, and until it is repaired we will not call that record anonymous.
| What | How long |
|---|---|
| Your account and everything attached | While your account exists |
| Raw app usage events | 365 days, deleted by removing whole monthly storage blocks. Because deletion happens a block at a time, an individual record may persist up to roughly one further month — a maximum of about 13 months |
| Aggregate usage figures with no identifiers | Indefinitely |
| Records of events that failed validation | 30 days |
| Guardrail records (Section 16) | 12 months |
| Purchase records | As long as we need them for tax and accounting |
At our AI vendors. None of the three uses what we send to train their models. Each keeps a short record for abuse monitoring: Anthropic deletes within 30 days; xAI stores requests and responses encrypted for 30 days; OpenAI retains abuse-monitoring logs for up to 30 days. Content any of them flags as a policy violation may be kept longer.
You can delete your account from Settings by typing DELETE. It cannot be undone.
We remove your account record, your issue positions, your scores, your followed bills, your notifications and settings, your push token, your cached civic information, your subscription record, your share records, and your app usage events. We revoke your sign-in credentials and end all your sessions. We complete this within 30 days.
Deletion is not total, and here is exactly what outlives it.
1. A record of your issue positions, without your account identifier. Before deletion we copy your positions — the issue, your position, whether it was a priority, your districts, and the month — into a separate record used only for area-level figures.
We have to be honest about a limitation here. That record carries no account identifier, but as currently built we could internally link it back to your deleted account. Only our own systems could do that, and we do not — but it means we will not describe this record as anonymous until we have changed it, which we are doing.
2. A record that a message draft or search was blocked by our election-law guardrail, including your account identifier, kept for 12 months and then deleted. These exist to evidence that the guardrail worked, which is their entire purpose. This applies to both the search guardrail and the drafting guardrail.
3. Any error report you submitted, with your account identifier removed. The report itself survives, including any free text you typed into it.
4. Aggregate figures that contain no identifier of any kind and cannot be traced to you.
Part Five
Today, and at launch:
What we may do in future. We may offer area-level figures — how a district's residents lean on an issue — to researchers and institutions. If we ever do, these commitments bind it:
Citizen produces a personalised result about you automatically: your score, which representatives and bills you see, and which notifications you receive. The arithmetic is fixed, applies identically to every user, and contains no AI model. The bill classifications it consumes are AI-generated.
You are not subject to any decision with a legal or similarly significant effect. Citizen decides nothing about your rights, your eligibility for anything, or your access to any service. It tells you how your representatives' recorded votes compare with the positions you chose.
Citizen is for adults. Both the app and the website ask you to confirm you are 18 or older before sign-up, and you cannot proceed if you say no. The App Store rates Citizen 17+. We do not knowingly collect information from anyone under 18, and we delete it if we learn we have.
One correction. Earlier materials said no data is collected before the age gate. That is not accurate: the install identifier described in Section 11 is created when the app first launches, an app-opened event is recorded at that moment, and the age gate itself records whether it was passed or failed — including the under-18 outcome. Those records carry the install ID and a timestamp and are connected to no account and no identity. We record the under-18 outcome so we know how often it happens, which is itself a compliance measure. We would rather describe it than claim a cleaner story.
Everyone, in the app or on the website: change or remove your issue positions, change your address (which recomputes your districts), turn usage measurement off, turn notifications and the Daily Brief off, and delete your account.
If you live in California, you have the right to know what we collect and to receive a copy, to correct it, to delete it, to opt out of sale or sharing, to limit our use of sensitive personal information, and not to be treated differently for exercising any of these.
If you live in Texas, you have the right to confirm whether we process your personal data and to access it, to correct it, to delete it, to obtain a portable copy, and to opt out of targeted advertising, sale, and profiling in furtherance of decisions producing legal or similarly significant effects. You also have the right to appeal a refusal of any of these requests. We will respond to an appeal in writing within 60 days and, if we deny it, tell you how to complain to the Texas Attorney General.
Do Not Sell or Share. We do not sell or share your personal information, so there is no opt-out for us to offer you. If that ever changes, we will build one and tell you before the change takes effect.
How to exercise these rights. Deletion is self-service in Settings. For anything else, contact us at the address in Section 3. We will verify your request against your phone number, since that is the only identifier we hold.
If personal information is exposed in a way that creates a risk to you, we will notify affected users and the regulators we are required to notify, without unreasonable delay and within the deadlines the law sets.
When we change this policy materially we will update the version number and the date below, and tell you in the app.
One thing we cannot yet do. We display the version of this policy at sign-up, but we do not currently record which version you accepted. We are adding that, and when it is in place this section will say so.
Citizen Scorecard LLC
support@citizenscorecard.com
citizenscorecard.com
If you gave us your email on our launch page before Citizen opened, we still hold that address together with the options you ticked — beta program, App Store notification — and use it only to send you what you asked for. It is not tied to any account, it is never sold or shared, and there is no other list it feeds. Write to support@citizenscorecard.com at any time and we will delete it.
Citizen Scorecard LLC · Privacy Policy · Version 1.1.0