Privacy Policy

Version 2026-10-22. Effective October 22, 2026.

1. WHO THIS COVERS

Voter Count is operated by IVC Media LLC ("we", "us"), in partnership with L2, Inc. ("L2"), which provides the voter data the product queries. This policy explains what we collect about the people who use Voter Count, how we use it, who we share it with, and how long we keep it.

This policy covers information about you, our user. It is not a description of L2's own privacy practices as the source of the underlying voter data. Those are published by L2 separately.

Voter Count is a professional research tool intended for use in the United States by people aged 18 or over.

2. THE SHORT VERSION

We collect the information needed to run an account: your email, your password stored only as a cryptographic hash, or your Google sign in, and your subscription status.

We store the questions you ask and the answers you receive, so your conversation history is there when you return.

Your questions are answered inside L2's own secure data environment, which the product reaches through views that exclude personally identifying columns. Your name, email and account identifier are not sent with them.

We do not train, fine tune, evaluate or benchmark any artificial intelligence model on voter registration records, and we do not send your conversations to any outside model provider for that provider to train or improve its own models. Our agreement with L2 requires both.

We do use your questions and the results returned to you to run, secure, support, debug and improve the service, which includes correcting and extending how the service interprets a question and turns it into a query, and building test cases from real examples. We may also train and test models we own and run ourselves, for the single purpose of interpreting a question and routing it to the right query, using question text with account and user identifiers removed together with aggregated patterns of use. Those models are never trained on voter registration records.

Voter Count answers in aggregate, meaning counts, segments and trends. It is not designed to return individual voters' names, phone numbers or addresses, and the data it can reach excludes those fields.

We do not sell your personal information. We do not run advertising on the product, and no advertising scripts are loaded. On our public pages and our sign up, sign in and checkout pages we use Google Analytics to understand how people find and use the site, and it sets cookies only if you accept them.

If you ask us to see, correct or delete your information, email us and we will handle it.

3. WHAT WE COLLECT

Account information.Your email address, and your name and profile image if you sign in with Google. If you use a password, we store only an Argon2id hash of it. We never store the password itself and cannot recover it. We also record when your account was created and what role it holds. If you created your account using an invitation link that another member shared with you, we record which link you redeemed, and the member who issued that link can see your account's email address and when you redeemed it, and nothing else about your account or activity. Our administrators can see the same redemption record for every invitation link, as part of the administrative access described under "Administrative records" below. If you registered directly rather than by invitation, there is no redemption record and nobody sees one.

Your conversations.The questions you type, the answers returned to you, and the supporting output for those answers, meaning the tables and charts. A conversation's title is taken from the opening words of your first question in it. This applies equally to questions sent through a connected application or AI assistant, or through an API key where API access has been provisioned, rather than through the web interface. Questions those tools send and answers they receive are stored the same way.

Consent and certification records. When you accept our Terms, consent to automatic renewal, or certify your permitted purpose under Section 5 of the Terms, we record that you did so, when, and which version you accepted, together with your browser user agent string. We keep these records for at least three years, or one year after your subscription ends, whichever is longer, because we need to be able to prove them, and we may keep them longer where a dispute, an inquiry or a legal obligation requires it.

Feedback you send us. If you rate an answer or flag it as wrong, we store that rating and any comment you write. Please do not put personal or confidential details in a feedback comment. Comments are passed on to the team that maintains the underlying data model exactly as you wrote them, and they cannot be edited or withdrawn once sent.

Billing information. If you start a trial or subscribe, our payment processor Stripe handles your payment details. We never see or store your card number. We keep your Stripe customer and subscription identifiers, your current plan status, and your token balance and usage history.

If you arrive through a partner's link.If you reach Voter Count through a link shared by one of our affiliate partners, we note which partner's link it was. If you then create an account, we keep that partner's link code with your account so the partner can be credited.

Usage records. The tokens each question consumes, your running balance, and the seats on your account. We use these to meter your plan, to bill you, and to detect abuse.

Technical information. Your IP address, used to apply rate limits and to protect sign in against automated abuse. In our database we store only a salted one way hash of an IP address, never the address itself. The address is held briefly in a rate limiting service keyed to short expiry windows. We also keep server logs of requests.

Administrative records. We keep an append only audit log of privileged actions taken inside the product, including when a member of our staff views a conversation. These records exist so that access to your data is accountable, and by design they cannot be altered or deleted.

