leadhoundapi
Back to site
Privacy Policy
Last updated July 20, 2026.
leadhoundapi (leadhoundapi.com) provides lead intelligence from public business signals. This page summarizes what we collect, why we collect it, and which services may process it.
Data We Collect
- Email addresses submitted for free market proofs, magic links, checkout, account creation, and customer support.
- Account data such as API-key hashes and prefixes, plan, covered markets, legacy Signals balance, OAuth client registrations, OAuth refresh tokens, and usage records.
- Request data such as category, city, business name, timestamps, source-vendor events, request identifiers, IP-derived rate-limit keys, an approximate city derived from your IP to prefill the market form, cache hits, monitors, and free-proof records.
- Payment, revenue, and billing events received from Stripe. We do not store full card numbers.
- Provider-wallet and cost-reservation records used to manage vendor spend and account limits.
- Public business data returned by third-party data providers, including business names, websites, phone numbers, ratings, review counts, review metadata, market snapshots, need objects, derived evidence, and related public signals.
- Learning and evaluation records such as compact observations, recommendations, scores, costs, and metadata used to improve routing and quality.
How We Use Data
- Run public market count previews, verified free market proofs, supervised paid scans, legacy Signals calls, MCP tools, and change checks.
- Prevent abuse, enforce market coverage, apply rate limits, meter usage, and control paid vendor costs.
- Provision API keys, process payments, send account emails, debug failures, and improve product quality.
- Maintain source-cost, revenue, market-history, and quality analytics so the service stays reliable and economically enforceable.
Processors And Providers
Depending on the feature used, data may be processed by Cloudflare (hosting, Turnstile human verification, and Workers AI), Stripe, Resend, Google OAuth, third-party business-data providers, and AI model providers. We use these services to host the API, block bots, process payments, send account emails, authenticate users, retrieve public business signals, and perform AI-assisted scoring.
Retention
We keep account, billing, OAuth, usage, free-proof, source-event, scan-history, market-snapshot, need-object, provider-wallet, cost-reservation, and learning records as long as needed to operate the service, enforce limits, support customers, audit costs, improve quality, and satisfy business or legal requirements. Cached public market data may be retained to reduce cost and latency.
Public Reviews
leadhoundapi uses public review signals to create derived evidence and suggested angles. Customer-facing outputs should not republish reviewer names or raw review text. We use paraphrases, labels, scores, and compact evidence instead.
Your Choices
You can request account deletion, correction, API key revocation, or information about your account data by emailing [email protected]. Business opt-out and correction requests can be sent to [email protected]. We may need to retain limited records for fraud prevention, accounting, security, or legal reasons.
Cookies
The dashboard uses a session cookie to keep you signed in. The public site works without sign-in cookies, and we do not use third-party advertising cookies or cross-site trackers.
Security
We use server-side API-key authentication, OAuth access tokens, rate limits, paid-plan and balance checks, no-store responses for key-bearing pages, and vendor-cost caps. No internet service can guarantee absolute security.
Changes
We may update this policy as the product, providers, or legal requirements change. The updated date above shows the latest version.