Data sources

Data sources behind VoterFile.

VoterFile is not a voter-file reseller. Campaigns bring data they are permitted to use, and the product combines that campaign input with public reference datasets and product metadata needed to make the workflow usable.

Written by Jose Lopez, Founder and managing member, Lopez Labs LLCSources reviewed Official source

Request California access review Review California requirements

California voter-data upload, import, and activation are hard-stopped until the customer, source, viewers, agency acceptance, notice/security handoff, and security evidence are approved. Do not upload or email a voter file with this request.

California access review firstNo file upload while activation is closedOfficial fields only after approval
California access review is required before upload.

The platform activation bundle is available, but each campaign still requires customer, source, viewer, permitted-use, and workspace approval before voter data can be uploaded or opened.

Request California access review
Modeled signals are implemented, but not generally activated.

California workspaces default to raw official-file fields only. BISG and turnout-derived voter-level output may be opened only in a separately approved modeled-output lane after source, legal, validation, customer, workspace, and output-scope review. These pages document methods and limitations; they do not promise that a model is active for a customer.

Primary campaign input

The main campaign input is the California voter file obtained by a qualified requester through the appropriate source process. VoterFile is designed to organize, filter, and export approved raw fields once lawful access is verified; modeled scoring is not generally activated and requires a separate modeled-output approval.

Refresh timing matters. The product is designed to keep the voter-data workflow aware of when the underlying file was obtained and whether the campaign should update it.

Sources: California Secretary of State voter-file request process

Public reference datasets

Some workflows rely on public reference datasets such as Census surname tabulations, district or geography reference data, and demographic context that help campaigns interpret a segment more carefully.

These reference datasets are used to support explainable planning signals and list-building context. They do not turn the product into a hidden commercial enrichment system.

  • California voter-file source records provided by the campaign
  • Public surname and demographic reference data
  • Geographic and district context for campaign targeting
  • Product metadata for refresh, review, and export workflows

Sources: U.S. Census Bureau 2010 surname tabulations

Campaign and product metadata

VoterFile also stores operational metadata needed to run the service, such as access-request information, product analytics, and administrative details tied to onboarding and support.

That metadata is kept separate from the idea of selling voter records. Its purpose is product operation, not unrelated commercial reuse.

What VoterFile does not claim

The product does not claim to know how someone voted, whether a voter supports a candidate, or that a modeled demographic signal is the same as self-reported identity.

VoterFile is designed to help campaigns reason about outreach and segmentation, not to make unsupported claims about individual voters.

California access status

Complete California access review before any file upload.

Submit the campaign, requester, issuing source, viewer list, geography, and intended use. VoterFile does not open upload, import, browse, export, or voter-level modeled output until the California activation checklist is complete.

Human eligibility reviewAgency and viewer coverageActivation required before upload
Request California access reviewReview California requirements

Questions

Does VoterFile include a California voter file subscription?

No. Campaigns bring voter data they are qualified to use. VoterFile organizes and analyzes that data for campaign workflows.

Can campaigns load refreshed files later?

Yes. The workflow is designed around the reality that campaign voter data needs periodic refresh and review.

Explore more

Compare county coverage, contest types, and campaign workflows through the pages below.

MethodologyMethodology behind VoterFile filters and signals.Learn how VoterFile handles California voter-file filtering, turnout ranking, modeled outreach signals, and exportable campaign lists.Permitted UsePermitted use comes before any voter-file workflow.See who VoterFile is for, how BYO and data-included state workflows differ, and which campaign voter-data uses are excluded.SecuritySecurity controls and honest boundaries for campaign voter data.Review VoterFile authentication, access control, encryption, audit logging, retention, incident response, and current security limitations.PrivacyPrivacy and data handling for campaign teams.VoterFile privacy overview for national access requests, BYO and data-included campaign workspaces, analytics, payments, and voter-file handling.

Source links