If you ask to be put on a waiting list.Where we operate a waiting list, asking to join it stores your email address, the time you asked, your answer to one required question about the kind of work you do, chosen from a fixed list, and, if you arrived from a link for a specific plan, the name of that plan. We do not share this record with anyone outside the providers listed under "Who we share information with." If registration is open and you sign up directly, no waiting list record is created.

4. VOTER DATA, AND WHAT THIS PRODUCT DOES NOT DO

This Section describes what the service does and does not do with voter data.

Voter Count answers questions in aggregate. It reports counts, segments, distributions and trends across the voter file. It is not a lookup tool for individual people, and it is not a way to obtain a list.

Where the data lives.The voter data is L2's, and it stays in L2's own secure data environment. We do not hold a copy of it. The product reaches it through restricted views that exclude every personally identifying column, so the fields needed to identify or contact a specific voter are not present in what the product can query. That limit is enforced in the data layer, not by filtering in your browser, and the product offers no bulk export or data delivery function.

If you need licensed access to individual voter records, that is granted by L2 alone, under L2's own approval, compliance and fulfillment process. We cannot grant it.

When you ask for that access, or request a demo of L2's full offering, we pass your contact details and what you asked for to L2 so their team can follow up with you. That is the point of the handoff, and it only happens when you ask for it. See Section 6.

Availability of voter registration records, and what may lawfully be done with them, varies by state. Our Terms place responsibility for following the rules that apply to you on you, and require you to certify your permitted purpose. We make no claim here about the legal status of the underlying records.

5. HOW WE USE INFORMATION

  • To operate your account, authenticate you, and keep your conversation history available across your devices.
  • To produce answers to your questions, which requires sending the text of your questions to the data environment that answers them.
  • To meter your token usage, apply your plan's limits, and bill you.
  • To send transactional email: invitations, sign in links, email verification codes, password resets, notices when your login credentials change, subscription confirmations, renewal reminders and price change notices. We may also send occasional messages about the service itself, such as new features or changes that affect you, and every one of those carries an unsubscribe link. We do not sell or rent your address, and we do not send you third party advertising.
  • To keep the service secure and available, meaning rate limiting, abuse prevention, debugging and investigating incidents.
  • To improve the product. That includes reviewing flagged answers to correct the underlying data model, correcting and extending how the service interprets questions and turns them into queries, and building test cases from real examples.
  • To meet our legal obligations, including our record keeping obligations for consent and certification, and to enforce our Terms.

We do not train, fine tune, evaluate or benchmark any artificial intelligence model on voter registration records, and we do not send your conversations to any outside model provider for that provider to train or improve its own models. Our agreement with L2 requires both.

We do use your questions and the results returned to you to run, secure, support, debug and improve the service, which includes correcting and extending how the service interprets a question and turns it into a query, and building test cases from real examples. We may also train and test models we own and run ourselves, for the single purpose of interpreting a question and routing it to the right query, using question text with account and user identifiers removed together with aggregated patterns of use. Those models are never trained on voter registration records.

6. WHO WE SHARE INFORMATION WITH

We do not sell your personal information, and we do not share it for cross context behavioral advertising. We share it with the following categories of recipients, for the purposes described.

L2, Inc., our data partner. L2 provides the voter data the product queries and hosts it in its own environment. We report aggregate usage to L2, meaning figures such as query volumes and how many accounts are active. That reporting does not include your questions or anything that identifies you.

Separately, if you write a feedback comment about an answer, we pass that comment on as you wrote it so that the underlying data model can be corrected. A comment about a specific answer will usually describe the question it relates to. Please do not put personal or confidential details in a feedback comment.

Separately, when you request a demo or licensed access to individual voter records, we send L2 your contact details and what you asked for, so their team can respond. This happens only when you ask for it.

Compliance and enforcement. If we or L2 receive a question or complaint about how you are using the service, or if we suspend or terminate your account for a breach concerning the underlying data, we may pass your account details, your written response and the reason to L2, and to a state authority where the inquiry came from them or where the law requires it. Terms Sections 5 and 6 describe when this happens.

Snowflake, the data platform.L2's voter data is hosted on Snowflake, and the text of your questions is sent there so that the analysis producing your answer can run against it. When a conversation continues, earlier turns in that conversation may be sent again for context. These requests are authenticated as our application, not as you. Your name, email and account identifier are not included. Feedback comments you write are also sent.

Stripe, our payment processor. Receives your email address and an internal account identifier to create and manage your subscription, and handles your payment details directly.

PromoteKit, our affiliate program provider.If you created your account through a partner's link, we send PromoteKit your email address and your Stripe customer identifier so it can credit that partner.

