How we protect your data

Every record in LeadHound belongs to an account, and every query is filtered by that account at the database layer rather than in page code. Agencies sit above their client accounts and can only reach the ones they have been granted. A request carrying another account’s identifier is rejected outright instead of quietly returning nothing.

Traffic to the application and the tracking snippet is served over TLS. Advertising platform credentials, including OAuth refresh tokens and measurement secrets, are encrypted before they are written to the database and are never returned by the API. Dashboard users only ever see whether a connection has credentials, not the credentials themselves.

• Dashboard sessions use short, revocable bearer tokens. Signing out revokes the token immediately.
• Accounts have two roles. Administrators manage billing, integrations and tracking; standard users work with leads and reports and cannot change the account.
• Public API keys are prefixed so they are recognisable in logs, scoped to one account, rate limited per day, and can be revoked at any time without touching your other keys.

Recording, transcription and AI analysis are separate switches on each number pool, so you can record a sales line without recording anything else. Where PCI redaction is enabled, card-like numbers are stripped from a transcript before it is stored. Incoming webhooks from our telephony provider are signature-verified, so a forged request cannot create calls or leads on your account.

When a conversion is sent to Google Ads or Meta, contact details used for matching are hashed with SHA-256 first. Every upload is claimed in a local ledger before it is sent, which is what stops a retry from double-reporting revenue into your bidding.

Click sessions and number assignments are pruned on a schedule once they pass your retention window, which defaults to 90 days. Leads and calls stay until you delete them. Deleting a website removes its tracking configuration and call history with it.

If you have found a security issue, email security@getleadhound.iowith enough detail to reproduce it. We will confirm receipt within one business day and keep you updated while we fix it. Please give us a reasonable window before publishing, and do not run tests that degrade the service or touch other customers’ data. We will not pursue anyone who reports in good faith and follows this.

• Use a unique password, and remove members who leave your team.
• Treat API keys as passwords, and rotate them if one has been exposed.
• Only switch on call recording where you have told callers and have the right to record.

What we collect and who we share it with is set out in the privacy policy.