ListPlus
  • How it works
  • Product
    • 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 your own AI agentsConnect ChatGPT, Claude or your own agent to your lists.
  • Use Cases
  • GTM Recipes
  • Pricing
  • Open appLog inStart Free
☰✕
How it works
ProductFind leadsData qualityEnrich dataAI options inside ListPlusUse your own AI agents
Use CasesGTM RecipesPricingContact searchOpen appLog inStart Free

Privacy Policy

Last updated: 10 November 2026

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

This privacy policy informs you under Articles 13 and 14 of the General Data Protection Regulation (GDPR) which personal data we process when operating the website listplus.ai and the ListPlus application (listplus.ai/app, including the Outlook add-in, the browser extension for Chrome and the Agent API), for which purposes, on which legal basis, and which rights you have.

1. Controller

salesperformer GmbH Sperberweg 7 82152 Krailling Germany Phone: +49 (0)89 28741023 Email: support@listplus.ai Commercial register: Amtsgericht München, HRB 189481 Managing Director: Stephan Methner

For any data protection question and to exercise your rights, contact us at support@listplus.ai.

2. Data protection officer

We have not appointed a data protection officer at present; once we appoint one, we will name their contact details here. Please send data protection requests to support@listplus.ai.

3. Overview: our role in processing your data

Depending on your relationship with ListPlus, we process your data in different roles:

  • Website visitors (listplus.ai): we are the controller for the data arising when you visit the website (sections 4 and 5).
  • Users of the application (customers and their staff with their own account): we are the controller for account, contract, billing, usage and support data (sections 6 to 10).
  • People in customer lists: personal data that customers upload, import, create, enrich or forward to the Inbox is processed by us on behalf of that customer as a processor under Art. 28 GDPR. The customer is the controller (section 11).
  • People whose business contact data is retrieved through ListPlus: when customers retrieve contact or company data from data providers through ListPlus, section 13 gives you supplementary information about the sources and the processing; the duty to inform under Art. 14 GDPR lies with the respective customer.
  • ContactPlus: salesperformer GmbH also runs ContactPlus (contactplus.app), a search for individual business contacts for signed-in account holders. What an account holder retrieves there about other people it processes on their behalf, as at ListPlus (DPA, Annex 5); for accounts and purchases the ContactPlus privacy policy applies (contactplus.app/privacy). Both services use the same sign-in and the same suppression list (section 13); they do not share results about people.
  • Visitors who look at the application without an account: they see the interface and the sample list with invented data; searches, enrichments and everything that retrieves third-party data require an account. Section 4 applies to these visitors.

4. Visiting the website and hosting

The website and the application are hosted by Vercel Inc. (440 N Barranca Ave #4133, Covina, CA 91723, USA); servers and file storage are located in the EU region Frankfurt am Main. When you open a page, Vercel processes technically necessary connection data: IP address, date and time, requested URL, referrer, browser and operating system information and status codes (server log files).

Purpose: delivering the website, stability, security and abuse prevention. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in a secure, working service). Retention: server log files are deleted after at most 30 days unless needed longer to investigate a security incident.

Although servers and file storage are in the EU, data may also be transferred to the USA by Vercel itself, as Vercel is a US company and uses subprocessors. Vercel is certified under the EU-U.S. Data Privacy Framework; in addition we have concluded a data processing agreement with Standard Contractual Clauses with Vercel (see sections 15 and 16).

5. Cookies, local storage and analytics

We do not use advertising or tracking cookies, and no cookies from ad networks or social networks. We use the following cookies and entries in your browser's local storage (localStorage):

NameTypePurposeDuration
NEXT_LOCALECookie (first-party)Stores the language you chose for the website and the application1 year
hankoCookie (first-party, domain .listplus.ai)Session token after sign-in; signing in is not possible without itUntil sign-out or session expiry (max. 30 days)
lp-split-lists, lp-split-inbox, lp-split-pipelines, lp-split-saved, lp-split-segment, lp-split-research, lp-split-personCookie (first-party)Remembers whether and how wide each view's left column (e.g. the lists sidebar) is shown in the application1 year
lp_wsCookie (first-party, HttpOnly)Remembers which workspace you work in1 year
Application settings (e.g. userLanguage, column views and filters, last opened list, search history, inputs to the AI assistant, panel state, the state of your research runs, companies last loaded in the Markets search)localStorageStores your settings and work state in the browser so that they are there next time; the application sends some of them to our servers when a feature needs them (e.g. the language, your own checks)Until you clear it in your browser
hanko_session_state, hanko_last_login, hanko_pkce_code_verifier, pusherTransportTLSlocalStorage / sessionStorage (libraries of the sign-in service and the realtime service)State of the sign-in and of the live connectionUntil sign-out or until you clear it in your browser
hanko-auth-flow-statelocalStorageIntermediate state of the sign-in flowUntil sign-in completes
lp-help-talk, lp-help-talk-idsessionStorageYour conversation with the AI help (section 9) and a random identifier of the conversation, so that it is kept when you change the page; only created when you ask a questionUntil you close the browser tab

Legal basis: storing and reading this information on your device is based on Section 25(2) no. 2 TDDDG (German Telecommunications Digital Services Data Protection Act) where it is strictly necessary to provide the service you explicitly requested (sign-in, language setting, application settings, the AI help's conversation). The subsequent processing is based on Art. 6(1)(b) GDPR (user agreement) or Art. 6(1)(f) GDPR.

Reach measurement, usage events and error logs

Website and application: we use Vercel Web Analytics and Vercel Speed Insights to measure reach and page speed. These services work without cookies and without cross-device profiles. They record pages visited, referrer, approximate country-level location, device type, browser and operating system, and load times; to distinguish visits, a hash derived from request data is used and discarded daily.

Application: which features are used when, we count with PostHog (PostHog Inc., EU cloud in Frankfurt). Each event carries a pseudonym of your account (a hash of the user ID, not reversible), the plan, a hash of the workspace, the event and its properties (e.g. “list created”, “enrichment started”, the number of rows) — never names, email addresses or the contents of your lists. PostHog sets no cookies for us and records no sessions. You can switch usage measurement off in your account settings; a workspace owner can switch it off for all members (workspace policy). Independently of that, we keep daily counters without any personal reference (how often a feature was used).

Error logs: the logs of our servers are kept by our host Vercel. When an error happens in your browser, we only count on which kind of page it happened (as a usage event at PostHog, see above) — without the error text; the error itself does not leave your browser.

Purpose: improving the website and application, error analysis. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in designing our service to meet demand and in running it reliably). Recipients: Vercel Inc., PostHog Inc. (see section 15).

Third-party content your browser loads

In a few places your browser loads content directly from third parties, which thereby learn your IP address and browser data: map tiles from OpenStreetMap in the contact view and the record panel (with the coordinates of the company shown, not yours), icons from jsDelivr, profile pictures of people and company logos directly from LinkedIn or the data provider, images whose address is in a cell of your list, app logos from Pipedream (assets.pipedream.net) and, when you connect a tool, its sign-in dialog, and in the Outlook add-in Microsoft's Office library and the sign-in script via jsDelivr. We serve our explainer videos and their preview images ourselves (Vercel's file storage). Legal basis: Art. 6(1)(f) GDPR; our legitimate interest is to show the content you open.

Google Maps only on click: in the contact view, a person with a location shows a placeholder. Only when you click “Load map” does your browser load a map from Google Maps (Google Ireland Limited, Dublin); Google then receives your IP address, browser data, any Google cookies and the place shown. Legal basis: your consent by the click (Art. 6(1)(a) GDPR, § 25(1) TDDDG); without a click nothing is loaded.

Stripe and Link payment pages

When you subscribe to a plan or buy credits, you are redirected to a Stripe Managed Payments checkout page (checkout.stripe.com) on which Sold Through Link, LLC acts on our behalf as merchant of record (section 8); to manage the subscription we take you to the Stripe customer portal, and you can also manage orders at link.com. The privacy notices of Stripe and Link apply there; Stripe and Link set their own cookies there, among other things for fraud prevention.

