What a sub-processor is
A company we use that may process personal data from your account.
A sub-processor is a company LeadFindr uses that may process personal data from your account, such as your account details, the leads you find and the emails in your campaigns. We bind every company below to data protection terms at least as strict as the ones we give you. Services you connect yourself, such as your own mailbox, run on your own account and are not our sub-processors.
The current list
Each company with the one job it does for LeadFindr.
| Entity | Country | Purpose | Data |
|---|---|---|---|
| DM Champ | Netherlands | Account, credits and the AI agent engine that writes and answers the cold email autopilot's emails | Account data, lead data, email content and replies |
| VostokInc SAS (ScrapingBee) | France | Business search results from Google Maps, and fetching each business's public website to find owners and emails | Search terms, public business and website data |
| Google Maps Platform (Google LLC) | United States | Business search and turning a location into map coordinates | Search terms and locations |
| MillionVerifier (MillionVerifier Kft.) | Hungary | Checks whether an email address is deliverable before it is shown to you | Lead email addresses |
| Anthropic PBC | United States | AI processing for the cold email autopilot and lead search, depending on how requests are routed | Lead business data, public website content, email content and replies |
| Google LLC | EU, United States | AI processing for the cold email autopilot and lead search, depending on how requests are routed | Lead business data, public website content, email content and replies |
| OpenAI Ireland Ltd. (OpenAI OpCo, LLC) | Ireland, United States | AI processing for the cold email autopilot and lead search, depending on how requests are routed | Lead business data, public website content, email content and replies |
| Alibaba Cloud (Singapore) Private Limited | Singapore | AI processing for the cold email autopilot and lead search, depending on how requests are routed | Lead business data, public website content, email content and replies |
| Mistral AI SAS | France | AI processing for the cold email autopilot and lead search, depending on how requests are routed | Lead business data, public website content, email content and replies |
| xAI Corp. | United States | AI processing for the cold email autopilot and lead search, depending on how requests are routed | Lead business data, public website content, email content and replies |
| Amazon Web Services, Inc. (Amazon Bedrock) | EU, United States | AI processing for the cold email autopilot and lead search, depending on how requests are routed | Lead business data, public website content, email content and replies |
| Microsoft Corporation (Azure AI Foundry, Azure OpenAI Service) | EU, United States | AI processing for the cold email autopilot and lead search, depending on how requests are routed | Lead business data, public website content, email content and replies |
| Cohere Inc. | Canada, United States | AI processing for the cold email autopilot and lead search, depending on how requests are routed | Lead business data, public website content, email content and replies |
| Groq, Inc. | United States | AI processing for the cold email autopilot and lead search, depending on how requests are routed | Lead business data, public website content, email content and replies |
| Together AI (Together Computer, Inc.) | United States | AI processing for the cold email autopilot and lead search, depending on how requests are routed | Lead business data, public website content, email content and replies |
| Fireworks AI, Inc. | United States | AI processing for the cold email autopilot and lead search, depending on how requests are routed | Lead business data, public website content, email content and replies |
| OpenRouter, Inc. | United States | AI processing for the cold email autopilot and lead search, depending on how requests are routed | Lead business data, public website content, email content and replies |
| Voyage AI Innovations, Inc. (a MongoDB company) | United States | AI processing for the cold email autopilot and lead search, depending on how requests are routed | Lead business data, public website content, email content and replies |
| Runpod, Inc. | United States | AI processing for the cold email autopilot and lead search, depending on how requests are routed | Lead business data, public website content, email content and replies |
| Vast.ai Inc. | United States | AI processing for the cold email autopilot and lead search, depending on how requests are routed | Lead business data, public website content, email content and replies |
| Firebase Authentication (Google LLC) | Global (entity: United States) | Account sign in | Account email and sign in details |
| Stripe Payments Europe, Ltd. | Ireland | Billing and payments | Billing contact, payment details (held by Stripe) |
| Mailgun Technologies (Sinch) | EU region | Transactional email, such as access and account notices | Account email, email content |
| Hetzner Online GmbH | Germany | Hosting of the app, its API and databases, and backups | All service data |
| Cloudflare, Inc. | United States, EU | Website hosting, edge network, DNS, TLS and the bot check on the free try it step | Request metadata, IP addresses |
| Sentry (Functional Software, Inc.) | EU (entity: United States) | Application error and performance monitoring | Error reports, which can include request data |
How AI requests are routed
One purpose line for every AI provider, because requests move between them.
The cold email autopilot runs on the DM Champ AI agent engine. The AI providers above are every provider that engine may route requests to, so a routing change never adds a company you have not seen here. Which provider handles a given request depends on how requests are routed at that moment, which is why each AI provider carries the same purpose line.
Transfers outside the EU
Standard Contractual Clauses cover every transfer out of the EU.
LeadFindr itself is hosted in Germany. Where a sub-processor processes data outside the European Economic Area, such as in the United States or Singapore, the transfer is covered by the European Commission's Standard Contractual Clauses.
Changes to this list
14 days notice by email before a new sub-processor sees customer data.
- Before a new sub-processor processes customer data, we email every customer at least 14 days in advance and update this page.
- To object, email [email protected] before the date in the notice.
- If the objection cannot be resolved, you may end the affected service without penalty, as set out in the Terms.
- Removing a sub-processor we no longer use needs no notice. We simply take it off this page.