Lynx Privacy Policy

This Privacy Policy explains how Jeremy Lese (“Lynx,” “we,” “us,” or “our”) collects, uses, stores, discloses, and protects information when you use Lynx, including our web platform, companion mobile applications, websites, dashboards, APIs, and related services collectively referred to as the “Service.”

Lynx is designed for civic, political, campaign, field, fundraising, staff, communications, and operational workflows. Because these workflows may involve voter records, donor records, staff records, location-enabled field activity, internal messages, survey responses, and other sensitive operational data, we take privacy seriously.

1. Information We Collect

We may collect the following categories of information.

Account information

We may collect your name, email address, username, password or authentication credentials, phone number, organization name, role, permissions, billing status, and other account setup details.

Organization and project information

We may collect organization details, project details, campaign details, assigned staff, schedules, goals, geographic areas, walkbooks, canvassing assignments, resources, hotel or logistics details, and operational notes.

Voter, contact, and canvassing data

Users may upload, import, create, or generate voter records, contact records, address information, district or geographic information, canvassing outcomes, survey responses, notes, support levels, interaction history, contact attempts, not-home/refused/inaccessible outcomes, and related field activity.

Staff and workforce data

We may process staff names, contact information, roles, assignments, shift schedules, availability, schedule requests, field activity, performance metrics, quality assurance alerts, and internal communications.

Location data

With appropriate device permissions, the Lynx mobile app may collect or process device location data to support field operations, assigned walkbooks, distance checks, quality assurance alerts, address verification, map functionality, and operational reporting.

Location data may be compared against assigned addresses or project locations to identify whether field activity occurred near the expected location.

Messages and communications

If you use Lynx messaging or communication tools, we may process message content, sender and recipient information, timestamps, delivery metadata, conversation membership, templates, drafts, and related communications data.

Fundraising and donor data

If fundraising features are used, we may process donor names, contact information, contribution records, pledge records, compliance fields, source information, fundraising assignments, reporting metadata, and related notes.

Payment details may be processed by third-party payment processors such as Stripe. We do not intentionally store full credit card numbers on our own servers.

Device, usage, and technical information

We may collect IP address, browser type, device type, operating system, app version, pages viewed, features used, session activity, log files, crash reports, diagnostics, authentication events, security events, and approximate location derived from IP address.

2. How We Use Information

We may use information to:

• Provide, operate, maintain, and improve the Service.
• Create and manage user accounts, organizations, projects, and permissions.
• Enable canvassing, walkbooks, field assignments, surveys, and mobile workflows.
• Display maps, turf, geographic data, address information, and operational dashboards.
• Generate analytics, reports, performance metrics, and quality assurance alerts.
• Enable internal messaging and team coordination.
• Support fundraising, donor management, compliance workflows, and related reporting tools.
• Process payments, subscriptions, seat limits, billing, and account status.
• Provide customer support, troubleshooting, security monitoring, and fraud prevention.
• Enforce our Terms, protect users, and comply with legal obligations.
• Develop new features, improve reliability, and understand usage trends.

3. How We Share Information

We do not sell your personal information. We may share information in the limited circumstances described below.

With your organization

Information submitted to an organization, project, campaign, committee, or workspace may be visible to administrators, managers, authorized staff, or other users within that organization based on roles and permissions.

With service providers

We may share information with vendors and service providers that help us host, secure, process, analyze, support, or deliver the Service. These may include cloud hosting providers, database providers, authentication providers, payment processors, email providers, analytics providers, error monitoring tools, messaging providers, mapping services, geocoding providers, and mobile platform services.

With integrations you enable

If you connect Lynx to third-party services, export data, use an API, or authorize an integration, information may be shared according to your settings and the third party’s terms and privacy policy.

For legal and safety reasons

We may disclose information if we believe disclosure is reasonably necessary to comply with law, regulation, subpoena, court order, legal process, law enforcement request, security investigation, or to protect the rights, safety, property, or integrity of Lynx, our users, or others.

