Production boundaries that exist today
The public site is meant for product education, search discovery, and waitlist conversion. Private product, dashboard, and operations routes are handled differently in production so campaign work does not become a public web experience by accident.
That split matters because the public marketing layer should be crawlable, while campaign workflows, admin views, and export paths should not be open to search engines or casual visitors.
- Public marketing pages stay indexable
- Private product and operations routes stay gated in production
- Search indexing is blocked on private app paths
- Admin and export routes are not treated as public product pages
- No public voter-lookup or public export workflow
Access review happens before file handling
CA Voter is intended for qualified California campaigns, committees, consultants, candidates, and political users whose intended use fits permitted voter-registration use cases. Access review happens before onboarding because qualification matters as much as product setup.
That review is meant to tie access to the campaign, role, race, and intended workflow rather than opening a generic self-serve signup with no screening.
- Human review before workspace access
- Role, race, and campaign context matter
- Permitted-use fit matters before onboarding
- The source voter file remains the campaign's responsibility
Data-handling boundaries and export responsibility
CA Voter is not a voter-file reseller and is not positioned as a general marketing database. Campaigns bring voter data they are qualified to use, and the product helps them filter, review, and export that data for campaign work.
Once data is exported, the campaign or qualified user remains responsible for how that file is stored, shared, retained, and used downstream. Export is an operational boundary, not a transfer of compliance responsibility back to the product.
- Campaigns provide the source file they are authorized to use
- CA Voter is not a public data resale or lookup tool
- Exports leave the in-product control boundary
- Downstream storage and sharing remain the campaign's responsibility
Retention and support expectations
Waitlist and onboarding information should be retained only as long as needed to review fit, operate the beta, follow up with the campaign, and maintain necessary operational records. The point is to keep enough context to run the service, not to accumulate unrelated contact data indefinitely.
Campaign contacts can ask for waitlist or onboarding information to be removed through CA Voter contact channels. When support is involved, the expectation is to avoid unnecessary long-lived copies and keep handling tied to the campaign task that actually needs attention.
Practical security roadmap
The right security posture for this kind of product is not marketing theater. It is a set of practical controls that reduce avoidable mistakes while keeping the workflow usable for campaign operators on real deadlines.
That roadmap includes stronger audit history, export logging, role-based access, file refresh tracking, and clearer retention controls as the beta expands.
Need security and access answers before joining?
Review the trust pages, then use the waitlist to start a human follow-up on campaign fit, access review, and current beta workflow boundaries.
Questions
Is CA Voter a public voter lookup site?
No. The public site explains the product. Private campaign workflows are gated for qualified political use.
Who is responsible for exported voter data?
The campaign or qualified user remains responsible for how exported voter data is used, shared, retained, and secured after export.
How are private routes treated in production?
Private product, dashboard, and operations routes are gated in production and blocked from search indexing so they are not exposed like public marketing pages.
Does access review happen before voter data is loaded?
Yes. The private beta is reviewed before onboarding because campaign fit and permitted use matter before any file-handling workflow starts.
Can campaigns request deletion of waitlist or onboarding information?
Yes. Campaign contacts can ask for waitlist or onboarding information to be removed through CA Voter contact channels, subject to any operational or legal recordkeeping needs.