6. Registration, sign-in and user account

To use ListPlus you create an account with your email address. You sign in with your email address and a one-time passcode we send you by email, or with “Sign in with Google”; we do not store a password. The sign-in service is operated for us by Hanko GmbH, Kiel, Germany (hosted in the EU); a session lasts 30 days. If you choose to sign in with Google, Google LLC (USA) confirms your identity and sends us your email address and your Google account ID; Google learns that you sign in to ListPlus (third-country safeguard: EU-U.S. Data Privacy Framework). We process your email address, optionally your name, an internal user ID, the sign-in method, the times of registration and sign-in, and technical session data. The same sign-in is used for ContactPlus (contactplus.app). On registration we check whether the address comes from a provider of throwaway addresses; for this we ask the public services debounce.io and kickbox.com and MillionVerifier about the domain of the address (not the address itself).

Purpose: setting up and securing your account. Legal basis: Art. 6(1)(b) GDPR (contract or pre-contractual steps). Retention: for the duration of the user relationship; after the account is deleted, the data is deleted unless statutory retention obligations apply.

7. Providing the application and performing the contract

When you use ListPlus, we process your account data, your plan, your credit balance and its transactions (purchases, usage per action, refunds), settings, the lists, folders and saved contacts you create, AI agent connections, the lists shared with them and their call logs, as well as technical logs for error analysis and abuse detection.

Purpose: providing the contractual services, billing credits, security and abuse prevention (e.g. rate limits). Legal basis: Art. 6(1)(b) GDPR; for security and abuse prevention Art. 6(1)(f) GDPR.

For a fast working data store we use Redis Cloud (Redis EMEA Ltd., London), hosted in the Frankfurt region (AWS eu-central-1). For live status updates in the browser (e.g. “import finished”) we use the realtime service Pusher (Bird B.V., Amsterdam; servers in Ireland); it transmits event and status information about your operations and, for small changes, the changed cell values.

For managing your account, the following also applies:

  • On sign-up, we add you to our CRM system Attio: your email address and your user ID. There we also note your plan and key events of your account — sign-up, first list, first enrichment, first flow, joining a workspace, buying a plan or credits, cancelling — and the progress they add up to (a stage and a score, e.g. “Enriched”, 40 of 100), so we see how far you use ListPlus. The contents of your lists never go there. The CRM system sends a welcome email. The same events with your email address and user ID also go to our automation service n8n (n8n GmbH, Berlin, hosted in the EU), which notifies our team via Slack; so do a failed payment, a refund or payment dispute (with the amount), unlocking or renewing a connected tool on the Basic plan, a newly connected tool (which app), the deletion of your account (only the user ID, plan and number of lists) a question the AI help could not answer (the question's text, without user ID or email address), and a sign-up refused for a disposable email address (the address, its domain, the user ID and which check recognised it).
  • On a purchase, Stripe reports it to an interface of our service; we record the purchased plan or credits on your account.

Purpose: managing your account and plan, sending the welcome email to get you started, and looking after our customers (e.g. help getting started, questions about the plan or a cancellation). Legal basis: Art. 6(1)(b) GDPR (performance of the user agreement); for the account events in the CRM Art. 6(1)(f) GDPR (legitimate interest in looking after our customers). When you delete your account, we delete these entries too; only your email address stays there on a suppression list so that we never contact you again (Art. 6(1)(f) GDPR). The welcome email is purely a greeting and onboarding message about your account, not advertising. We only send newsletters or promotional emails with your explicit consent (Art. 6(1)(a) GDPR), which you can withdraw at any time.

Workspaces and invitations

You work in workspaces. Lists, Watchlist, Inbox, research runs, pipelines and connected systems belong to the workspace and every member sees them; plan and credits belong to the workspace owner. Whoever invites a member triggers an email to the invited address with the inviter's name and the workspace name, sent via Postmark (section 14) from notifications@listplus.ai; an invitation expires after 14 days. The owner can switch features and data providers off for all members in the workspace policy; the current policy can be viewed in the workspace settings and exported as a text file. Legal basis: Art. 6(1)(b) GDPR; for the invitation email to a person not yet registered, Art. 6(1)(f) GDPR (the inviter's interest in working together).

8. Payments and invoices

We sell plans and credit packs through Stripe Managed Payments. The sale is handled on our behalf by the merchant of record Sold Through Link, LLC (formerly Lemon Squeezy, LLC), 354 Oyster Point Boulevard, South San Francisco, California 94080, USA, a Stripe company; payments are processed in the EU by Stripe Technology Europe, Limited and in other regions by another Stripe group company. Link calculates, collects and remits VAT (or sales tax or GST), issues invoices, receipts and refund notices and sends them to you by email, handles requests about payments and refunds (support.link.com) and gives you your order history and management of subscription, payment method and billing address at link.com; Stripe handles payment disputes and screens payments for fraud.

Data: In the checkout you enter your name, email address, billing address and payment data directly with Stripe or Link; you can create a Link account or pay as a guest. We pass your email address, your user ID and the purchased product and price to Stripe. We do not receive full card or account details from Stripe, only customer and payment status information (customer and transaction IDs, email address, amount, currency, tax amount, status, plan) and invoice data.

