TFS FIELDFieldStrike

Privacy Policy

Effective date: September 26, 2026

FieldStrike is a field-organizing tool that helps political campaigns manage walk lists, canvassers, and door-to-door responses. This policy explains what information we handle, why, and the choices you have.

1. Account data

When you create an account we collect your email address, your name, and a password (stored only in hashed form). If you sign in with Google, we receive your name, email, and profile identifier from Google through OAuth. We do not receive your Google password or access to other Google data.

2. Campaign data and access controls

Each campaign is its own isolated workspace. Campaign names, settings, team memberships, and join links belong to that campaign. Access is role-based — owners, admins, organizers, and canvassers each see only what their role requires, and data never crosses between campaigns.

3. Voter and door list data

Campaigns may upload voter or address lists (for example CSV or PDF exports from their voter file). The campaign that uploads a list is the controller of that data and is responsible for having the right to use it. FieldStrike processes it only to build walk lists, maps, and reports for that campaign.

4. Door responses from canvassers

Canvassers record door outcomes such as contact status, support level, issues, notes, and the time and approximate device location of each knock (used to verify the knock happened near the door). When there is no signal, responses are saved on the device in an offline queue and sent to our servers once a connection returns. Canvassers checking in through a campaign link provide a name and mobile number so the campaign can identify who walked which doors; we also record basic device and network information (such as IP address) for security and fraud prevention.

5. Maps and address lookups

To place doors on a map, addresses are sent to public geocoding services (such as the U.S. Census Bureau geocoder), and map tiles are loaded from OpenStreetMap. Directions open in a third-party maps app (Google or Apple Maps) of your choosing, which is subject to that provider's own privacy policy.

6. Integrations and automations

Campaigns can connect outside tools (for example Zapier-style automations) using a shared API key issued to that campaign. The campaign decides what data those automations send or receive and is responsible for its own third-party services. You can rotate or revoke the key at any time.

7. We do not sell voter data

We do not sell, rent, or trade voter data, door responses, or personal information, and we do not use campaign data for advertising or share it with other campaigns.

8. Security and retention

Data is encrypted in transit, protected by access controls, and logged for audit. We keep campaign data for as long as the campaign's workspace is active, or until the campaign deletes it.

9. Your choices and deletion requests

You may request access to, correction of, or deletion of your account data by emailing support@fieldstrike.app. Requests about a voter record should also be directed to the campaign that uploaded it; we will assist campaigns in honoring those requests.

10. Changes and contact

We may update this policy and will revise the effective date when we do. Questions: support@fieldstrike.app.