Privacy Policy

Last updated June 26, 2026.

leadhoundapi 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 keys, plan, covered towns, 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, and cache hits.
• Payment and billing events received from Stripe. We do not store full card numbers.
• Public business data returned by third-party data providers, including business names, websites, phone numbers, ratings, reviews metadata, and related public signals.

How We Use Data

• Run free market proofs, paid scans, Signals calls, MCP tools, and change checks.
• Prevent abuse, enforce town 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 and revenue analytics so the service stays reliable and economically enforceable.

Processors And Providers

Depending on the feature used, data may be processed by Cloudflare, Stripe, Resend, Google OAuth, DataForSEO, SerpApi, OpenRouter, and Cloudflare Workers AI. We use these services to host the API, 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, and source-event records as long as needed to operate the service, enforce limits, support customers, and satisfy business or legal requirements. Cached public market data may be retained to reduce cost and latency.

Your Choices

You can request account deletion, correction, API key revocation, or information about your account data by emailing [email protected]. We may need to retain limited records for fraud prevention, accounting, security, or legal reasons.

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.