Privacy Policy

VoterContact.io (“VoterContact,” “we”) is a voter file and field planning tool for campaigns, operated by Dan Kelly (DK Dev). This policy explains what the service collects, why, where it is stored, who processes it, and the choices you have.

Who this covers

• Campaign users: staff and administrators who sign in.
• Volunteers and event guests: people who use a public event page or a PIN-protected canvass link, or who a campaign adds to its volunteer roster.
• People in a voter file: voters whose records a campaign uploads.

Our role with voter files

A campaign is the licensee of the voter file it uploads and decides how that data is used. We host and process it on the campaign's behalf, only to provide the service. We do not use a campaign's voter file for our own purposes, sell or rent it, use it for advertising, or combine it with another campaign's data. Each campaign's data is kept separate in the database and enforced there, not only in the screens. An organization administrator sees totals across the campaigns they administer, not voter-level records from campaigns they do not administer.

Information we collect

• Account: your email address. If you sign in with Google, the email, name and profile picture Google shares for sign-in.
• Organization and campaign details: names, state, county or district, election date, and roles.
• Voter files a campaign uploads: names, addresses and map coordinates, phone numbers and types, birth year, gender, party and vote-by-mail status as given in the file, registration date, vote history, precinct and districts. From these we build households, searches, turfs, plans and results.
• Results a campaign records or imports: canvass, call and text outcomes, survey answers, notes of who did the work and when.
• Volunteers and RSVPs: name, email and phone that a campaign enters or that a person submits on an event page. For a canvass link, the name the volunteer types in.
• Files: voter files, documents, printed packets and call sheets, stored in the campaign's private storage.
• Activity log: who searched, exported, imported, printed, changed roles or deleted, and when. This protects the voter file.
• Technical records: IP address and request logs kept by our hosting and network providers for security and reliability.

Device location. The canvass link reads the phone's location to show where the volunteer is on the map. For a distributed canvass it is sent once to choose nearby doors. We do not store it.

Cookies and tracking

We use only essential cookies: your sign-in session, the campaign you have selected, and, before launch, the site's access password. We do not use advertising or analytics cookies or trackers.

How we use information

• To run the service: sign you in, show your campaign's data, cut turf, print packets, and produce results and plans.
• To send sign-in emails and respond to support requests.
• To keep the service secure and investigate misuse.
• We do not sell, rent or share personal information for advertising. California residents: we do not sell or share personal information.

Plain-English search (AI)

If you use the plain-English search box, the sentence you type, plus a summary of the values in your campaign's file (party codes with counts, precinct codes, city names, election dates and district names), is sent to Google's Gemini service to turn it into a search filter. Individual voters' names, addresses and phone numbers are not sent, and the AI never writes database queries or sees individual voter records. Google processes that text under its own terms and may review it, so please do not type personal details about individual voters into the box.

Service providers

These providers process data only to provide their part of the service:

• Supabase: database, sign-in and file storage.
• Vercel: application hosting.
• Cloudflare: domain name service and the pre-launch access gate.
• Resend: sign-in emails.
• Google: Google sign-in, and the Gemini service described above.
• OpenStreetMap: map tiles. Loading a map sends your IP address and the area you are viewing to their servers, and our server requests tiles to draw printed packet maps.
• U.S. Census Bureau Geocoder: addresses in a voter file that have no coordinates are sent to it to find their location.

Sensitive information and lawful use

Voter files can include political party and vote history, which some state laws treat as sensitive. Each campaign is responsible for having the right to upload and use its file, for following the file's license and the laws of its state, and for honoring do-not-contact and opt-out requests. Numbers on a campaign's opt-out list and voters marked do-not-contact are left out of calling and texting lists.

Retention and deletion

Data is kept until the campaign deletes it. Deleting a campaign deletes its voters, households, phone numbers, vote history, results and its stored files (voter files, documents, printed packets). A record that a campaign was deleted, with its name, the time and who did it, remains in the activity log. Copies held by our database provider in routine backups expire on the provider's schedule.

Security

Data is encrypted in transit. Files are stored privately and are available only to the campaign's own members. Database rules limit every user to their own campaigns. Canvass PINs are stored hashed and failed attempts are limited. Saved integration credentials are encrypted. No system is perfectly secure, and we cannot promise absolute security.

Your rights and choices

• Users: email dan@dkdev.io to see, correct or delete the information tied to your account.
• People in a voter file: the campaign that uploaded your record decides how it is used. Contact that campaign. If you are not sure which one, email dan@dkdev.io and we will help route the request.
• Volunteers and RSVPs: ask the campaign you signed up with, or email dan@dkdev.io.

Children

VoterContact is for campaign staff and volunteers and is not directed to people under 18.

Google user data

Google sign-in is used only to verify who you are. VoterContact's use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Changes

We may update this policy. The date above changes when we do, and we will ask you to review the data-use notice again when a change affects how data is used.

Contact

Questions about privacy: dan@dkdev.io.