Amazon Web Services (AWS SES), our email provider. Receives your email address and the contents of transactional messages we send you. These messages go out through a dedicated configuration set with open and click tracking turned off, so SES does not rewrite links or add a tracking pixel to them.

Google. If you choose to sign in with Google, Google authenticates you and provides us your name, email address and profile image.

Google Analytics, our site analytics provider.On our public pages, such as the home page, example answers, plans and the legal pages, and on the sign up, sign in and checkout pages, we load Google Analytics, and Google Tag Manager, Google's tool for managing such tags. It receives the address of the page you are on and of the page you came from, with questions, one time codes and other personal details removed from those addresses, together with your browser and device type and an approximate location that Google derives from your IP address. If you accept analytics cookies, it also receives an identifier stored in a cookie that lets it recognize your browser on later visits. We do not send Google Analytics your name, email address, account identifier, questions or conversations, and we do not use it inside your conversations or account pages. We have turned off Google signals, advertising features and data sharing with other Google products, and we use the reports only in aggregate, to understand and improve the site.

Stytch, our connection authorization provider. If you choose to connect an external AI assistant, such as Claude or ChatGPT, to your account, Stytch operates the authorization service that issues that assistant its access credential. Stytch receives your email address and an internal account identifier when you approve a connection. As with any web service, Stytch also sees standard connection metadata, such as your IP address, while you use its authorization pages. If you never connect an assistant, we send no information about you to Stytch.

Applications you connect. If you connect an external application or AI assistant, or use an API key in another tool, the questions you send through it and the answers it receives are handled by that tool under its own terms and privacy policy, not ours. We do not control what a connected tool does with an answer once we return it. Review the privacy practices of anything you connect.

Google Cloud Platform and Upstash, our infrastructure providers. Host the application, the database and the rate limiting service. Our primary application database is located in the United States.

Cloudflare, our domain name and redirect provider. Runs the domain name service for our web addresses, and the redirect that forwards two older addresses, www.votercount.ai and our former address chat.ivcmediallc.com, to the current one. Requests to the site itself go directly to our hosting provider and do not pass through Cloudflare. If you open a link pointing at one of those two older addresses, Cloudflare receives the address you requested, including anything carried in the link such as the one time code in a sign in, invitation or password reset link, along with your IP address and any cookies your browser sends. It does not receive your questions, your conversations or your account record.

Business tools our team uses. Our team uses standard business software, such as Google Workspace for email, documents and spreadsheets, and Slack for team messaging, to run the company: to follow new signups, answer support requests and keep business records. These tools may hold your name, email address, how and when you signed up, your plan, and anything you send us, including when you email us to exercise any of the rights described below. The providers of these tools handle that information on our behalf under their business terms.

Others when required. Professional advisers, or law enforcement and regulators where we are legally required to respond. If our business is sold or reorganized, information may transfer as part of that transaction.

7. COOKIES AND TRACKING

Apart from the analytics cookies described below, all cookies on votercount.ai are set by us. Six persist: one that keeps you signed in, one that identifies your browser before you have an account, one that remembers whether you keep the conversations sidebar collapsed, one to remember whether you were signed in with light or dark mode, one that records whether you accepted or declined analytics cookies, and one, set only if you arrive through a partner's link, that remembers which partner it was. A few short-lived cookies are set only while you sign in, redeem an invitation, or connect an AI assistant, and expire within minutes or when you close your browser. Two of those carry a session for Stytch, our connection authorization provider, during the connection step. We set no advertising cookies. When we send you to Stripe to pay, to Google to sign in, or to Stytch's authorization pages, those services set their own cookies under their own policies.

On our public pages and our sign up, sign in and checkout pages we load Google Analytics and Google Tag Manager, and on most of those pages we ask, the first time you visit, whether you accept analytics cookies. If you accept, Google Analytics sets its own cookies on votercount.ai, named _ga and _ga_ followed by an identifier, which let it recognize your browser on later visits and last up to two years. If you decline, or have not chosen yet, no analytics cookie is set, and Google receives your page visits without a cookie identifier, which can be used to estimate overall traffic. You can change your choice at any time with the Cookie settings link at the foot of our home page, at the top of this policy, or on your account page, and if your browser sends a Global Privacy Control signal we treat it as declining. We load no advertising scripts. Our fonts are served from our own servers rather than requested from a third party as you browse.

Our emails carry no tracking. Our transactional messages are sent through a dedicated configuration set with open and click tracking turned off, so links in those emails are not rewritten and no tracking pixel is added.