Responsibility: Link and Stripe are independent controllers for the purchase, invoicing, tax, payment processing, fraud prevention and the Link account; the privacy notices of Link and Stripe apply. You can ask Stripe or Link to delete the data of your Managed Payments purchases and your Link account. We process the data we receive from Stripe to activate your plan and credits and to keep our accounts. Under its terms Stripe alone determines the purposes and means of this processing (Stripe Managed Payments Terms, section 6.1; Stripe's data processing agreement, “Stripe as controller”); there is no joint controllership. Privacy notices: stripe.com/privacy and link.com/privacy.

Third-country transfer: Sold Through Link, LLC and Stripe, LLC are based in the USA; the data of your purchase is therefore transferred to the USA. The basis is Stripe's Data Transfers Addendum: primarily the EU-U.S. Data Privacy Framework (Art. 45 GDPR; Stripe, LLC is certified), otherwise the EU Standard Contractual Clauses (Art. 46(2)(c) GDPR). The addendum also covers Stripe's affiliates, including Sold Through Link, LLC.

Legal basis: Art. 6(1)(b) GDPR (performance of contract) and Art. 6(1)(c) GDPR (tax and commercial law obligations). Retention: we keep accounting records for the statutory periods (Section 147 AO, Section 257 HGB: 8 years for vouchers, 10 years for books and annual accounts); how long Link and Stripe keep data is set out in their privacy notices.

9. Support by email and AI help

When you contact us by email (support@listplus.ai), we process your message, your contact details and, where you have an account, your user ID, name and email address so we can match your account. There is no chat with staff in the application; questions are answered there by the AI help (see below), which can pass a conversation on to our support by email. Our mailboxes (e.g. support@listplus.ai) are run by Google Workspace (Google Cloud EMEA Limited, Dublin; section 15).

Legal basis: Art. 6(1)(b) GDPR where your request concerns the contract, otherwise Art. 6(1)(f) GDPR (legitimate interest in answering requests). Retention: until the request is fully resolved, then 24 months for traceability, unless statutory retention obligations apply.

AI help (“Ask ListPlus”)

In the application's help window and via the “Questions about ListPlus?” button on our website you can ask questions about ListPlus. The answers are given by an AI model, not a person; it answers only from our help texts and our product description. When you ask a question, we transmit to our servers and from there to the AI provider OpenAI (section 12): your question, the latest messages of the current conversation, the interface language and the address of the page you are on (without search parameters). For signed-in users the workspace's plan and credit balance are added so that the answer fits, and — when you ask in an open list — counts of that list (e.g. the number of rows, of rows with an email address or a company, of duplicate or invalid email addresses). The contents of your lists — names, addresses or other values, including the list's name — are not transmitted. Please do not enter personal data of third parties into your questions.

The conversation is kept in your browser until you close the tab. In addition we store every question and its answer for 30 days, to check the quality of the answers and to improve our help texts. These entries contain the text of your question, the answer, the language, the page address and whether the question came from a signed-in user (with their plan) or a visitor — and a random identifier of the conversation, but no user ID, no email address and no IP address. We also count how many questions are asked and how they were answered (answered, nothing found, not about the product). To limit misuse we count the questions per day: for signed-in users under the user ID, for visitors without an account under a shortened hash of the IP address; these counters contain no question text and are deleted after two days at the latest.

If the AI help cannot help, signed-in users can send the conversation to our support with one click (“Send to support”). We then receive by email the conversation, what you add, your email address, workspace, plan, the page you were last on and the browser identifier; a copy goes to your account's email address. The email is sent via Postmark (section 14).

Legal basis: Art. 6(1)(b) GDPR (help as part of the application, or pre-contractual information at your request); for the counters that limit misuse and for storing questions and answers for 30 days Art. 6(1)(f) GDPR (legitimate interest in protecting the service and in improving the answers). The owner of a workspace can switch off the AI functions, and with them the AI help, for their workspace (workspace policies).

10. Connections to other systems

When you connect a CRM, spreadsheet or other tool (e.g. HubSpot, Salesforce, Pipedrive, Google Sheets, Airtable, Notion, Lemlist, Stripe, or as an import source Apollo, Phantombuster, Intercom, Zoom, Calendly), the connector service Pipedream, LLC (Pleasanton, USA; a Workday company) manages the login credentials (OAuth) on our behalf; ListPlus itself does not store them. Requests to and transfers into the connected system run wholly or partly through Pipedream's proxy service; the transferred records pass through Pipedream's servers. Which data is transferred is determined by your actions (import, export, pipeline target); a reference list reloads from its source regularly at your request. Destinations you connect with your own API key (e.g. Instantly, Smartlead, your own webhook endpoint) we reach directly; we store the key encrypted. Legal basis: Art. 6(1)(b) GDPR; section 11 applies to the content.

Email drafts: When a customer sets up a pipeline with the target “Email draft”, ListPlus uses this connector service to create one draft per contact in the connected mailbox (Gmail or Outlook) of the person who sends (for automatic sending: the person who set up the pipeline): the contact's address and name, subject and text from the customer's template. ListPlus does not send any email; whether and when a draft is sent is decided by the user in their mail program. We read the sender's name from the connected mailbox. We store the draft's identifier and a link to it on the record (“Open in mailbox”) and, per pipeline, the email addresses a draft already went to, so that nobody gets two drafts of the same pipeline — until the pipeline is deleted. The content of the mailboxes is not read. For each person a member contacts through outreach in a list or a pipeline (email draft, LinkedIn invitation), the workspace keeps a contacted log (channel, time, member as a pseudonym, list, the person's name and identifier such as email address or LinkedIn profile) so that nobody is contacted twice; entries are deleted after 365 days. The owner of a workspace can switch email drafts off for all members (workspace policy), independently of the other connected systems. Legal basis: Art. 6(1)(b) GDPR; section 11 applies to the contact data.

Your own AI: Agent API, MCP and research link

You can connect an AI system of your choice (e.g. ChatGPT, Claude or your own agents) to ListPlus through an agent key or a sign-in for the workspace (see the next paragraph) or through a research link (listplus.ai/r/…). That AI system reads and writes only the lists the workspace's owner or an admin shares with it, within the rights given per list (visible and writable columns, sublists, permitted actions); it cannot delete records. Per shared list we store which connection may work on it, with which rights, who shared it and when. The provider of that AI system is your recipient, not our service provider: which data it receives and how it treats it is determined by your choice of provider and the lists and rights you share. Where a client has no field for a header, the access key is part of the address path and then appears in the access logs of our hosting provider.

For the whole workspace there are agent keys (REST at listplus.ai/a/…, MCP at listplus.ai/mcp): with them the AI system finds people (name, role, company, LinkedIn profile — no contact details), has records it sends checked and fields enriched. It can also search the contact database and the company database by criteria (role, place, industry, size); the people and companies found are put into a new list of the workspace (name, role, company, LinkedIn profile, place — no contact details), people who objected excluded. Standard checks do not create a list. Direct enrichment returns the updated records. Job inputs and results are available for polling for up to 48 hours. If the agent supplies an explicitly shared list and row IDs, ListPlus updates those rows in that list. Per key we store its name, creator, day budget, counters (calls, credits, last use) and the day's spend, no contents; per workspace a log of the keys' calls (action, number of records, names of the requested fields, credits — the last 200 calls for 7 days) and tasks and credits per day for 92 days. An AI client that signs in through OAuth (Claude, ChatGPT) receives access tokens we store only as hashes (valid one hour; renewal tokens 30 days); the sign-in creates an agent key with the same data as above. To verify the client we fetch its public metadata document from claude.ai or chatgpt.com. The checking of records can also be used to a limited extent without a key; for that we count calls per IP address, stored only as a hash and deleted after two days. An AI system can find people only with an agent key or a sign-in, i.e. on behalf of a workspace.

11. Customer data: ListPlus as processor

Personal data that customers process in ListPlus — such as lists from file imports, imports from LinkedIn or connected systems, enrichment results, saved contacts and Inbox entries — is processed by us on behalf of and on the instructions of the customer (Art. 28 GDPR). The customer is the controller of this data and of its use, for example for sales outreach. Data subjects should address their requests to the company using their data; if such a request reaches us, we forward it to the customer where possible.

The data processing agreement (DPA) at listplus.ai/dpa applies and is part of the user agreement for customers on every plan. A signed copy is available on request at support@listplus.ai.

Retention: lists are stored until the customer deletes them; a deletion is started at once and usually completes within minutes (copies in the daily database backups up to 7 days; if the customer sets up a “record deleted” rule, ListPlus keeps deleted rows for it for up to 30 days). Some areas are deliberately time-limited: Inbox entries are deleted 14 days after arrival, shared result links stop working 7 days after their last view (each view extends the period), AI research runs in the application are deleted 7 days after they start, runs via the customer's own AI (research link) 1 to 7 days after they start (the user's choice); a run that hands its hits to a list, 30 days from the start or from switching on the hand-over, profiles that were only viewed (not saved or enriched) drop out of “Recently viewed” after 30 days without further activity, and a pipeline’s history (records sent to a destination the customer chose, with the destination’s response) is deleted 30 days after sending. Watchlist entries, contacts from the Outlook add-in and form submissions stay until the customer deletes them.

Deleting the account: you delete your account yourself in the settings (“Delete account”). We then delete your account, every workspace you own with all its lists, files, pipelines, inboxes, research runs and watchlists, your personal data in our database and your pseudonym at PostHog with its events; running subscriptions are cancelled. What remains: invoices and the customer record at Stripe (statutory retention), a Link account if you created one when buying (it belongs to Link; you request its deletion there), data you created in workspaces owned by others (it belongs to that workspace), logs at the hosting provider until they expire (at most 30 days; they may contain your user ID), the message history at the email service (45 days), notifications about your account that went to our team until then (Slack), entries in the CRM system from before 30 October 2026, which we delete by hand on request, shared result links until 7 days after their last view, and the cross-customer caches without personal reference. Because ListPlus and ContactPlus use the same sign-in, “Delete account” also deletes your ContactPlus account and its data. A 30-day marker prevents a still-valid sign-in session from recreating the account.

12. AI processing

ListPlus uses AI models to understand commands, check and judge data, fill AI columns, detect columns on import, recognise Inbox entries and webhook records, transcribe dictation, run research and — when the customer sets it up or clicks for it — write and check texts for email drafts and suggest the company knowledge from the customer's website. The calls are made exclusively from our servers, never from your browser; the AI provider receives the part of the data the task needs — for checks only distinct values, for the features named below also whole texts or records:

  • Commands and questions: your text, column names and types, row count, the names of statuses and pipelines and the conversation so far including earlier results; only when a command needs values, the distinct values of the columns involved (duplicates removed).
  • AI checks and judge columns: only the distinct values or value combinations of the columns involved (e.g. job title, city and country); a verdict is cached for 30 days under a hash of the value (verdicts on values without personal reference, such as job titles or places, for all customers; verdicts with personal reference per workspace).
  • AI text columns: the prompt you wrote with the values of the columns it names from the respective record (up to 2,000 characters) and, where present, the record's enrichment and check details (up to 1,500 characters each, which may include email address and phone number), once per distinct combination.
  • List webhooks: unknown field names with one sample value each, so the column can be mapped; on request a spam check with up to 12 fields of 120 characters per record.
  • Business cards: if someone photographs a business card in a customer's form or in the Inbox, an AI model (OpenAI, in the EU with EU processing) reads the image to recognise name, position, company and contact details.
  • Dictation: the audio recording of your voice input (up to 3 MB) to turn it into text.
  • Column detection on import: column headers and a sample of example values (10% of the file, at least 50 and at most 200 rows) and, for advice on individual columns, up to three example values per column.
  • Inbox: To recognise people and companies in a longer entry, its text is sent to OpenAI: for forwarded emails, the email body and the text extracted from supported attachments (e.g. PDF), cut to at most about 24,000 characters. Structured entries (vCards, calendar invitations, CSV and JSON data) are read without AI extraction. Short entries (e.g. a signature line) and the recognised contact details (name, position, company, email address, location) are sent to a model via the Vercel AI Gateway for classification and a plausibility check (with EU processing OpenAI in the EU, otherwise also TypeSafe AI); to confirm a person or company, a Google search with name and company may be run (section 13).
  • AI Research: your search description, or the known identity details of a person (name, company, job title, location), to search public web sources, and the content the research reads there (web pages, imprints, public posts and comments with their authors' names) to recognise and rate hits.
  • Other single tasks: the gender from a first name (only the first name), whether two company names mean the same company (only the names), whether a LinkedIn post found fits the search (text and author of the post), for app events whether a text names a contact (the text), suggestions for an outreach template from three example records of the list, and columns a connected AI has derived via the Agent API (the values of the columns named).
  • AI help: your question to the help with the latest messages of the conversation, language and page address, for signed-in users plan and credit balance (section 9) — also from website visitors without an account.
  • AI texts in email drafts: only when the customer puts an AI text into the template of an “Email draft” pipeline. Then the AI provider receives, for each draft, the template's instructions, the briefing, the workspace's company knowledge, the sender's name and the data of the record including its enrichment data (e.g. position, career, former employers, company data, each with its date) — without email addresses and phone numbers. Without an AI text in the template no contact data is sent to an AI provider. We keep the result for one day in the workspace so the same text is not generated twice.
  • Check content: only on a click on “Check content”: subject, text and signature of the template with placeholders (no contact data), the briefing and the workspace's company knowledge.
  • Company knowledge from the website: only on a click on “Suggest” in the settings (Company knowledge): ListPlus fetches the customer's website — the home page and up to four linked public pages, no legal or login pages — and sends their text for evaluation. We store the company knowledge (information about the customer's own company, its products, audiences and proof) in the workspace until the customer changes it or deletes the workspace.

Providers and place of processing: Every call of a language model goes through the AI Gateway of Vercel Inc. (contracting party: Vercel; data processing agreement with Standard Contractual Clauses). By default every call is pinned to data centres in the EU (regional inference): the model provider processes the request there and, to the extent it stores anything at all, stores it there. According to Vercel, a request the EU cannot serve fails instead of running elsewhere; we check the region reported for every answer and log deviations. What is not pinned is the way to the gateway itself: according to Vercel a request can be accepted and processed in any Vercel region before the gateway forwards it to the provider; the gateway keeps no prompts or answers. In both modes we instruct the gateway to use only providers that do not train on the data and keep nothing after the request (zero data retention); OpenAI additionally receives the “do not store” setting. The exception are requests a provider flags for abuse or safety review: it may retain those under its own policy, possibly outside the chosen region. The models: OpenAI (language models; through the gateway in EU data centres) and TypeSafe AI (judgement model “Jev”, TypeSafe AI, Inc., USA; it has no EU region and, with EU processing, receives only job titles and positions (title with company name, without the person's name) — Inbox entries, webhook records, judge columns and names are then judged by OpenAI in the EU). A workspace owner can switch on “AI models outside the EU” (workspace policy): the gateway then picks the region per request (the USA among them), TypeSafe AI also judges values that identify people, and dictation becomes available — the transcription of dictations runs directly at OpenAI (OpenAI Ireland Ltd., Dublin; Standard Contractual Clauses; USA), because no transcription model with an EU region exists yet; with EU processing, dictation is switched off. Seat, data location and safeguard per provider are in section 15. A workspace owner can switch all AI features off for the workspace (workspace policy); no AI provider is called then. AI Act: the AI features serve to maintain and check business contact and company data and to find business contacts; they are not high-risk AI systems within the meaning of Regulation (EU) 2024/1689 and are not intended for selecting applicants or employees. The AI help discloses that it is an AI. Models, data flows, classification and risk assessment are described in Annex 4 of our data processing agreement (listplus.ai/dpa). Legal basis: for customer data we act as processor (section 11); otherwise Art. 6(1)(b) GDPR. No automated decision-making with legal or similarly significant effects within the meaning of Art. 22 GDPR takes place; AI results (including judgements such as seniority or a “fit” score in research) are suggestions that the user reviews and applies. The research fit score describes how well a hit matches the customer's search description; a workspace owner can switch this rating off (workspace policy), after which no hit is rated.

Web index in the person search (outside the EU): Besides Google search (Serper), the contact search asks the web index of Parallel Web Systems, Inc. (Palo Alto, USA) for the searched person's LinkedIn profile; the search term (name, role, company, place) is transmitted. The same applies to the recognition in the Inbox: for the contacts recognised there (e.g. from forwarded emails, calendar invitations or app events), name, role and company are likewise passed to Google and Parallel. The web and news searches of the AI research, the news in a profile and the Agent API's Google search use Parallel's web index too (the search term is transmitted), because since October 2026 Google lets only the first three result links of a search be opened. This is on by default; the workspace owner can switch it off under Settings → Privacy ("Parallel"), and ListPlus then searches through Google only. It rests on the same data processing addendum with EU Standard Contractual Clauses as below.

Web research on click (outside the EU): The company brief in the contact search and the questions about a company or person are carried out by Parallel Web Systems, Inc. (Palo Alto, USA) — an AI-assisted research service that reads public web pages and backs every statement with a source. This research runs outside the EU even when the workspace is set to EU processing, and only when a user clicks it explicitly; the note "Research runs outside the EU" is on the button. Transmitted are the company name and domain, for a question about a person their name, role and LinkedIn URL, and the question. It rests on a data processing addendum with EU Standard Contractual Clauses; the provider retains requests under its privacy policy for as long as the service needs.

13. Data providers and data enrichment (information under Art. 14 GDPR)

ListPlus lets customers search for, complete and verify business contact and company data. This data does not come from ListPlus itself — ListPlus owns no contact database of its own — but is retrieved at the moment of the request from specialised data providers or from publicly available sources. If your business contact data has been retrieved through ListPlus, this section informs you about the processing.

Categories of data

Name, job title and seniority, company and company data (industry, size, location, website, funding, technologies), business email address and its deliverability status, business phone number and, where applicable, mobile number, LinkedIn profile URL, location, and publicly visible profile details (e.g. career history, past employers) as well as public posts, comments or reactions where a customer retrieves them. In AI research, in addition: the source (URL), a short piece of evidence (e.g. the comment that led to the hit) and an estimate of how well the person matches the search description (“fit”, 0–100, with a reason).

Sources

The data comes from data providers that run their own databases of business contacts — Prospeo (contact database, email and phone), FullEnrich (email and phone), CompanyEnrich (company data), Crustdata (company identification by domain; only the domain), MillionVerifier (deliverability), HarvestAPI (publicly visible LinkedIn data), Serper (Google search results), The Companies API (company data when CompanyEnrich has none; only the domain), Parallel Web Systems (web index beside Google in the person search, Inbox, AI research, news and Agent API, can be switched off; web research with cited sources for the company brief and the questions about a company or person on an explicit click — in the USA, see section 12) — and from publicly accessible sources that a service reads at the customer's request: LinkedIn (search results, employee lists, posts, comments and reactions, profile search including by past employer), Crunchbase company pages, Reddit, X, Hacker News (search via Algolia, only the search term), Google Maps profiles, web traffic estimates and arbitrary websites, also to find contact details. These public sources are read by the data collection platform Apify (Prague) with third-party programs (“actors”); the platforms themselves are not our contracting partners. The complete, current list with seat, data transmitted and safeguard is at listplus.ai/en/subprocessors, Part B.

The data providers are responsible for their own data sets; information on their processing is available in their respective privacy notices. A workspace owner can switch individual providers and sources off for the workspace (workspace policy).

Purposes, recipients and legal basis

The data is retrieved when a customer triggers a specific search or enrichment and is provided only to that customer, who uses it for their own business purposes (e.g. sales, maintaining CRM data). We send the data provider only the search key needed for the lookup (e.g. email address, domain, LinkedIn URL, name and company, or search filters), never the rest of the customer's list. The customer's legal basis for the retrieval is usually Art. 6(1)(f) GDPR: its legitimate interest in finding business contacts and maintaining accurate business data; it is limited to data in a professional context. ListPlus pursues no purposes of its own with these retrievals. Personal enrichment results (email addresses, phone numbers, job titles) are not shared between customers. For retrievals a customer triggers, we act as that customer's processor and transmit the search key to the data provider on the customer's instruction; providers with a data processing agreement process it as our further processors only to answer the query; the data providers are controllers of their own databases (DPA § 2(3)).

Outlook add-in

If a customer uses the Outlook add-in, it sends the name and email address of the correspondent currently opened to ListPlus, which retrieves data about them as in an enrichment and stores them in an “Outlook Contacts” list of the workspace until the customer deletes them.

Browser extension for Chrome

ListPlus browser extension for Chrome. The extension stores the people, companies and pages a user saves only locally in their browser (chrome.storage). Page content is read only on the user's click and processed with Chrome's built-in on-device AI model; it is not transferred to us. The extension reads details from LinkedIn pages only when the user turns this on. Only when the user hands entries over to ListPlus are the selected entries (name, profile address, role, company, location, contact data, notes if chosen) transferred to their ListPlus workspace and processed like other list data (section 11); if they request an enrichment, the providers named in this section apply. If the user hands entries over to their own endpoint, the extension sends them directly to the address the user entered; we do not receive this data. To sign in, the extension uses the existing ListPlus session in the browser. Legal basis: Art. 6(1)(b) GDPR (hand-over to ListPlus); local storage involves no transfer to us.

The extension's own HubSpot connection. If the user connects their HubSpot account in the extension's settings, the extension checks on LinkedIn profiles whether the person already exists there as a contact, and creates contacts or adds their LinkedIn address only on the user's click. For this the extension talks to HubSpot directly from the browser: for the check, the profile address and the person's name go to HubSpot; when creating, the details the user confirms in the dialog (name, e-mail address, job title, company, LinkedIn address; e-mail and job title come, where available, from an enrichment the user ran before). This data and HubSpot's answers do not reach ListPlus; no ListPlus account is needed. Only the exchange of the access credentials with HubSpot (authorization code, access and refresh token) passes through our server, because HubSpot requires our app's secret for it; the server neither stores nor logs this data, it only counts requests to limit misuse (by IP address and a hash of the token, for a few minutes). The tokens and a cache of the check results stay in the user's browser only. "Disconnect" revokes the access at HubSpot and deletes the data in the browser; the app can also be removed in HubSpot under Connected apps. The customer is responsible for the data in their HubSpot account; HubSpot processes it under its own terms. Legal basis: Art. 6(1)(b) GDPR (the connection the user sets up); for limiting misuse Art. 6(1)(f) GDPR.

Retention

Results added to a customer's list are stored until the customer deletes them (section 11). Lookup results about people are cached only in the respective customer's workspace to avoid duplicate lookups: 30 days from the retrieval at the provider. Company data for a domain (name, industry, size, location, website, technologies, funding, address and phone of the headquarters — no details about people) is kept in a company cache shared across customers for 30 days from retrieval; a workspace can switch off contributing to this cache. We are the controller of this cache (Art. 6(1)(f) GDPR; our interest is not to request the same company data again for every customer). For sole traders, company name, address and phone may exceptionally relate to a person.

Your rights

You have the rights listed in section 18, in particular the right to object to the processing of your data at any time. To do so, contact support@listplus.ai. Where a customer processes your data in its own lists or contacts you, that customer is the controller; your objection to direct marketing should then be addressed to that customer. A short version of this information addressed to you is at listplus.ai/en/contact-data-notice. An objection is entered into a suppression list that applies to all customers: your data is then no longer retrieved from data providers through ListPlus and no longer shown as a hit of a search or research. A lookup only by name and company cannot be matched before the provider answers; data a customer already holds is handled by that customer.

Suppression list: we keep the suppression list as controller (Art. 6(1)(c) GDPR in conjunction with Art. 21 GDPR, alternatively (f): our interest in honouring objections permanently and for all customers). It contains only checksums (SHA-256) of your email address or LinkedIn address, applies to ListPlus and ContactPlus and is kept for as long as you do not withdraw your objection.

14. Email receiving and sending (Postmark)

Users can forward emails to a personal address at @in.listplus.ai so that ListPlus recognises contact details in them (e.g. from signatures, vCards or calendar invitations). These emails are received via the Postmark service (ActiveCampaign, LLC, formerly Wildbit, USA). Postmark accepts the email and passes its content to us as structured data (JSON). We process sender, recipient, subject, body and supported attachments of the forwarded email; third-party data contained in it is processed by us as the user's processor (section 11). To recognise contacts, the content is sent to AI providers (section 12).

Through the same service we send, from notifications@listplus.ai, workspace invitations (the invitee's address, the inviter's name, the workspace name) and, when a customer sets up a pipeline with the “Email” target, digest mails to members of the workspace with the name, position and company of each entry and a link to its contact card (the links work for 30 days), as well as support requests from the AI help to our support. Sign-in codes are sent by the sign-in service (section 6), not by Postmark. A workspace owner can switch the Inbox address and pipeline emails off.

Legal basis: Art. 6(1)(b) GDPR (providing the feature the user uses). Third-country transfer: we base the transfer to Postmark in the USA on the EU Standard Contractual Clauses (Art. 46(2)(c) GDPR). Postmark is also certified under the EU-U.S. Data Privacy Framework (Art. 45 GDPR); the data processing agreement is part of Postmark's terms of service. Retention: Postmark keeps messages for 45 days by default. Inbox entries are deleted automatically on our side 14 days after arrival; contacts the user saves or adds to a list are kept.

14a. List webhooks and forms

A customer can set up a webhook per list (an address at listplus.ai/i/…) to which other systems send records, and publish a form (listplus.ai/f/…) that visitors of the customer's website fill in. We process the data arriving this way as the customer's processor (section 11); the customer is the controller towards the data subjects and informs them. Records pass through the queues of our hosting provider; unknown field names and, on request, a spam check go to AI models (section 12); doubtful records can be held back in the customer's Inbox.

For a form we store, per submission, the page it is embedded in, with a consent checkbox the consent and its time, and for two minutes a shortened hash of the visitor's IP address to limit mass submissions (for two days when a business card is photographed; an AI model reads the image, section 12); we serve the fonts ourselves, no third-party content is loaded. The form's consent text is a suggestion to the customer, not legal advice. Legal basis: Art. 6(1)(b) GDPR towards the customer; for abuse limitation Art. 6(1)(f) GDPR.

15. Recipients and subprocessors

We only pass on personal data where this is necessary for the purposes described. Within our company, only people who need access for their tasks have it. We use the following service providers:

Part A: Sub-processors

Service providerServiceData transmittedAddress / locationThird-country safeguard, contract
Vercel Inc.Running the application, file storage for lists and imports, queues for background work, web analytics and speed insights, AI Gateway: every call of an AI model (OpenAI, TypeSafe AI) goes through the gateway — by default with regional inference in the EU, without training and without retention at the providerAll data of the application; connection data on every request (IP address, browser)440 N Barranca Ave #4133, Covina, CA 91723, USA — Hosting, file storage and queues in the EU region Frankfurt. The AI Gateway accepts a request in any Vercel region and forwards it to the model provider in the chosen region (according to Vercel the gateway hop itself is not pinned to a region); the gateway keeps no prompts or answersEU-U.S. Data Privacy Framework; Standard Contractual Clauses in the data processing agreement — Contract: vercel.com/legal/dpa
Redis EMEA Ltd. (Redis Cloud)The application's database: workspaces, lists, working data, cachesAll data of the applicationBridge House, 4 Borough High Street, London SE1 9QQ, United Kingdom (contracting entity for customers in Europe; parent company Redis Ltd., Alon 2 Tower, 94 Yigal Alon St., Tel Aviv 6789140, Israel) — Databases in Frankfurt (AWS eu-central-1), encrypted at rest, transport TLS-encryptedProcessing in the EU; United Kingdom and Israel: adequacy decision; Standard Contractual Clauses (modules 2 and 3) in the provider's data processing agreement (part of the Redis Cloud Agreement) for support access from other third countries — Contract: redis.io/legal/data-processing-addendum-dpa
Amazon Web Services EMEA SARL (Amazon S3)Daily backup of the database; every backup is deleted after 7 daysAll data of the database at the time of the backup38 Avenue John F. Kennedy, L-1855 Luxembourg — Own storage (S3 bucket) in Frankfurt (eu-central-1), encrypted, no public accessProcessing in the EU; Amazon is certified under the EU-U.S. Data Privacy Framework; Standard Contractual Clauses in AWS's data processing addendum (part of the AWS Service Terms) — Contract: AWS GDPR Data Processing Addendum, aws.amazon.com/service-terms
Bird B.V. (Pusher)Live status updates in the browser (import done, enrichment running, new hits)Events about operations; for small changes the changed cell valuesKeizersgracht 268, 1016 EV Amsterdam, Netherlands (contracting entity for customers outside the USA; the Pusher service is run by the Bird company MessageBird UK Limited, formerly Pusher Ltd., 3 More London Riverside, London SE1 2AQ, United Kingdom) — Cluster “eu”: AWS eu-west-1 (Ireland)Contracting party in the EU; processing in the EU cluster (Ireland); United Kingdom: adequacy decision; Standard Contractual Clauses (modules 2 and 3) in Bird's data processing agreement for transfers to other third countries — Contract: bird.com/legal/dpa
Pipedream, LLCConnections to CRM systems and spreadsheets (OAuth credentials, forwarding of calls); creating email drafts in the user's connected mailbox (Gmail, Outlook) — never sending; delivery of app events from connected apps (form answers, bookings, messages)Records the customer exchanges with a connected system (for email drafts the contact's address and name, subject and text); the content of the app events the customer sets up6110 Stoneridge Mall Road, Pleasanton, CA 94588, USA (a Workday company)Standard Contractual Clauses (modules 2 and 3) in the provider's data processing agreement; not certified under the EU-U.S. Data Privacy Framework — Contract: pipedream.com/dpa
Postmark (AC PM LLC, ActiveCampaign)Receiving e-mails forwarded to the Inbox address @in.listplus.ai; sending workspace invitations and pipeline digest mails from notifications@listplus.ai; sending support requests from the AI help to our supportForwarded e-mails in full (sender, subject, body, attachments); the invitee's address and the inviter's name; per digest entry name, position, company; for a support request the conversation, the user's e-mail address, workspace, plan and page1 N Dearborn Street, Suite 500, Chicago, IL 60602, USAEU-U.S. Data Privacy Framework (ActiveCampaign, LLC including AC PM LLC); Standard Contractual Clauses in the data processing agreement that is part of Postmark's terms of service — Contract: postmarkapp.com/dpa
OpenAILanguage models for commands, checks, AI columns, column recognition on import, understanding a search query, list titles, recognition of contacts in the Inbox, mapping of unknown webhook fields, AI research, AI help; transcription of dictationsThe excerpt the task needs (section “AI processing” of the privacy policy); language models through the gateway with “no training”, zero data retention and “do not store” (store: false) — requests flagged as possible abuse may be kept by the provider under its own rules; for transcription (directly at OpenAI) the provider keeps abuse-monitoring logs for up to 30 daysOpenAI Ireland Ltd., 1st Floor, The Liffey Trust Centre, 117–126 Sheriff Street Upper, Dublin 1, D01 YC43, Ireland (contracting entity for the EU); processing also by OpenAI OpCo, LLC, 1455 3rd Street, San Francisco, CA 94158, USA — Language models: processing in EU data centres by default (regional inference through Vercel's AI Gateway); processing in the region the gateway picks only when the workspace owner switches “AI models outside the EU” on. Transcription of dictations: only with that setting, directly at OpenAI (USA)Language models through Vercel's AI Gateway: the contracting party is Vercel (data processing agreement with Standard Contractual Clauses); OpenAI works for Vercel under zero data retention and no-training agreements. Transcription: Standard Contractual Clauses in the Data Processing Addendum with OpenAI Ireland Ltd., which is part of the OpenAI Services Agreement (OpenAI is not certified under the EU-U.S. Data Privacy Framework) — Contract: vercel.com/legal/dpa; openai.com/policies/data-processing-addendum
TypeSafe AI (model “Jev”, via Vercel's AI Gateway)Judgement model: seniority of job titles, kind of a LinkedIn position; only with “AI models outside the EU” also the pre-check of Inbox entries and webhook records, judge columns, name splittingThe values to judge (job titles and positions with the company name; with “AI models outside the EU” also names and up to 12 fields of a record); without storage at the provider (zero data retention); according to the provider not used for trainingTypeSafe AI, Inc., 255 California Street, Suite 1300, San Francisco, California, USA (address as stated in the provider's terms) — Processing in the USA (the model has no EU region). With EU processing (the default) it receives only job titles and positions (title with company name), without the person's name; Inbox entries, webhook records and judge columns then go to OpenAI in the EU. All tasks only when the workspace owner switches “AI models outside the EU” onThrough Vercel's AI Gateway: the contracting party is Vercel (data processing agreement with Standard Contractual Clauses); TypeSafe works for Vercel under a zero data retention agreement — Contract: vercel.com/legal/dpa
Apify Technologies s.r.o.Data collection platform: runs scrapers (“actors”) that read public pages — LinkedIn imports (Sales Navigator, employee lists, post reactions and comments, people search incl. by past employer), Crunchbase company pages, Reddit, X, Google Maps profiles, web traffic, contact details on websitesThe search URL, company URL, post URL, company name or research query — never the customer's list; actors by other developers run on Apify's infrastructure under Apify's termsNa Příkopě 959/27, 110 00 Prague 1, Czech RepublicProcessing mainly in the EU and the USA; Standard Contractual Clauses in the provider's data processing agreement — Contract: docs.apify.com/legal/data-processing-addendum
PostHog Inc. (EU cloud)Usage events of the application (which feature was used when), pseudonymousEvent name and properties, a pseudonym of the account (hash), plan, workspace hash; no names, e-mail addresses or list contents; can be switched off per account and per workspace2261 Market St., #4008, San Francisco, CA 94114, USA — EU cloud in FrankfurtProcessing in the EU; EU-U.S. Data Privacy Framework and Standard Contractual Clauses (module 2) in the signed data processing agreement (19 October 2026)
Hanko GmbHSign-in: e-mail address with one-time code or Google login; sessions (30 days)E-mail address, user id, sign-in method, timestampsRingstraße 19, 24114 Kiel, Germany — Data centres in Germany onlyProcessing in the EU
Google LLC (Sign in with Google)Confirming the sign-in when the user chooses “Sign in with Google”E-mail address and Google account id; Google learns that the person signs in to ListPlus1600 Amphitheatre Parkway, Mountain View, CA 94043, USAEU-U.S. Data Privacy Framework
Sold Through Link, LLC and Stripe (Stripe Managed Payments)Handling the sale of plans and credits on our behalf as merchant of record: checkout, payment processing, invoices and receipts, VAT, refunds, payment disputes, fraud prevention, the buyer's Link account. Independent controllers for the purchase and the Link account, not only processorsFrom us: e-mail address, user id, purchased product and price; in the checkout the buyer enters name, billing address and payment data directly with Stripe/LinkSold Through Link, LLC (formerly Lemon Squeezy, LLC): South San Francisco, California, USA; payment processing in the EU: Stripe Technology Europe, Limited, Dublin, IrelandStripe's Data Transfers Addendum (part of Stripe's data processing agreement): primarily the EU-U.S. Data Privacy Framework (Stripe, LLC is certified), otherwise Standard Contractual Clauses (module 1); the addendum also covers Stripe's affiliates, including Sold Through Link, LLC
Attio Ltd. (CRM)Customer care: the account with e-mail address, plan and key account events; sends the welcome e-mailE-mail address, user ID, plan, account eventsLondon, United KingdomAdequacy decision for the United Kingdom
n8n GmbH (n8n Cloud)Internal notifications to our team via Slack about key account eventsE-mail address, user ID, account event (e.g. purchase, failed payment, refund, cancellation, newly connected tool, account deletion) with amount or app; questions the AI help could not answer (without user ID or e-mail address)Berlin, Germany — Hosting in the EU (Frankfurt am Main)Processing in the EU
Google Cloud EMEA Limited (Google Workspace)Our mailboxes (e.g. support@listplus.ai): support requests, data subject requests, AI help conversations sent to supportContent of e-mails to us (sender, text, attachments); for “Send to support” the conversation, e-mail address, workspace, plan and pageVelasco, Clanwilliam Place, Dublin 2, Ireland — Google's data centres, also outside the EUContracting party in the EU; Google LLC is certified under the EU-U.S. Data Privacy Framework; Standard Contractual Clauses in Google's data processing agreement (Cloud Data Processing Addendum) — Contract: cloud.google.com/terms/data-processing-addendum
Slack Technologies Limited (Slack)Receiving our internal notifications about account events (via n8n)As for n8n: e-mail address, user ID, account event with amount or app; questions the AI help could not answer (without user ID or e-mail address)Salesforce Tower, 60 R801, North Dock, Dublin, Ireland (contracting entity for workspaces outside the USA and Canada; Salesforce group)Contracting party in the EU; Standard Contractual Clauses for transfers outside the EU (according to Slack's privacy policy)
Parallel Web Systems, Inc.Web search beside Google (can be switched off): the person search and the Inbox recognition for the LinkedIn profile, the web and news searches of the AI research, the news in a profile and the Agent API's Google search; web research with cited sources on an explicit click: the company brief (status, legal name, register entry, directors, funding, news) and the questions about a company or person in a profileThe search term (name, role, company, place, research topic); company name and domain; for a question about a person their name, role and LinkedIn URL; the question itself735 Emerson St, Palo Alto, CA 94301, USA — Processing in the USA (no EU option for the research API)Data processing addendum with EU Standard Contractual Clauses (modules two and three); not certified under the EU-U.S. Data Privacy Framework; SOC 2 Type II — Contract: parallel.ai/legal/dpa

Part B: Data providers and sources

On a lookup these providers receive only the search key (e.g. e-mail address, domain, LinkedIn URL, name and company or search filters), never the rest of the list. Providers with a data processing agreement (column “contract”) process the search key only to answer the query, as further processors of ListPlus; for their own databases all providers are independent controllers. Providers without a data processing agreement receive the search key as recipients on the customer's instruction (DPA § 2(3)). “Switch off” names the workspace policy switch with which the customer switches a provider off for its workspace.

Service providerServiceData transmittedAddress / locationThird-country safeguard, contract
ProspeoB2B contact database (segment search), verified business e-mail addresses and phone numbers, company profiles, job changesSearch filters or the search key: LinkedIn URL, name and company, domainDefastra Tech Inc. (Prospeo), 1102-20 Eglinton Ave W, Toronto, ON M4R 1K8, Canada; EU representative: Kevin Viotti, 20 Rue de Belleville, 75020 Paris, France — Hosting in the USA (AWS us-east-1)Canada: adequacy decision; USA (hosting): Standard Contractual Clauses in the provider's data processing agreement — Contract: prospeo.io/dpa
FullEnrichBusiness e-mail address and phone number from name and company or LinkedIn URL (waterfall through 20+ sources)Name and company, domain or LinkedIn URLFullEnrich Corp., 28 Geary St, STE 650, Suite #346, San Francisco, CA 94108, USAStandard Contractual Clauses (modules 2 and 3) in the provider's data processing agreement — Contract: fullenrich.com/data-processing-agreement
CompanyEnrichCompany data from domain or company name (industry, size, location, website); workforce, decision makers, similar companiesDomain or company name; for person lookups name and companySTDİO Bilişim San. ve Tic. Ltd. Şti., Bahçelievler Mah. 91 Sk. No: 1, Gölbaşı, Ankara, Türkiye — Servers, databases and backups in Finland (Hetzner, Helsinki)Processing in the EU (Finland); for Türkiye (no adequacy decision) Standard Contractual Clauses (modules 2 and 3) in the provider's terms — Contract: companyenrich.com/dpa
CrustdataCompany identification by domain (LinkedIn company page, name, size class) for enrichmentOnly the company domain; no personal dataCrustdata Technologies Inc., 95 Third Street, 2nd Floor, San Francisco, CA 94103, USA — Data in the USANo transfer of personal data (company domains only)
The Companies APICompany data for a domain when CompanyEnrich returns nothing (fallback provider)Only the company domainThe Companies API, France (according to the provider's privacy policy; the provider names neither its company nor an address)Seat in the EU (France); the provider names no place of processing or contract
HarvestAPIPublicly visible LinkedIn data: profile, company, profile search, posts and reactions, open jobsLinkedIn URL, name and company, post URLAventra Technologies Limited (HarvestAPI), Flat 5, 4/F, Won Hing Building, 74–78 Stanley Street, Central, Hong Kong — processing in the USA (Google Cloud); logs with the request for at most 30 days, profile data cached for at most 10 minutesHong Kong and USA (no adequacy decision): EU Standard Contractual Clauses (Modules 2 and 3) in the provider's data processing agreement, which also covers its Actors on Apify — Contract: Data Processing Agreement of Aventra Technologies Limited (available from us on request)
MillionVerifierChecking whether an e-mail address is deliverableThe e-mail addressSouthern Vector Limited, 26 Applefield Court, Northwood, Christchurch 8051, New Zealand — Processing in New Zealand, Hungary and other EEA countries, the USA and other countriesNew Zealand: adequacy decision; onward transfers according to the provider under contractual safeguards of comparable protection (no Standard Contractual Clauses named) — Contract: millionverifier.com/policies/data-processing-agreement
Serper (Google search)Google search results: LinkedIn profile URL for name and company, company website, news, web search of the AI research, confirmation of recognised contacts in the InboxThe search term (e.g. name and company). In the provider's logs the search term is masked for our account; the provider keeps time, our server's IP address and usage without a set retention periodSerper (serper.dev; the provider does not name its company or an address, also on request; terms under the law of the United Kingdom) — processing in the USA and Singapore; the provider forwards every query to Google in real timeUSA and Singapore (no adequacy decision); no data processing agreement and no Standard Contractual Clauses (the provider offers them to large customers only)
Hacker News (search via Algolia)Public stories and comments on Hacker News including user names, for the AI researchOnly the search term, never data from customer listsAlgolia, Inc., 3790 El Camino Real, Unit #518, Palo Alto, CA 94306, USA — public interface without an accountNo contract; only the search term is transmitted
Public sources (read via Apify)Publicly visible pages a scraper reads at the customer's request; the platforms are not our contracting partners, the customer observes their termsThe URL or search calledLinkedIn, Crunchbase, Reddit, X, Google Maps, Similarweb, arbitrary websitesNot applicable (retrieval of public pages)

Part C: Recipients chosen by the customer

Systems the customer transfers data to because it connects or names them itself. The customer is the controller of that transfer; they are listed for completeness.

Service providerServiceData transmittedAddress / locationThird-country safeguard, contract
The customer's connected systemsImport from and export to systems the customer connects; pipeline targetsThe records the customer transfersHubSpot, Salesforce, Pipedrive, Attio, Close, Slack, Google Sheets, Airtable, Notion, lemlist, Instantly as a pipeline target (via Pipedream); Instantly and Smartlead in the export (with the customer's key)The customer is the controller of this transfer
The customer's own webhook endpointPipeline target “endpoint”The records the customer transfersNamed by the customerThe customer is the controller of this transfer
The customer's own AI (Agent API, MCP, research link)Reading and writing lists and research through an AI system the customer connectsWhat the connection exposes (columns, sublists, actions)Chosen by the customer, e.g. ChatGPT, Claude, own agentsThe customer is the controller of this transfer

We have concluded data processing agreements under Art. 28 GDPR with service providers acting on our behalf; for most of them it is part of the provider's terms of service. The current list with seat, data location and safeguard is published at listplus.ai/en/subprocessors; it is also Annex 3 of our data processing agreement. Beyond that, we only disclose data where we are legally obliged to (e.g. to authorities or tax advisers under statutory obligations).

16. Transfers to third countries

Some of the service providers listed are based outside the EU/EEA, in particular in the USA, or use subcontractors there. We host the application in the EU region Frankfurt but cannot rule out that data is transferred to third countries. We transfer data to service providers working on our behalf (section 15, Part A) only where there is an adequacy decision of the European Commission (e.g. for companies certified under the EU-U.S. Data Privacy Framework, Art. 45 GDPR) or appropriate safeguards are in place, in particular EU Standard Contractual Clauses (Art. 46(2)(c) GDPR). Data providers (Part B) receive only the search key of a retrieval a customer triggers: providers with a data processing agreement as our further processors (with Standard Contractual Clauses where they are based or process in a third country), the others as recipients, for whose transfer the customer is responsible. Some of these providers name no transfer safeguard (Serper in the USA and Singapore, without a contract and without naming its company; the Hacker News search via Algolia without a contract); this is stated in Part B, and a workspace owner can switch each of them off. You can request a copy of the safeguards at support@listplus.ai.

17. Retention at a glance

DataRetention
Account and usage dataFor the duration of the user relationship; deleted after account deletion
Lists and saved contactsUntil deleted by the customer or until account deletion
Inbox entries14 days after arrival
Forwarded emails at the receiving service Postmark45 days (provider default)
Shared result links7 days after the last view
Contacted log of the workspace365 days
Suppression list after an objection (checksums only)Until you withdraw the objection
AI research runsIn the application 7 days from start; via your own AI (research link) 1 to 7 days, the user's choice; 30 days when hits are handed to a list (from the start or from switching on the hand-over)
Watchlist, Outlook contacts, form submissionsUntil deleted by the customer
Profiles only viewed (“Recently viewed”)30 days after last activity
Pipeline history (records sent and responses)30 days after sending
Cached lookup results about people (per workspace)30 days from the retrieval at the provider
Company cache (shared across customers, no personal reference)30 days from retrieval
Usage events (PostHog, pseudonymous)Until the account is deleted, at most 7 years (the provider's period)
Invoices and accounting recordsStatutory retention periods: vouchers 8 years, books 10 years
Server log files and error reports at the hosting providerAt most 30 days
Conversations with the AI helpIn your browser until you close the tab; questions and answers with us for 30 days, without a user identifier
Counters of the AI help (questions per day; for visitors under a shortened hash of the IP address)2 days at most
Support requests24 months after the request is closed

We have no feature to restore deleted data. The database is backed up daily; every backup is deleted after 7 days. Until then, deleted data may still be contained in a backup.

18. Your rights

You have the following rights towards us regarding your personal data:

  • Right of access (Art. 15 GDPR), including any available information about the source of the data
  • Right to rectification (Art. 16 GDPR)
  • Right to erasure (Art. 17 GDPR)
  • Right to restriction of processing (Art. 18 GDPR)
  • Right to data portability (Art. 20 GDPR)
  • Right to withdraw consent with effect for the future (Art. 7(3) GDPR)

To exercise your rights, a message to support@listplus.ai is enough. We respond without undue delay and at the latest within one month; for many or complex requests the period can be extended by two months, of which we inform you (Art. 12(3) GDPR). If there are reasonable doubts about your identity, we may ask for additional information (Art. 12(6) GDPR).

Right to lodge a complaint (Art. 77 GDPR): you have the right to lodge a complaint with a data protection supervisory authority. The authority responsible for us is the Bavarian State Office for Data Protection Supervision (BayLDA), Promenade 18, 91522 Ansbach, Germany, www.lda.bayern.de.

18a. Right to object (Art. 21 GDPR)

You have the right to object at any time, on grounds relating to your particular situation, to the processing of your data where we process it on the basis of Art. 6(1)(f) GDPR. This concerns in particular: server log files and reach measurement (sections 4 and 5), usage events (section 5), account events in the CRM system (section 7), the counters and the log of the AI help (section 9), the company cache and the suppression list (section 13) and abuse limitation for forms (section 14a). We then no longer process the data unless we can demonstrate compelling legitimate grounds that override your interests, or the processing serves the establishment, exercise or defence of legal claims.

Where your data is processed for direct marketing, you can object at any time without giving reasons; the data will then no longer be processed for that purpose. You object to the retrieval of your business contact data through ListPlus with a message to support@listplus.ai; we enter you into the suppression list (section 13).

19. Obligation to provide data

Providing your email address is required for registration; without it we cannot set up an account. Payment details are required to subscribe to a paid plan or buy credits. Otherwise you are under no obligation to provide us with data.

20. Data security

Every transmission — between your browser and us, between our servers and the database, and to every service provider — is encrypted (TLS). Files are stored encrypted at our hosting provider; the database (Redis Cloud) is also encrypted at rest. API and AI keys are used on the server only; access keys customers store for their own destinations are stored encrypted. Access to lists requires sign-in and is limited to the members of the respective workspace. ListPlus itself holds no security certification of its own; our hosting provider Vercel is certified to ISO 27001:2022, among others, and has a SOC 2 Type 2 report.

21. Changes to this privacy policy

We update this privacy policy when our service or the legal situation changes. The version published on this page applies.

ListPlus

Contacts ready for what comes next.

Product

How it worksUse CasesGTM RecipesFind leadsFlowsData qualityEnrich dataIntegrationsAI agentsAI in ListPlusPricingChrome extensionOutlook Add-in

Guides

All topicsHubSpot EnrichmentClay alternativeGTM EngineeringAgent API (developers)

Company

BlogHelp centerContactStatus

Legal

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