Service providers and data sources
Last updated: 10 November 2026
This English version is a convenience translation. The German version is legally binding.
This list is Annex 3 of our data processing agreement (listplus.ai/en/dpa) and the “Recipients” section of our privacy policy in one — generated from a single source so that there are never two versions. Changes of sub-processors are announced to customers 30 days ahead (DPA § 7).
“Customer can switch off” names the workspace policy switch with which a workspace owner stops transfers to this provider for its workspace.
Jurisdiction and protection against access from third countries (Art. 28 Data Act): ListPlus is operated by salesperformer GmbH (Germany). The application, database and file storage run in the EU region Frankfurt at Vercel Inc. (USA) and Redis Cloud on Amazon Web Services; the infrastructure is subject to EU and German law and, because its operators belong to US groups, also to US law. We encrypt transmissions and stored data, store in the EU, grant access only as needed and review every request of an authority of a third country for lawfulness; we disclose only the minimum and inform the customer beforehand where permitted (Art. 32 Data Act, DPA § 8a). Sub-processors under Standard Contractual Clauses must report such requests to us under Clause 15 of those clauses.
Part A: Sub-processors
These providers process customer data on our behalf under Art. 28 GDPR. Each row gives the contracting entity’s full postal address and the data processing agreement that contains the Standard Contractual Clauses. “Switch off” names the workspace policy switch with which the customer stops transfers to this provider for its workspace.
| Service provider | Service | Data transmitted | Address / location | Third-country safeguard, contract | Customer can switch off |
|---|---|---|---|---|---|
| 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 provider | All 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 answers | EU-U.S. Data Privacy Framework; Standard Contractual Clauses in the data processing agreement — Contract: vercel.com/legal/dpa | no |
| Redis EMEA Ltd. (Redis Cloud) | The application's database: workspaces, lists, working data, caches | All data of the application | Bridge 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-encrypted | Processing 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 | no |
| Amazon Web Services EMEA SARL (Amazon S3) | Daily backup of the database; every backup is deleted after 7 days | All data of the database at the time of the backup | 38 Avenue John F. Kennedy, L-1855 Luxembourg — Own storage (S3 bucket) in Frankfurt (eu-central-1), encrypted, no public access | Processing 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 | no |
| 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 values | Keizersgracht 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 | no |
| Pipedream, LLC | Connections 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 up | 6110 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 | yes: Connected systems |
| 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 support | Forwarded 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 page | 1 N Dearborn Street, Suite 500, Chicago, IL 60602, USA | EU-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 | yes: Inbox address, Team e-mails |
| OpenAI | Language 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 dictations | The 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 days | OpenAI 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 | yes: AI features |
| 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 splitting | The 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 training | TypeSafe 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” on | Through 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 | yes: AI features |
| 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 websites | The 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 terms | Na Příkopě 959/27, 110 00 Prague 1, Czech Republic | Processing 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 | yes: Scrapers via Apify |
| PostHog Inc. (EU cloud) | Usage events of the application (which feature was used when), pseudonymous | Event 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 workspace | 2261 Market St., #4008, San Francisco, CA 94114, USA — EU cloud in Frankfurt | Processing in the EU; EU-U.S. Data Privacy Framework and Standard Contractual Clauses (module 2) in the signed data processing agreement (19 October 2026) | yes: Usage events |
| Hanko GmbH | Sign-in: e-mail address with one-time code or Google login; sessions (30 days) | E-mail address, user id, sign-in method, timestamps | Ringstraße 19, 24114 Kiel, Germany — Data centres in Germany only | Processing in the EU | no |
| 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 ListPlus | 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA | EU-U.S. Data Privacy Framework | no |
| 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 processors | From 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/Link | Sold Through Link, LLC (formerly Lemon Squeezy, LLC): South San Francisco, California, USA; payment processing in the EU: Stripe Technology Europe, Limited, Dublin, Ireland | Stripe'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 | no |
| Attio Ltd. (CRM) | Customer care: the account with e-mail address, plan and key account events; sends the welcome e-mail | E-mail address, user ID, plan, account events | London, United Kingdom | Adequacy decision for the United Kingdom | no |
| n8n GmbH (n8n Cloud) | Internal notifications to our team via Slack about key account events | E-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 | no |
| Google Cloud EMEA Limited (Google Workspace) | Our mailboxes (e.g. support@listplus.ai): support requests, data subject requests, AI help conversations sent to support | Content of e-mails to us (sender, text, attachments); for “Send to support” the conversation, e-mail address, workspace, plan and page | Velasco, Clanwilliam Place, Dublin 2, Ireland — Google's data centres, also outside the EU | Contracting 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 | no |
| 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) | no |
| 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, the Agent API's Google search and the nightly news searches of the Daily radars; 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 profile | The search term (name, role, company, place, research topic; for a Daily radar the topic, keywords and country — no people, no list contents); company name and domain; for a question about a person their name, role and LinkedIn URL; the question itself | 735 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 | yes: Parallel |
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 provider | Service | Data transmitted | Address / location | Third-country safeguard, contract | Customer can switch off |
|---|---|---|---|---|---|
| Prospeo | B2B contact database (segment search), verified business e-mail addresses and phone numbers, company profiles, job changes | Search filters or the search key: LinkedIn URL, name and company, domain | Defastra 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 | yes: Prospeo |
| FullEnrich | Business e-mail address and phone number from name and company or LinkedIn URL (waterfall through 20+ sources) | Name and company, domain or LinkedIn URL | FullEnrich Corp., 28 Geary St, STE 650, Suite #346, San Francisco, CA 94108, USA | Standard Contractual Clauses (modules 2 and 3) in the provider's data processing agreement — Contract: fullenrich.com/data-processing-agreement | yes: FullEnrich |
| CompanyEnrich | Company data from domain or company name (industry, size, location, website); workforce, decision makers, similar companies | Domain or company name; for person lookups name and company | STDİ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 | yes: CompanyEnrich |
| Crustdata | Company identification by domain (LinkedIn company page, name, size class) for enrichment | Only the company domain; no personal data | Crustdata Technologies Inc., 95 Third Street, 2nd Floor, San Francisco, CA 94103, USA — Data in the USA | No transfer of personal data (company domains only) | no |
| The Companies API | Company data for a domain when CompanyEnrich returns nothing (fallback provider) | Only the company domain | The 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 | yes: CompanyEnrich |
| HarvestAPI | Publicly visible LinkedIn data: profile, company, profile search, posts and reactions, open jobs | LinkedIn URL, name and company, post URL | Aventra 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 minutes | Hong 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) | yes: LinkedIn data |
| MillionVerifier | Checking whether an e-mail address is deliverable | The e-mail address | Southern Vector Limited, 26 Applefield Court, Northwood, Christchurch 8051, New Zealand — Processing in New Zealand, Hungary and other EEA countries, the USA and other countries | New 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 | yes: MillionVerifier |
| 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 Inbox | The 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 period | Serper (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 time | USA and Singapore (no adequacy decision); no data processing agreement and no Standard Contractual Clauses (the provider offers them to large customers only) | yes: Google search via Serper |
| Hacker News (search via Algolia) | Public stories and comments on Hacker News including user names, for the AI research | Only the search term, never data from customer lists | Algolia, Inc., 3790 El Camino Real, Unit #518, Palo Alto, CA 94306, USA — public interface without an account | No contract; only the search term is transmitted | yes: research source Hacker News |
| 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 terms | The URL or search called | LinkedIn, Crunchbase, Reddit, X, Google Maps, Similarweb, arbitrary websites | Not applicable (retrieval of public pages) | yes: Scrapers via Apify, research source Reddit, research source X, research source LinkedIn posts, LinkedIn people search, reading web 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 provider | Service | Data transmitted | Address / location | Third-country safeguard, contract | Customer can switch off |
|---|---|---|---|---|---|
| The customer's connected systems | Import from and export to systems the customer connects; pipeline targets | The records the customer transfers | HubSpot, 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 | yes: Connected systems |
| The customer's own webhook endpoint | Pipeline target “endpoint” | The records the customer transfers | Named by the customer | The customer is the controller of this transfer | no |
| The customer's own AI (Agent API, MCP, research link) | Reading and writing lists and research through an AI system the customer connects | What the connection exposes (columns, sublists, actions) | Chosen by the customer, e.g. ChatGPT, Claude, own agents | The customer is the controller of this transfer | yes: Agent API and MCP |