Privacy Policy

This Privacy Policy explains how LeadHunter processes information when users create an account, request lead research, save lead records, enrich public contact information, and use export or integration features.

LeadHunter is designed to organize publicly available business information. This policy is a product disclosure and is not legal advice.

We process information users provide directly, including:

• Account email address and authentication credentials submitted through the sign-in or signup flow.
• Search terms, locations, URLs, filters, and source choices submitted to run lead research.
• Spreadsheet IDs, tab names, export selections, and other integration inputs.
• Support requests, plan inquiries, and other communications sent to us.

LeadHunter uses Supabase for account authentication and session management. Authentication tokens are stored in secure, HTTP-only cookies according to the application's session configuration.

LeadHunter does not sell user login credentials. Users are responsible for keeping their account credentials secure and for notifying support if they believe an account has been compromised.

At a user's request, LeadHunter may collect and organize publicly available business information such as business names, websites, phone numbers, addresses, categories, source URLs, and public contact information.

Public source data can be incomplete, outdated, or unavailable. LeadHunter does not guarantee that every field will be present or current.

LeadHunter uses configured Google Places or related Google services to process local-business searches. Information returned by those services is handled according to the product workflow and the applicable Google terms. LeadHunter does not automate or bypass the private Google Maps user interface.

When a business website is available, public email discovery may inspect a limited set of public website pages, such as the homepage, contact page, about page, team page, or locations page.

LeadHunter may store a public email address, the page where it was found, a confidence score, or a detected public contact-page URL. It does not log into private pages, bypass access controls, or guarantee that an email will be found.

For restaurant campaigns, LeadHunter may infer public delivery-platform presence from public search-result titles, snippets, and URLs. It may store a matching public listing URL and confidence status.

LeadHunter does not claim access to private restaurant-platform dashboards and does not claim official partnership or verification. Platform presence may require manual verification.

When community features are enabled, LeadHunter may process public posts or listings from supported startup communities. Availability depends on source configuration and provider access. Private posts and account-only data are outside the intended workflow.

LeadHunter exports only the saved lead records and filters selected by the authenticated user. Internal identifiers and raw metadata are excluded from customer-facing export formats.

For Google Sheets, users provide a spreadsheet ID and tab name and grant the configured service account permission to edit the destination spreadsheet. Users can remove that permission through Google Sheets.

LeadHunter processes usage counts, scrape-job status, source types, timestamps, error information, and other operational records needed to enforce plan allowances, prevent abuse, diagnose failures, and operate the service.

LeadHunter uses authentication cookies to maintain secure sessions and may use limited browser storage for product preferences. Disabling required session cookies may prevent access to authenticated features.

LeadHunter relies on providers such as Supabase, Google Places, Google Sheets, hosting infrastructure, Upstash when configured, ScrapeGraphAI for enabled extraction sources, and configured search providers for delivery presence checks. Their processing is subject to their own terms and privacy practices.

Account, lead, job, usage, and integration records are retained for as long as reasonably necessary to provide the service, maintain security, resolve disputes, and meet legal obligations. Retention periods may vary by record type and operational need.

LeadHunter uses reasonable technical and organizational safeguards, including authenticated access, user-level data isolation, protected server credentials, and secure session cookies. No online service can guarantee absolute security, and LeadHunter does not claim certifications that have not been obtained.

Users can choose which searches to run, which records to save or delete, which leads to export, and which spreadsheets receive synced data. For account-data or privacy requests, contact irssmex@gmail.com.

LeadHunter may be accessed from multiple countries, and service providers may process information in different jurisdictions. Users remain responsible for ensuring that their use of business information and outreach complies with laws that apply to them.

LeadHunter is a business research service and is not directed to children. Users must be old enough to enter into a binding agreement in their jurisdiction.

We may update this policy as LeadHunter's features, providers, or legal requirements change. The updated date at the top of this page identifies the latest published version.

Questions or requests can be sent to irssmex@gmail.com.