Privacy Policy
Last updated 30 July 2026 · These terms are maintained by LeadsCastle.
This page explains what information the service handles, why, and what you can ask us to do with it. It describes current practice in the product; it is not a certification or an audit result.
Information we collect
Account information — the name and email address used to create your account, your plan, and authentication records needed to sign you in.
Usage information — the searches you run, your monthly allowance consumption, plan-change events, and basic technical logs used to operate and debug the service.
Lead data — business contact records returned by your searches (such as business name, address, phone, website and business email), stored against your account so you can review, export and push them to your CRM.
Billing information — subscription status, plan and invoice history. Card details are entered directly with our payment processor and are never stored on our servers.
Integration settings — the credentials you supply to connect your CRM, stored so we can deliver leads to it on your instruction.
How we use it
To provide the service and run your searches; to deliver leads to the destinations you connect; to enforce plan allowances; to bill you and prevent abuse; to send account, security and transactional email; and to improve reliability and product quality.
We do not sell your account information or your saved lead lists to third parties.
Where lead data comes from
Lead records are compiled from third-party data providers and publicly available business sources. They are business contact details, not consumer profiles. If you are the subject of a record and want it removed from your view of the service, contact us using the address below; removal from the original public source must be requested from that source.
Service providers we use
We rely on a small number of processors to run the service: a cloud application and database platform for hosting, authentication and storage; a payment processor for subscriptions and invoices; lead data and email-verification providers; an email provider for transactional messages; and, where you enable it, your CRM as a delivery destination. Each receives only the data needed for its function.
Security
Access to the application requires authentication, data is transmitted over encrypted connections, and stored records are scoped so an account can only read its own data. Integration credentials and API keys are held server-side and are not exposed to the browser. No system is perfectly secure — use a strong, unique password and tell us promptly if you suspect an issue.
Retention and deletion
Account, usage and lead data is kept while your account is active. After cancellation, data associated with the account may be deleted following a short grace period, other than billing records we are required to keep. You can export your lead data at any time while your account is active.
Your choices
You can access and update your account details in the app, export or delete saved leads, disconnect an integration at any time, and ask us to close your account and delete the data we hold. Depending on where you live, you may have additional rights over personal data — contact us and we will action reasonable requests.
Cookies
We use cookies and local browser storage that are necessary to sign you in, keep your session alive (including when the app runs inside a CRM dashboard iframe) and remember your interface preferences.
White-label accounts
If you reached this service through a partner's branded version, that partner operates the account relationship with you and may hold your account and lead data as part of their business. This policy describes how the underlying platform handles data; your partner's own practices apply in addition.
Changes
We may update this policy as the product changes. The date at the top shows when it was last revised.
Questions about this page?
Contact our support team.
