Why Virginia is unavailable today
Virginia limits voter-list recipients to classes authorized by state law. The required statement under Va. Code § 24.2-407 says the recipient will not permit list use or copying by a person who is not authorized, with false-statement penalties. We have not found a hosted-processor carve-out that would let VoterFile receive or copy the protected list.
Sources: Virginia Department of Elections — voter-list client services
What would need to change
Support requires written Virginia Department of Elections authorization for the processor relationship, a revised statement with an agent carve-out, or a product design in which VoterFile never receives or copies the protected list.
- Written source-agency authorization or a clear statutory processor path
- A file-handling design that honors the state's recipient limits
- Updated onboarding terms and a verified first-file workflow before launch
What you can do now
Do not upload a Virginia voter file to VoterFile or send one by email. Review the supported-state directory for other campaign work, or contact the issuing office directly if you want to ask whether it will authorize a named private processor.
Need voter-file software in another state?
Compare the 45 currently supported states plus Washington, DC (46 jurisdictions). This state remains unavailable under the present hosted-processor model.
Questions
Can I bring my own Virginia voter file?
Not today. Customer ownership of the file does not override a recipient or access restriction, so VoterFile will not accept the upload without a confirmed processor path.
Can VoterFile obtain the file instead?
No. A separate provider request does not cure the current recipient limits or create a confirmed lawful path to deliver or process the file for the customer.
How will I know if support opens?
This page and the by-state directory will be updated only after the source-agency path, contract terms, file handling, and first-file validation are complete.