Effective September 12, 2026

Privacy Policy

This policy explains what LeadHound handles, why it is needed, where it is stored, and when information is shared with service providers.

1. Scope and single purpose

LeadHound's single purpose is to help users find, organize and export publicly displayed local-business lead information from Google Maps searches selected by the user. Data handling is limited to operating this functionality, enforcing the free-plan quota, authenticating optional accounts, and managing PRO subscriptions.

2. Data handled by the extension

Google Maps website content

When the user starts a search, LeadHound reads business information displayed on Google Maps pages that matches the user's search. Depending on the selected mode and what Google Maps displays, this may include a business name, publicly displayed telephone number, address, category, rating, review count, website link and Google Maps listing URL.

Lead results and search history are primarily stored locally in the user's browser using Chrome storage and/or IndexedDB so they can be displayed and exported by the user.

Search configuration and user activity

LeadHound stores settings required to operate the extension, such as selected states, cities, manually entered locations, keywords, search mode, search progress, saved results and the number of unique leads used under the free plan.

Device identifier and free-plan usage

LeadHound generates a random pseudonymous device/profile identifier to enforce the 200-lead free allowance and reduce repeated free-trial abuse. The identifier is sent over HTTPS to the LeadHound backend. The backend stores a SHA-256 hash of the identifier together with the free-lead usage count; it does not use this identifier for advertising or cross-site tracking.

Optional account information

An account is not required for the free plan. If a user creates an account to access PRO features, LeadHound handles the user's email address, password and authentication session. Passwords are transmitted over HTTPS and stored on the backend only as a one-way password hash; plaintext passwords are not stored.

Subscription information

For PRO subscriptions, the LeadHound backend stores information necessary to identify subscription entitlement, such as Stripe customer ID, Stripe subscription ID, subscription status and account plan status. LeadHound does not receive or store full card numbers, card security codes or bank account credentials.

3. Stripe

Payments and subscription checkout are processed by Stripe. When a user chooses to subscribe, LeadHound may provide Stripe with the account email and internal account reference needed to create and associate the subscription. Payment-method information is handled by Stripe under Stripe's own privacy and security practices.

4. How data is used

to perform searches requested by the user and display/export results;
to remember the user's settings, saved results and search progress;
to apply the 200-lead free-plan quota;
to authenticate optional LeadHound accounts;
to activate, verify and manage PRO subscription access;
to maintain security, prevent abuse and troubleshoot service reliability.

5. Data sharing

LeadHound does not sell user data and does not transfer user data for personalized advertising, creditworthiness, lending or unrelated marketing purposes.

Information may be shared only when necessary to provide the service, including with Stripe for payment/subscription processing and with infrastructure providers that host the LeadHound backend, or when required by law or necessary to protect the security of the service.

6. Google Maps content

LeadHound processes Google Maps page content only when needed for the user-facing lead-finding functionality. LeadHound is an independent product and is not affiliated with Google. Use of Google services remains subject to the terms and policies applicable to those services.

7. Security

Personal or sensitive information transmitted between the extension and the LeadHound backend is sent over HTTPS. Passwords are hashed server-side. Stripe secret keys and webhook signing secrets are stored only on the server and are not included in the Chrome extension.

8. Retention and deletion

Locally stored leads and search history can be cleared from the extension. Server-side free-plan usage may remain associated with a pseudonymous device hash to enforce the one-time free allowance. Registered users may request deletion of their LeadHound account and associated account data through the support channel described on the Support page, subject to information that must be retained for legal, security or transaction-record purposes.

9. Children's privacy

LeadHound is a business productivity tool and is not directed to children.

10. Changes

If LeadHound materially changes its data-handling practices, this policy and relevant product/store disclosures will be updated before the new practices are used where required.

11. Chrome Web Store Limited Use

Limited Use disclosure: LeadHound's use and transfer of information received from Google Chrome APIs and website content will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only to provide or improve LeadHound's disclosed single purpose and related security/operational functions.

12. Contact

For privacy or account-deletion requests, use the instructions on LeadHound Support.