Business transfers

If Lynx is involved in a merger, acquisition, financing, reorganization, bankruptcy, sale of assets, or similar transaction, information may be transferred as part of that transaction, subject to appropriate confidentiality and legal protections.

4. Cookies and Similar Technologies

We may use cookies, local storage, tokens, device identifiers, and similar technologies to keep you signed in, remember preferences, secure sessions, analyze usage, and operate the Service.

You can control cookies through your browser settings, but disabling cookies or local storage may prevent parts of the Service from working correctly.

5. Data Retention

We retain information for as long as reasonably necessary to provide the Service, fulfill the purposes described in this Privacy Policy, comply with legal obligations, resolve disputes, enforce agreements, maintain security, and support legitimate business needs.

Customer Data may remain in backups, logs, archives, or legally required records for a limited period after deletion from active systems.

6. Security

We use administrative, technical, and organizational safeguards designed to protect information. These may include access controls, authentication, encryption in transit where appropriate, logging, monitoring, and separation of user permissions.

No system is perfectly secure. You are responsible for using strong passwords, protecting credentials, managing organization access, and promptly notifying us of suspected unauthorized access.

7. Your Choices and Rights

Depending on your location and applicable law, you may have rights to access, correct, delete, export, restrict, or object to certain processing of your personal information.

Organization administrators may be responsible for responding to requests involving Customer Data controlled by that organization. If you are a staff member, volunteer, donor, voter, or contact whose information was added by a Lynx customer, you may need to contact that organization directly.

You may contact us at jlese2005@gmail.com to make a privacy request. We may need to verify your identity before fulfilling a request.

8. Location Permissions

On mobile devices, you may control location permissions through your device settings. Disabling location permissions may limit or disable certain field operations, map, quality assurance, distance verification, or walkbook features.

9. Children’s Privacy

The Service is not intended for children under 13, and we do not knowingly collect personal information from children under 13. If we learn that we have collected such information, we will take appropriate steps to delete it.

10. Political and Public Records Data

Some information processed through Lynx may originate from public records, voter files, customer-provided datasets, campaign data, donor records, or other third-party sources. Customers are responsible for ensuring that their collection, upload, use, and disclosure of such data complies with applicable law and source restrictions.

11. International Users

Lynx may process information in the United States and other locations where we or our service providers operate. If you access the Service from outside the United States, you understand that your information may be processed in jurisdictions that may have different data protection laws than your location.

12. Third-Party Links and Services

The Service may contain links to third-party websites, platforms, payment processors, maps, integrations, or services. We are not responsible for the privacy practices of third parties. Review their privacy policies before providing information to them.

Mobile Application Privacy

The Lynx mobile application is designed for authorized field users, staff, contractors, volunteers, and administrators who use Lynx to access assigned projects, walkbooks, voter or contact records, survey workflows, internal messages, and related field operations.

The mobile application may collect or process account information, project assignments, canvassing activity, survey responses, notes, timestamps, message activity, device information, app diagnostics, and location data when location permissions are enabled.

Location data is used to support field operations, map functionality, assignment verification, quality assurance, and proximity-based checks such as confirming whether a recorded canvassing action occurred near the assigned address. Location data is not used for advertising.

Users may control mobile permissions, including location permissions, through their device settings. Disabling permissions may limit certain field, map, walkbook, or quality assurance features.

13. App Store Privacy Disclosures

For users of Lynx mobile applications, app store privacy disclosures are intended to summarize certain data practices. This Privacy Policy provides additional detail. If there is a conflict between a short app store disclosure and this Privacy Policy, this Privacy Policy controls to the extent permitted by applicable law.

14. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. The updated version will be posted on this page with a revised “Last updated” date. Your continued use of the Service after changes become effective means you acknowledge the updated Privacy Policy.

15. Contact

Questions or privacy requests may be sent to:
jlese2005@gmail.com