ListPlus
  • How it works
  • Product
    • The listColumns, rules and handoffs: how your list works for you.
    • Find leadsFind the right companies and people.
    • Data qualitySpot errors and gaps with 100+ checks.
    • Enrich dataFill in missing contact and company details.
    • AI options inside ListPlusResearch, checks and rules built into the app.
  • Use Cases
    Jobs to do
    • Keep your CRM cleanFix mistakes and fill the gaps.
    • Qualify inbound leadsKnow who is worth a follow-up.
    • Use LinkedIn reactionsTurn likes and comments into contacts.
    • Work your target accountsThe right people at the companies you want.
    Recipes to rebuild
    • Check and fix contact dataUpload a list and have the mistakes fixed.
    • Duplicates before a CRM importWho is already in HubSpot?
    • Score first, then enrichOnly look up contacts that fit.
    • Spot job changesWhen your contact moves to a new company.
    All use cases →All GTM recipes →For GTM engineers (Claude Code) →
  • For AI agents
  • Pricing
  • Open appLog inStart Free
☰✕
How it works
ProductThe listFind leadsData qualityEnrich dataAI options inside ListPlus
Use CasesUse CasesGTM Recipes
For AI agentsPricingContact searchOpen appLog inStart Free

Our position on data protection

Last updated: 10 November 2026

This English version is a convenience translation. The German version is legally binding.

This page is for data protection officers and anyone who reviews ListPlus before using it. It sums up how we see our role and why. The binding texts are the data processing agreement, the privacy policy and the provider list; this page explains them.

1. A tool, not a database

ListPlus does not collect people and does not sell data. Every search, enrichment or research run happens because a customer triggers it in their workspace, and its result belongs to that workspace alone. Nothing about people is shared between customers; across customers we keep only company data without personal reference, for 30 days. Nobody can search for people on ListPlus without an account.

That is why we see ourselves as the customer's processor (Art. 28 GDPR): the customer decides whether, about whom and for what purpose data is retrieved; we provide the tools. The data providers we query on the customer's behalf are controllers of their own databases and receive only the search key. Providers with a data processing agreement process the search key as our further processors, only to answer the query; for their own databases they are controllers themselves. We name every provider with its address and the safeguard it names — or that it names none —, announce new providers 30 days in advance, and the customer can switch off any of them that receives personal data (DPA § 2(3)).

These statements apply to ListPlus and equally to ContactPlus (contactplus.app), the search for individual business contacts of salesperformer GmbH: it is open only to signed-in account holders acting as businesses and processes their retrievals on their behalf under the same DPA (Annex 5). Both use the same infrastructure, the same sign-in and the same suppression list. They do not share results about people: ListPlus keeps caches with personal reference per workspace, ContactPlus per account.

2. The customer is in control, on the server

The owner of a workspace switches off in the workspace policy whatever their data protection officer does not want: individual data providers, AI features, connected systems, the Inbox address, the Agent API, pipeline emails, usage events, contributing to the company cache. Off means: no member and no connected AI system can use the feature, and no data reaches the respective provider — checked on the server, not merely hidden in the interface.

One feature we treat specially: rating research hits (fit score: how well a hit matches the search description) is on but can be switched off; then nobody is rated.

The policy exports as a text file, and the data protection package (policy, DPA with annexes, provider list, notice for the people in the data, privacy policy) opens as one file to print, or as a 30-day link to pass on.

3. Transparency: one list, every name

Every service provider, data provider and source is in one list with seat, data transmitted and third-country safeguard (listplus.ai/en/subprocessors), which is also Annex 3 of the DPA and the recipients section of the privacy policy — generated from one source so there are never two versions. We also name what is uncomfortable: that public sources such as LinkedIn, Crunchbase, Reddit or X are read by scrapers of a data collection platform, that some providers are in the USA, and where a provider names no transfer safeguard.

4. The people in the data

Anyone found or completed through ListPlus finds an explanation addressed to them at listplus.ai/en/contact-data-notice: what ListPlus is, where the data comes from, who receives it, which rights they have. An objection to support@listplus.ai goes, as a checksum, into a suppression list that applies to all customers: the person is no longer retrieved through ListPlus and no longer recorded as a hit. One limit we name: in a search by name and company only, we learn email address and profile only when the provider answers; we then do not store the result.

5. AI

We call AI models only from our servers, never from the browser. By default they process in data centres in the EU; outside the EU only when a workspace owner switches on “AI models outside the EU”. Separately, ListPlus by default queries Parallel’s web index (USA) beside Google search and runs research with cited sources there on a click; the “Parallel” switch turns both off. Job titles with the company name, without the person’s name, are rated by a model in the USA even with EU processing. Requests to OpenAI go with the “do not store” setting, without use for training and without retention after the request; the judgement model works without storage at the provider. The one exception to the server: the browser extension uses Chrome’s built-in model on the user’s device; that content never reaches us. Which data a feature sends is in Annex 4 of the DPA – with its classification under the AI Act and a risk assessment – and in the privacy policy (section 12), including where it is whole texts. No AI output decides anything with legal effect; all of it is suggestions the user reviews.

6. What we deliberately do not do

  • No database of people of our own, no data-broker model — not even for markets where it would be allowed.
  • No sharing of personal data between customers.
  • No person search without an account.
  • No use of customer data for training models, neither by us nor by our AI providers.
  • No regional “non-EU mode”: as a German GmbH we apply the GDPR to everyone, wherever the customer or the person is.

7. What is still open

We also write down what is not finished. Some data providers name no seat or no transfer safeguard; the provider list says so openly, and the customer can switch them off. We have not appointed a data protection officer; whether there is a duty to do so (Art. 37 GDPR, Section 38 BDSG) we review continuously and have assessed by a lawyer. Questions: support@listplus.ai.

ListPlus

Contacts ready for what comes next.

Product

How it worksThe listUse CasesGTM RecipesFind leadsFlowsData qualityEnrich dataIntegrationsAI agentsFor GTM engineersAI in ListPlusPricingChrome extensionOutlook Add-in

Guides

All topicsHubSpot EnrichmentClay alternativeGTM EngineeringAgent API (developers)

Company

BlogYouTubeHelp centerContactStatus

Legal

PrivacyTermsImprintSecurity & GDPRDPAProviders & data sourcesNotice for people in the data
© 2026 ListPlus.ai · salesperformer GmbHPrivacyTermsImprint