We do not respond to browser Do Not Track signals, because there is no common standard for how to interpret them. Nothing changes if you send one, since we are not tracking you across other sites.

8. HOW LONG WE KEEP INFORMATION

We keep your account information and conversation history for as long as your account is open, so that earlier analysis is available to you across your devices, and delete them when you close your account or ask us to.

When you close your account, we delete your account information and conversation history within a reasonable period, normally within 30 days. Deleting a single conversation in the product hides it from your history immediately. Ask us and we will remove it permanently.

Server logs are normally kept for no more than 30 days. We may keep a specific log longer where we need it to investigate a security incident or a suspected breach of these Terms, and only for as long as that takes.

Waiting list records. We keep these for as long as we have a reason to, being to tell you when access becomes available and to follow up with you about the product. In practice that means until you take up access, until you tell us you are no longer interested, until you ask us to delete it, or until we stop pursuing that list. We do not delete them on a fixed schedule, and you can have yours deleted at any time by asking us.

Three categories survive deletion of your account, because a deletable record cannot serve their purpose: the audit log of privileged actions, consent records, and the permitted purpose certifications and automatic renewal consents described in Section 3, which we are required to retain. None of them contains the content of your conversations, and the audit log holds identifiers rather than your personal details.

We may keep information longer where we need it to meet a legal, tax or accounting obligation, or to resolve a dispute.

9. YOUR CHOICES AND HOW TO EXERCISE THEM

You can update your password from your account page. You can cancel a subscription at any time from the billing portal, online, without contacting us.

To see what we hold about you, correct it, obtain a copy, or delete your account and its data, email privacy@votercount.ai. We will verify that the request comes from you, and we will respond within the time the law allows, generally 45 days, which some statutes permit us to extend where we tell you why. We will not treat you worse for exercising these rights.

We handle these requests by email rather than through a button in the product, and the email reaches a person.

Some information cannot be deleted on request. We keep records we need in order to meet legal, tax and accounting obligations, to resolve disputes, and to enforce our Terms. As noted in Section 8, audit records, consent records and certification records are retained by design.

10. STATE PRIVACY RIGHTS

Depending on where you live, you may have specific rights over your personal information: to know what is collected and why, to obtain a copy, to correct it, to delete it, to opt out of its sale or of targeted advertising, and to appeal a decision we make about a request. Residents of California, Colorado, Connecticut, Texas, Virginia and a number of other states have these rights under their own statutes.

We do not sell personal information and we do not use it for targeted advertising or profiling, so those opt outs have nothing to act on here. For everything else, use the contact route in Section 9. If we decline a request, you may ask us to reconsider by replying to our decision, and you may complain to your state attorney general.

We do not hold, store or sell voter data. It stays in L2's environment, and the product queries restricted views of it that exclude personally identifying columns and returns aggregate results only. Nothing the product returns disseminates personal information about a voter to anyone, and the voter registration records the service draws on derive from voter registration records maintained by state and local election officials, as compiled by L2. The rights described above concern your account information, which is the personal information we keep about you.

11. HOW WE PROTECT INFORMATION

Passwords are stored as Argon2id hashes. Invitation links, sign in links, password reset links, connection credentials and any API keys we issue are stored only as one way hashes, so a copy of our database does not reveal a usable credential. Session cookies are restricted to our own domain and are not readable by scripts in your browser.

Connections to the product are encrypted in transit. Our database rejects unencrypted connections, is not reachable from the public internet, and its storage is encrypted with a key we control. Access to privileged functions is checked on the server on every request, and privileged actions are recorded in the audit log described in Section 3.

The voter data itself is not held by us. It remains in L2's environment under L2's controls, and the product reaches it only through restricted views that exclude personally identifying columns.

The contents of your conversations are stored in our database, protected by encryption of the underlying storage and by access controls. No system is perfectly secure, and we cannot guarantee that a determined attacker will never succeed.

12. CHILDREN

Voter Count is not directed to children and is not intended for anyone under 18. We do not knowingly collect information from children. If you believe a child has given us information, contact us and we will delete it.

13. CHANGES TO THIS POLICY

If we make a material change we will update the version at the top of this page and, where the change affects how we use information you have already given us, we will bring it to your attention. Earlier versions are available on request.

14. CONTACT US

Privacy questions and data requests: privacy@votercount.ai. Our Terms of Service govern your use of the product.

IVC Media LLC, 2700 Adams Ave Suite 202, San Diego, CA 92116.

Allow cookies from Voter Count?

Privacy