M2V Privacy Policy
Effective August 25, 2026, updated September 17, 2026 (added the "How we count use" section) · Match2Vote ("M2V") · match2vote@gmail.com
Who we are
Match2Vote (M2V) is an independent, nonpartisan voter guide developed and published by Kiki Taylor, an independent developer based in Connecticut, who is the developer of record on Google Play and the person responsible for this app and for the data described on this page. Match2Vote is not affiliated with, endorsed by, or acting for any government agency, election office, political party, or campaign. Privacy questions and requests: match2vote@gmail.com.
What the app collects
Nothing that identifies you. M2V does not ask for your name, email address, phone number, precise location, contacts, or any account sign-in. There is no advertising SDK, no analytics SDK, and no third-party tracking of any kind in the app. The only usage figure we keep is how many devices open the web version each day, described in "How we count use" below.
The state code you can choose to send
If your state has no researched races yet, the app shows a button like "I want M2V to cover Missouri." Tapping it sends exactly one thing to our database: the two-letter state code (for example, "MO"). The database records that code and the time it arrived. That is the entire record. No IP address is stored in it, no device identifier, no user identifier, no session identifier, and no user agent. The write-only key the app uses cannot read the table back. This happens only when you tap the button, never automatically, and the app remembers on your device that you tapped so it will not ask again. We use these counts for one purpose: deciding which states get expanded coverage first.
How we count use
We want to know roughly how many people use M2V, and we do it without tracking anyone. When you open the web version at app.match2vote.org, the app sends exactly two things to our database: the word "web", and a yes or no for whether this device has ever been counted before. The database records those two things and the time they arrived. That is the entire record. No IP address is stored in it, no cookie is set, and there is no device identifier, user identifier, session identifier, user agent, page, or state. The app remembers on your device that it has already counted today, so it sends at most one record per device per day, and nothing at all can connect one day's record to the next. The write-only key the app uses cannot read the table back. We use these counts for two purposes: knowing how many devices opened the web app each day, and how many of them were opening it for the first time. The Android app does not send this record; for Android we rely only on the install and usage statistics that Google Play shows every developer, which Google collects under Google's privacy policy.
What stays on your device
Everything you do in the app is stored only in the app's local storage on your own device: the state you select as your ballot state, your quiz answers and which issues you mark as mattering most, the candidates you mark on your sample ballot, and your display preferences (like dark mode). We cannot see any of it. Deleting the app deletes all of it. If you use the share or export features, the image is generated on your device and goes only where you choose to send it.
What the app downloads
On launch, M2V downloads the public candidate database for the state you selected (names, races, sourced policy positions) from our server so the information can be updated between elections without an app update. The request names that state so the server can return the right data; it carries no other information about you. This is a one-way download of public data. The request works like any web request: our hosting provider (Supabase) transiently processes your device's IP address to deliver the data, as every internet service must, and keeps short-lived operational request logs like every hosting provider. We do not store IP addresses in our database, and we do not use logs to analyze or identify anyone. No information about you, your answers, or your choices is uploaded. After the first load, the app works offline from its cached copy.
What we never do
We never sell data. We never share data with third parties for marketing. We never build profiles of users. We cannot connect any quiz answer or ballot choice to any person, because that information never reaches us. Match results are computed entirely on your device.
Data retention and deletion
State-code records (the two-letter code and the time it arrived) and open counts (the word "web", a first-time yes or no, and the time they arrived) are the only records the app can create about its use. They are kept as aggregate counts until the November 3, 2026 election has been certified and are then deleted. Because these records contain nothing that identifies you or your device, there is no record of you for us to look up or delete on request; if you email us anyway, we will confirm this. Everything else the app stores lives only on your device and is deleted when you delete the app. Our hosting provider's operational request logs are retained by the provider for a short period (days, not months) and are not exported or analyzed by us.
Children
M2V is an election-information tool intended for people old enough to vote or preparing to vote. It collects no personal information from anyone, including children.
Ratings
On Android, the app may once ask whether you would like to rate it, and the About screen has a "Rate M2V on Google Play" button. Both use Google Play's own review dialog or listing, which are operated by Google under Google's privacy policy. M2V receives nothing from that dialog and does not know whether you rated the app. The app only remembers, on your device, that it has already asked, so it never asks again.
Email contact
If you email us (match2vote@gmail.com) to report an error, we receive whatever you choose to include in your email and use it only to fix the issue. We do not add you to any list.
Changes
If the app's behavior ever changes in a way that affects this policy (for example, adding crash reporting), we will update this page first and note the change in the app's store listing before shipping it.