Data Processing Agreement (DPA)
Last updated: 10 November 2026
This English version is a convenience translation. The German version is legally binding.
This Data Processing Agreement (“DPA”) governs the processing of personal data by salesperformer GmbH, Sperberweg 7, 82152 Krailling, Germany (“ListPlus”, “processor”) on behalf of the customer (“Customer”, “controller”) when using ListPlus. It supplements the ListPlus Terms of Service (listplus.ai/terms, “Terms”) and becomes part of the contract when the user agreement is concluded, without the need for a separate signature. A signed copy is available on request (support@listplus.ai).
Structure: The sections set out rights and obligations. Annex 1 describes subject matter, nature, purposes, data subjects, data and deletion periods, Annex 2 the technical and organisational measures, Annex 3 the sub-processors and data providers with address, safeguard and contract, Annex 4 the AI systems used, with their classification under the AI Act and a risk assessment, Annex 5 the particulars for ContactPlus. In a signed version, an Annex 1a describes the specific use at the Customer and the contact persons of both parties.
§ 1 Subject matter and definitions
(1) This DPA covers the processing of personal data that ListPlus carries out on behalf of the Customer when providing the Service under the Terms (“Customer Data”). Subject matter, nature, purposes, categories of data, data subjects and duration are set out in Annex 1, the use of AI systems in Annex 4.
(2) Terms such as “personal data”, “processing”, “controller”, “processor” and “personal data breach” have the meaning given in Art. 4 GDPR.
(3) “Retrieval Tools” are the functions of the Service with which the Customer queries data from external data providers or publicly accessible sources, in particular enrichment, people and segment search, e-mail verification, LinkedIn imports, AI research and signal queries, including via the Agent API.
(4) ContactPlus. This DPA also applies to ContactPlus (contactplus.app), a service of salesperformer GmbH, in relation to the holders of a ContactPlus account; Annex 5 applies to it and takes precedence over the other provisions to that extent.
§ 2 Roles of the parties
(1) ListPlus as processor. The Customer is the controller and appoints ListPlus as processor for
- data the Customer uploads, imports, creates, synchronises from connected systems or forwards to the Inbox;
- data the Customer queries with the Retrieval Tools: ListPlus runs each search, enrichment or research only at the Customer's request and within the scope the Customer sets, transmits the necessary search key to the respective data provider and makes the result available to that Customer only;
- data the Customer sends to destinations of its choice via pipelines, exports, the Agent API or connected systems.
The Customer decides whether, about which persons, with which tools and for what purpose data is processed. It is responsible for complying with the obligations data protection law imposes on controllers. Annex 1 lists exhaustively the purposes for which ListPlus processes Customer Data.
(2) ListPlus as controller. ListPlus processes the following on its own responsibility and not on behalf of the Customer:
- account, contract, billing, support and usage data of the Customer's users;
- data required for operation, security, prevention of abuse and fraud, credit billing and compliance with legal obligations;
- aggregated or anonymised usage statistics for improving the Service that do not allow conclusions about individual data subjects in Customer Data;
- the cross-customer company cache (§ 13(3) of the Terms), to the extent it exceptionally contains personal data;
- the cross-customer suppression list under § 9(1) (hashes only), with which ListPlus honours objections of data subjects for all customers.
The ListPlus Privacy Policy (listplus.ai/privacy) applies to this processing.
(3) Data providers and sources (dual role). ListPlus owns no contact database and does not pass data from a database of its own to the Customer. When the Customer triggers a retrieval, ListPlus transmits, on the Customer's instruction (§ 3), only the search key needed for the query to a provider named in Annex 3, Part B, that the Customer has not switched off in the workspace policy, and makes the result available to that Customer only. Per processing step: (a) providers with a data processing agreement (Annex 3, Part B, column “contract”) process the search key solely to answer the query as further processors of ListPlus; §§ 7 and 8 apply to them. (b) For their own databases and for providing data from them to the Customer, the providers are independent controllers; the Customer receives the data as controller and needs its own legal basis for using it (§ 4). (c) Providers and public sources without a data processing agreement receive the search key as recipients; the Customer, as controller, is responsible for this transfer, including to a third country; for this purpose Annex 3, Part B, names for each provider its address, the data transmitted and the safeguard the provider states. ListPlus announces new providers in Part B with the notice period of § 7(2) sentence 1; the Customer can switch off any provider that receives personal data at any time in the workspace policy (Annex 3 names the switch for each provider).
§ 3 Instructions
(1) ListPlus processes Customer Data only on documented instructions from the Customer, unless ListPlus is required to do so by Union or Member State law; in that case ListPlus informs the Customer of that legal requirement before processing, unless the law prohibits this.
(2) The Customer's instructions are set out conclusively in the Terms, this DPA, the workspace policy and the operation of the Service. Every action triggered by the Customer or its users – for example an import, a search, an enrichment, an AI research with the search description written by the Customer and the sources it selected, a pipeline or an export – is a documented instruction to the extent defined by the action. The same applies to actions the Customer triggers via the Agent API or an AI system it connects. With the workspace policy (§ 3(4) of the Terms) the Customer instructs ListPlus not to use certain features, data providers or sources for its workspace; ListPlus enforces this instruction technically.
(3) The Customer gives further instructions in text form to support@listplus.ai; it confirms oral instructions in text form without delay. ListPlus may refuse instructions that go beyond the agreed scope of services or carry them out against reasonable remuneration.
(4) ListPlus informs the Customer without delay if, in its opinion, an instruction infringes data protection law, and may suspend its execution until the Customer confirms or changes it.
(5) Persons authorised to give and receive instructions. On the Customer's side, instructions are given and notices under this DPA are received by the owner of the workspace (who sets the workspace policy), the administrators of the workspace (who manage members, agent connections and their list shares) and the persons the Customer names to ListPlus in text form; members give instructions only by operating the Service within the workspace policy. On ListPlus's side, instructions are received by the management, currently Stephan Methner, reachable at support@listplus.ai and +49 (0)89 28741023. If the named persons or their contact details change, the party concerned informs the other without delay in text form. In a signed version, the persons of both parties are named in Annex 1a.
§ 4 Customer obligations
The Customer ensures that
- there is a legal basis for every processing it initiates, in particular for querying data with the Retrieval Tools and its later use;
- it informs data subjects under Art. 13 and 14 GDPR, honours objections and responds to data subject requests; Annex 4 contains the information it needs about the AI features and a suggested wording;
- advertising by e-mail, telephone or other channels takes place only within the statutory limits, in particular § 7 of the German Act against Unfair Competition (UWG);
- no special categories of personal data (Art. 9 GDPR) and no data relating to criminal convictions (Art. 10 GDPR) are processed;
- it checks AI results before using them and uses the AI features only within their intended purpose under Annex 4;
- it is entitled to provide the Customer Data to ListPlus for processing.
The Customer informs ListPlus without delay if it detects errors or irregularities in the processing.
§ 5 Confidentiality
ListPlus ensures that all persons authorised to process Customer Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality. Only persons who need access to provide the Service, for support or to resolve faults are given access to Customer Data; they process Customer Data only in accordance with this DPA and the Customer's instructions (Art. 29, Art. 32(4) GDPR).
§ 6 Technical and organisational measures
(1) ListPlus implements the technical and organisational measures described in Annex 2 under Art. 32 GDPR to ensure a level of security appropriate to the risk.
(2) The measures are subject to technical progress. ListPlus may replace them with equivalent or better measures; the level of security must not fall below the agreed level. ListPlus documents material changes in Annex 2; the version in force is in the workspace's data protection package.
§ 7 Sub-processors
(1) The Customer grants ListPlus general authorisation to engage sub-processors. The sub-processors engaged at the time the contract is concluded are listed in Annex 3, Part A, and — for the search key — the data providers with a data processing agreement in Part B, with the contracting entity's full postal address, service, data transmitted, place of processing, safeguard and contract, and are deemed approved.
(2) ListPlus informs the Customer in text form at least 30 days before engaging a new sub-processor or replacing an existing one (e.g. by e-mail or by updating Annex 3 with a notice by e-mail). The Customer may object to the change in text form within this period for an important data protection reason. If the parties cannot agree, the Customer may terminate the user agreement as of the date the sub-processor is engaged. If ListPlus must replace a sub-processor at short notice to maintain the security or availability of the Service – for example because a service provider fails, discontinues its service or the cooperation must end for legal reasons – ListPlus may engage the replacement without prior notice; ListPlus then informs the Customer without delay, at the latest within seven days. The right to object under sentence 2 remains; the period starts with this notice.
(3) ListPlus imposes on every sub-processor by contract the same data protection obligations as set out in this DPA, in particular providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that the processing meets the requirements of the GDPR (Art. 28(4) GDPR). Where a sub-processor fails to fulfil its data protection obligations, ListPlus remains liable to the Customer for the performance of that sub-processor's obligations.
(4) Ancillary services that ListPlus uses from third parties without those third parties gaining access to Customer Data (e.g. telecommunications, monitoring the availability of the Service, payment processing for ListPlus itself) are not sub-processing within the meaning of this DPA.
(5) Annex 3 names each sub-processor's agreement; that agreement refers to the list of its own sub-processors. On request, ListPlus gives the Customer, within 14 days, the name, address and place of processing of every further link in the chain, as far as this information is available to ListPlus or can be obtained from the sub-processor.
§ 8 Transfers to third countries
(1) Customer Data is processed outside the EU/EEA only if the requirements of Art. 44 et seq. GDPR are met, in particular on the basis of an adequacy decision (e.g. the EU-U.S. Data Privacy Framework) or the EU Standard Contractual Clauses (Module 3, processor to processor) that form part of the data processing agreement with the respective sub-processor. The application, database and file storage are located in the EU region Frankfurt; AI models run in EU data centres by default (Annex 4). Annex 3 names the safeguard and the contract for each sub-processor. For data providers and sources without a data processing agreement § 2(3)(c) applies: they receive only the search key, and only as long as the Customer has not switched them off. Where such a provider names no transfer safeguard, Annex 3 says so; the Customer decides with the switch named there whether to use it.
(2) Assessment of the transfers. For recipients certified under the EU-U.S. Data Privacy Framework, the European Commission's adequacy decision applies; no supplementary measures are needed. For transfers to the USA based on Standard Contractual Clauses, ListPlus has taken into account that the safeguards introduced by Executive Order 14086 (limiting access by intelligence services to what is necessary and proportionate, redress before the Data Protection Review Court) apply to all transfers to the USA, irrespective of the transfer tool used (information note of the European Data Protection Board of 18 July 2023). The measures in Annex 2 add to this: encrypted transmission, transmission of only the excerpt the task needs, processing in the EU where the provider offers it. On this basis ListPlus considers the level of protection adequate and reviews the assessment when the legal situation changes.
(3) On request, ListPlus provides the Customer with the sub-processors' agreements containing the Standard Contractual Clauses, as far as they are not publicly available (Annex 3, column “contract”), and explains the assessment under paragraph 2.
§ 8a Requests from authorities
(1) If an authority or court, including one of a third country, demands disclosure of or access to Customer Data from ListPlus, ListPlus informs the Customer without delay, as far as legally permitted, and refers the authority to the Customer. The same applies if ListPlus learns of such a request to a sub-processor (in particular through a notification under Clause 15.1 of the Standard Contractual Clauses).
(2) ListPlus discloses Customer Data only where Union or Member State law requires it; ListPlus complies with requests from authorities or courts of a third country only in accordance with Art. 48 GDPR. ListPlus reviews the lawfulness of a request, uses reasonable legal remedies and discloses only what is demanded.
(3) ListPlus informs the Customer without delay of inspections and measures of a supervisory authority insofar as they concern Customer Data, and assists the Customer with enquiries from its supervisory authority concerning this processing.
§ 9 Assisting the Customer
(1) ListPlus assists the Customer with appropriate technical and organisational measures in responding to data subject requests. The Service enables the Customer to view, export, correct and delete Customer Data itself; the workspace's Block List marks records of persons who are not to be contacted. If a person objects to ListPlus, ListPlus enters their identifier as a hash into a cross-customer suppression list so that they are no longer retrieved from data providers or added as a research hit through the Service; records the Customer already holds are not affected and are for the Customer to handle.
(2) If a data subject contacts ListPlus directly, ListPlus forwards the request to the Customer without delay, as far as the Customer can be identified, and does not answer it itself unless the Customer instructs it to do so or the law requires it.
(3) Taking into account the nature of the processing and the information available, ListPlus assists the Customer in complying with the obligations under Art. 32 to 36 GDPR (security, notifications, data protection impact assessment, prior consultation). For a data protection impact assessment, ListPlus provides in particular Annexes 1, 2 and 4 and the workspace's data protection package.
(4) ListPlus may charge reasonably, according to effort, for assistance that goes beyond the functions of the Service and the documents under paragraph 3 and is not based on a breach by ListPlus.
§ 10 Personal data breaches
ListPlus notifies the Customer of a breach of the security of Customer Data, and of a well-founded suspicion of one, without undue delay after becoming aware of it (Art. 33(2) GDPR), to the e-mail address of the workspace owner and to the persons named under § 3(5). The management of ListPlus is responsible for the notification. A first notification is made even if not all information is known yet; it contains, as far as known, the information under Art. 33(3) GDPR, missing information is provided without undue delay. ListPlus takes the necessary measures to secure the data and mitigate possible adverse consequences without delay and documents the incident. Notifying supervisory authorities and data subjects is the Customer's responsibility. The notification is not an acknowledgement of fault.
§ 11 Deletion and return
(1) The Customer can export and delete Customer Data itself at any time during the term of the contract; deleting a list, a workspace or the account is started at once and usually completes within minutes. Certain data is deleted automatically after the periods stated in Annex 1.
(2) After the user agreement ends, ListPlus deletes or returns the Customer Data at the Customer's choice, unless there is a legal obligation to retain it. Data is returned through the Service's export function and the Agent API; after the end of the contract the Customer Data remains retrievable for at least 30 calendar days (§ 7a of the Terms, Art. 25 Data Act). ListPlus then deletes it completely. If the Customer deletes its account itself, this is its instruction to delete immediately; the application points to the export beforehand. On request, ListPlus confirms the deletion in text form.
(3) Copies in the daily database backups are deleted after 7 days at the latest. Sub-processors delete Customer Data in accordance with their agreements and retention periods, in particular logs and caches with limited retention (Annex 1).
§ 12 Evidence and audits
(1) On request, ListPlus provides the Customer with all information necessary to demonstrate compliance with the obligations under Art. 28 GDPR. As a rule, current self-assessments, this DPA with its annexes, the workspace's data protection package and certificates and audit reports of the sub-processors (e.g. ISO 27001 or SOC 2 of the hosting provider) are sufficient evidence.
(2) If this evidence is not sufficient in an individual case, the Customer may carry out further audits, including inspections, at most once per calendar year after giving reasonable notice (at least 30 days), during normal business hours, itself or through an auditor bound to confidentiality who is not a competitor of ListPlus, unless a supervisory authority requires more or there is a specific reason. The audit takes place primarily remotely (written questions, documents, video conference); for the data centres, the sub-processors' certificates and audit reports replace an on-site audit. Each party bears its own costs.
§ 13 Liability
(1) Liability towards data subjects is governed by Art. 82 GDPR and is not affected by this DPA. Between the parties, damage is borne according to each party's share of responsibility (Art. 82(5) GDPR), unless the following paragraphs provide otherwise.
(2) ListPlus is liable without limitation for intent and gross negligence, for injury to life, body or health, under the Product Liability Act and to the extent of a guarantee given.
(3) In the case of slight negligence, ListPlus is liable only for breach of essential contractual obligations; these are obligations whose fulfilment makes the proper performance of this DPA possible in the first place and on whose observance the Customer may regularly rely, in particular the obligations under Art. 28(3) GDPR, the notification under § 10 and the technical and organisational measures under Annex 2. Liability is then limited to the damage typical for the contract and foreseeable at its conclusion, per contract year in total to the higher of EUR 50,000 and three times the remuneration the Customer paid to ListPlus in the twelve months before the event giving rise to the damage. This limit applies separately from the liability limits of the Terms.
(4) ListPlus is liable for sub-processors as for its own fault (Art. 28(4) sentence 2 GDPR); paragraphs 2 and 3 apply accordingly.
(5) Fines are borne by the party on which they are imposed; no indemnity for fines is agreed. Statutory recourse claims remain unaffected.
(6) If a data subject or an authority asserts claims, the parties inform each other without delay and coordinate the defence; neither party acknowledges a claim that falls on the other internally without its consent.
(7) This § 13 conclusively governs liability for breaches of this DPA and of data protection law and takes precedence over the liability and indemnity provisions of the Terms (§§ 14, 15 of the Terms); it can only be amended under § 14(3).
§ 14 Term and final provisions
(1) This DPA applies for the term of the user agreement and beyond for as long as ListPlus processes Customer Data.
(2) In the event of conflicts between this DPA and the Terms, the provisions of this DPA prevail in matters of data protection.
(3) Amendments to this DPA require the Customer's consent in text form; consent may also be given by confirming it in the application. ListPlus announces intended amendments in text form at least six weeks before they are to take effect. If the Customer does not consent, this DPA continues to apply in its previous version; the termination rights under the Terms remain unaffected. Only changes of sub-processors under § 7 and changes of the technical and organisational measures under § 6(2) that do not lower the level of protection take effect without consent. The amendment procedure of § 16 of the Terms does not apply to this DPA.
(4) The Customer may terminate the user agreement without notice if ListPlus seriously breaches this DPA or data protection law, fails to carry out a lawful instruction or refuses audits under § 12; § 11 applies.
(5) The law of the Federal Republic of Germany applies. The place of jurisdiction, as far as legally permissible, is the registered office of salesperformer GmbH. The German version of this DPA is binding. In the event of conflicts the order of precedence is: Annex 1a of a signed version, this DPA with its other annexes, the Terms.
(6) Should individual provisions be invalid, the validity of the remaining provisions remains unaffected.
Annex 1: Subject matter, purposes and scope of processing
Subject matter
Provision of the ListPlus service as software as a service: the Customer keeps lists of business contacts and companies in ListPlus, checks and completes them, finds new business contacts and hands records over to its own systems. ListPlus processes Customer Data only as the Customer operates and configures the Service (§ 3(2)).
Nature of the processing
Collection (retrieval from data providers and public sources at the Customer's request), recording, organisation, structuring, storage, adaptation and alteration, retrieval, consultation, alignment, use, disclosure by transmission to recipients chosen by the Customer, restriction and erasure (Art. 4(2) GDPR).
Purposes of the processing
ListPlus processes Customer Data exclusively for the following purposes; which of them take place in the Customer's workspace is determined by the Customer through operation and the workspace policy:
- Keeping lists: storing, displaying, editing, filtering and exporting the Customer's lists; importing from files, addresses and connected systems, on request reloading from the source regularly and writing changes back to it; live status updates in the browser;
- Checking and cleaning: data quality checks (formats, duplicates, placeholders, plausibility) with suggested corrections, checking the deliverability of e-mail addresses, on request AI checks (Annex 4);
- Enriching: at the Customer's request, retrieving missing business details (e.g. position, business e-mail address and phone number, LinkedIn profile, company data) from data providers and adding them to the list; only the search key goes to the provider (§ 2(3));
- Searching: finding persons and companies by the Customer's criteria (e.g. role, industry, location, company size) in the data providers' databases and adding them to a list of the Customer;
- Researching: at the Customer's request, searching publicly accessible sources according to its search description (AI research, LinkedIn and web imports, web research on a company or person) and providing hits with source, evidence and a fit assessment;
- Receiving: content that the Customer or a system it set up sends to ListPlus (e-mails forwarded to the Inbox, list webhooks, forms, app events), recognising contacts in it, holding back doubtful records and adding the others to the list;
- Saving: keeping contacts and companies in the workspace's Watchlist;
- Detecting changes: at the Customer's request, checking whether a person still works at the company in its list (job change) and retrieving signals about companies (e.g. open jobs, news);
- Automating and transmitting: applying the Customer's rules to records (e.g. setting a status, enriching), transmitting records via pipelines and exports to destinations chosen by the Customer (e.g. CRM, spreadsheets, Slack, own endpoint), creating e-mail drafts in a user's connected mailbox (without sending) and sending digests to workspace members;
- Connecting: giving AI systems connected by the Customer access via the Agent API to the lists shared with them; receiving data from the Outlook add-in and from hand-overs of the browser extension;
- AI assistance: carrying out commands to the list assistant, filling AI columns, recognising columns on import and answering questions to the AI help (Annex 4).
ListPlus does not process Customer Data for its own purposes; § 2(2) remains unaffected.
Specific use at the Customer
Which of these processing operations take place is determined by the Customer's actions and the workspace policy (§ 3(2)); which features, data providers and sources are switched off in its workspace is documented in the workspace's data protection package (Settings → Workspace). In a signed version, Annex 1a describes the specific use at the Customer: features used, data subjects, categories of data, recipients and the persons named under § 3(5).
Categories of data subjects
- business contacts, prospects, customers and other persons in the Customer's lists;
- persons whose data the Customer queries with the Retrieval Tools, including persons the Customer keeps in the Watchlist and persons captured in the AI research as authors, commenters or people reacting to public posts;
- senders and persons named in forwarded content (Inbox); persons who fill in a form of the Customer or whose data a system sends to a list's webhook; persons whose data arrives from an app the Customer connected as an app event (e.g. form answers, bookings, messages);
- correspondents the Customer captures via the Outlook add-in; persons and companies whose LinkedIn pages the Customer captures with the Chrome browser extension and hands over to a list;
- the Customer's employees, to the extent they are contained in Customer Data.
Categories of personal data
- name, job position and seniority level, company;
- business e-mail address and its deliverability status, business phone and, where applicable, mobile number;
- LinkedIn profile URL, location, publicly visible profile information (e.g. career history, former employers), public posts, comments and reactions; for the AI research, source, evidence and a fit assessment;
- content of forwarded e-mails and attachments (Inbox);
- origin of a record and, for each added detail, provider and time;
- other data the Customer adds to its lists (no data under Art. 9 and 10 GDPR).
Duration and deletion periods
Processing lasts for the term of the user agreement; deletion under § 11. Independently of this, the following periods apply:
| Data | Retention |
|---|---|
| Lists, Watchlist, Outlook contacts, form submissions | Until deleted by the Customer |
| Inbox entries | 14 days after receipt |
| AI research runs | In the application 7 days after the start; via the Customer's own AI (research link) 1 to 7 days, the user's choice; 30 days from the start, or from switching on the hand-over of hits to a list |
| Pipeline history (records sent and responses) | 30 days after sending |
| Cached query results about persons (per workspace) | 30 days from the retrieval at the provider |
| Inputs and results of direct enrichments via the Agent API | Up to 48 hours |
| Shared result links | 7 days after the last view |
| Profiles only viewed (“Recently viewed”) | 30 days after the last activity |
| AI texts for e-mail drafts (cache) | 1 day |
| Verdicts of AI checks (under a hash of the value) | 30 days |
| Contacted log (who was contacted when through which channel) | 365 days |
| Copies of deleted rows for “record deleted” rules set up by the Customer | Up to 30 days |
| Forwarded e-mails at the receiving service (Postmark) | 45 days |
| Logs at the hosting provider | 30 days at most |
| Daily database backups | 7 days |
Annex 2: Technical and organisational measures
This annex describes ListPlus's technical and organisational measures under Art. 32 GDPR as of 10 November 2026, structured by Art. 32(1)(a) to (d) GDPR. ListPlus operates no servers or data centres of its own; the application and data are located at the sub-processors in Annex 3, Part A. The hosting provider Vercel is certified to ISO 27001:2022 and has a SOC 2 Type 2 report; ListPlus itself holds no certification of its own.
1. Pseudonymisation and encryption (a)
- Transmission: encrypted only (TLS) – between browser and application, between application and database (the database accepts TLS connections only) and to all service providers.
- Data at rest: file storage at the hosting provider, database (Redis Cloud) and backups (Amazon S3) encrypted at rest.
- Secrets: access keys the Customer stores for its own destinations are encrypted with AES-256-GCM; the key for this exists only in the server environment. ListPlus stores agent keys and OAuth access tokens only as hashes. OAuth credentials of connected systems are held by the connection service (Pipedream), not by ListPlus.
- Pseudonymisation: the suppression list under § 9(1) contains hashes only; IP addresses are counted for abuse limits as a truncated hash and deleted after two days at most (for the browser extension's HubSpot connection the IP address itself for a few minutes); usage events carry a pseudonym of the account and no names, e-mail addresses or list contents.
2. Confidentiality (b)
- Physical access control: no servers of our own. Physical access to the data centres lies with Vercel and Amazon Web Services (also for Redis Cloud) and is covered by their certifications (ISO 27001, SOC 2).
- System access control – application: sign-in by e-mail one-time code or with Google, without a password; sessions via signed tokens (30 days); no shared accounts.
- System access control – administration: the administrative accounts for hosting, database, storage, source code, payment and connection service are personal accounts with multi-factor authentication; credentials are kept in a password manager. Database and API keys exist only in the server environment, never in browser code.
- Data access control: roles owner, administrator and member per workspace; lists are accessible only to members of the workspace and persons explicitly granted access. Every interface checks sign-in and authorisation on the server; an automated test checks that every interface calls a sign-in or token check, and deliberately public interfaces are approved one by one. The server enforces the workspace policy, not just the user interface. Connected AI systems work only on lists explicitly shared with them, with the rights granted per list, and cannot delete records. The internal administration interface shows only account and usage figures, no list contents, and is accessible to the management only.
- Separation control: Customer Data is stored separately per workspace. Results about persons are not shared between customers, and ListPlus keeps caches with personal reference (e.g. about LinkedIn and X profiles, AI verdicts about persons) per workspace too; only company data without personal reference is stored across customers (30 days), and contributing to it can be switched off per workspace.
- Data minimisation: data providers receive only the search key needed for the query, never the rest of the list; AI providers receive only the excerpt the task needs (Annex 4).
3. Integrity (b)
- Transfer control: external accesses (Agent API, Inbox address, list webhooks, forms, app events, links to the data protection package) are protected by secret keys (agent keys, Inbox addresses and webhooks can be revoked; links to the data protection package expire after 30 days); incoming webhooks and app events verify signatures or shared secrets, and repeated deliveries are recognised. The Customer controls which service providers receive data through the workspace policy; the suppression list applies to every transmission to external destinations.
- Input control: for every record, ListPlus stores how it entered the list and, for every added detail, the provider and time. Pipeline deliveries (30 days) and calls of connected AI systems (action, number of records, requested fields, credits; 7 days) are logged as well; the hosting provider's server logs are deleted after 30 days at most. ListPlus does not currently keep a log of its own of administrative access.
4. Availability and resilience (b)
- Platform: the application and background processing run on managed platforms in the Frankfurt region; server functions scale automatically with load. The hosting provider automatically mitigates denial-of-service (DDoS) attacks at network level.
- Database: Redis Cloud, replicated, with a continuous journal (writes are persisted every second) and monitoring of memory use. Caches are kept in a separate database; losing it loses no Customer Data.
- Durable storage: lists are kept as an archive file in the hosting provider's file storage (EU region); changes are usually written there within five minutes (for large lists with ongoing changes up to 30 minutes); unsaved changes remain in the database until then and do not expire there.
- Load limits: ceilings per list (50,000 records) and per request; rate limits per user, workspace or IP address for public and programmatic access (AI help, Agent API, forms, webhooks, app events); limits on concurrent queries per data provider and per workspace so that a single customer cannot exhaust capacity; a fixed connection budget for background queues.
- Fault tolerance: background work runs through queues with automatic retries; interrupted enrichments resume where they stopped, and a watchdog restarts stalled runs; duplicate deliveries are recognised.
- Monitoring: an external monitoring service checks a health endpoint every five minutes (both databases reachable and within their memory limits, all scheduled jobs ran) and alerts ListPlus in case of a fault; the service receives no Customer Data.
5. Restorability (c)
- Database: backed up daily to a dedicated, encrypted storage without public access in Frankfurt (Amazon S3); every backup is deleted after 7 days. With replication and journal, data loss is normally limited to seconds, and to one day at most when restoring from the backup.
- Lists: the archive file in the file storage is the durable version; the hosting provider does not offer a backup of this file storage that ListPlus can access.
- Application: every version is deployed immutably; in case of a fault ListPlus can switch back to the previous version within minutes. The source code is kept in version control.
- Customer: the Customer can export its lists at any time.
6. Regular review (d)
- Every change to the application runs automated tests, type checking and static code analysis; automated tests check, among other things, that every interface calls a sign-in or token check and every scheduled job reports to the monitoring.
- The runtime environment (operating system, Node.js) is maintained by the hosting provider.
- ListPlus reviews these measures, the sub-processors and the data flows of the AI features at least once a year and on material changes and documents the result; architecture, billing and data protection were last reviewed in October and November 2026.
7. Processor control and organisation
- Sub-processors: selected by seat, safeguard and certification, bound by contract under § 7 and named in Annex 3 with address and contract; where noted, the Customer can switch each of them off.
- Staff: commitment to confidentiality (§ 5); access to production data only as far as necessary for operation and support, via personal accounts.
- Incidents: the management assesses security incidents; notification to the Customer under § 10.
- Data protection by design and by default: AI models in the EU by default, outside the EU only after the workspace owner switches it on; no use of Customer Data for training; automatic deletion periods (Annex 1); deletion of lists, workspaces and account by the Customer, started at once.
Annex 3: Sub-processors
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 |
| 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 profile | The 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 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 |
The current version of this annex is available at listplus.ai/en/subprocessors. Not in this annex: service providers that only process account, contract and billing data of users (Privacy Policy, section 15).
Annex 4: Artificial intelligence
This annex names the AI systems ListPlus uses when processing Customer Data, their data flows, their classification under Regulation (EU) 2024/1689 (“AI Act”) and the risk assessment, as of 10 November 2026. ListPlus does not train or modify models.
Models and providers
- Language models from OpenAI (Annex 3): via Vercel's AI Gateway (contracting party: Vercel). By default the model's processing is pinned to data centres in the EU; according to Vercel a request that cannot be served there fails instead of running elsewhere, and ListPlus checks the region reported for every answer. Vercel does not pin the route of a request to the gateway to a region; the gateway keeps no prompts or answers. The gateway is instructed 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. Requests a provider flags as possible abuse may be retained under its own rules.
- Judgement model “Jev” from TypeSafe AI (Annex 3): via the same gateway, without retention at the provider. The model has no EU region and, with EU processing, receives only job titles and positions (title with company name, without the person's name).
- Parallel Web Systems (Annex 3, USA): the research with cited sources (company brief, questions about a company or person) is an AI-based service and runs only on an explicit click with the notice “runs outside the EU”. In addition, ListPlus by default queries Parallel's web index beside Google search (person search, Inbox recognition, AI research, news, Agent API); the search term is transmitted, including a person's name, role and company. Both apply irrespective of the “AI models outside the EU” setting; the workspace owner switches them off with the “Parallel” switch.
- Transcription from OpenAI (dictation): directly at OpenAI in the USA, only when the workspace owner switches on “AI models outside the EU”; otherwise switched off.
- Model in the browser: the Chrome browser extension uses Chrome's built-in model on the user's device; this content does not reach ListPlus.
If the workspace owner switches on “AI models outside the EU”, the gateway chooses the region per request (including the USA) and the judgement model also receives values with personal reference. If the owner switches the AI features off, no AI model is called any more for the workspace (enforced on the server); research via Parallel is switched off with the “Parallel” switch.
Features
| Feature | Model | Data sent to the model | Result and control by the user |
|---|---|---|---|
| List assistant (commands and questions) | OpenAI | The user's text, column names and types, row count, names of statuses and pipelines, the conversation so far including earlier results; only when a command needs values, the unique values of the affected columns | A command from a fixed command set that the application checks and runs in the user's browser; changes to cells can be undone, started enrichments and hand-overs to pipelines cannot |
| AI checks and judgement columns (e.g. plausibility of city and country, seniority of a job title) | OpenAI, Jev | Only the unique values or value combinations of the affected columns | Finding or rating as a suggestion; the user applies corrections |
| AI text columns | OpenAI | The user's prompt with the record's values named in it (up to 2,000 characters) and, where present, its enrichment and check details (up to 1,500 characters each, including e-mail address and phone number) | Text in a column created as an AI column |
| Reading business cards (form, Inbox) | OpenAI | The photo of the business card | Recognised contact details that the sender or user sees |
| Column recognition on import, list titles | OpenAI | Column headers and a sample of values (10 % of the file, 50 to 200 rows) | Suggested column types and title, editable by the user |
| Recognition in Inbox, webhooks, forms and app events | OpenAI; Jev only outside EU processing | Text of an entry (up to about 24,000 characters); unknown field names with one example value; up to 12 fields for the spam check | Recognised contacts; doubtful records are held back and decided by the user |
| AI research with fit assessment | OpenAI, web sources | The Customer's search description; known identity details of a person (name, company, position, location) | Hits with source, evidence and an assessment 0–100 with reasoning; can be switched off |
| Understanding a search query | OpenAI | The user's search query | Search filters shown to the user, which the user can change |
| AI help | OpenAI | Question and last messages of the conversation, language, page address, plan and balance; counts of an open list, no values | Answer only from ListPlus's help texts; labelled as AI; forwarding to support on request |
| AI texts in e-mail drafts, “Check content”, company knowledge | OpenAI | Template, briefing, company knowledge, sender's name and the record's data without e-mail addresses and phone numbers; for company knowledge the text of the Customer's website | Draft in the user's mailbox; ListPlus sends no e-mails, the user reviews and sends them |
| Other single tasks | OpenAI | Gender: only the first name; company comparison: two company names; post search: text and author of a LinkedIn post; app events: the text; outreach template: three example records; Agent API: the values of the columns named | Result as a suggestion or field value in the workspace |
| Web research on click | Parallel (USA) | Company name and domain; for a question about a person their name, role and LinkedIn URL; the question | Answer with cited sources |
Classification under the AI Act
- Roles: ListPlus is the provider of the AI systems built into the Service (Art. 3(3) AI Act), the Customer is the deployer (Art. 3(4)). The underlying language models are general-purpose AI models; the obligations for these models lie with their providers.
- Intended purpose: maintaining and checking business contact and company data and finding and qualifying business contacts for sales and marketing. The AI features are not intended for the areas listed in Annex III of the AI Act, in particular not for selecting or evaluating applicants or employees and not for decisions on creditworthiness or access to services. If the Customer uses them for such purposes, it bears the responsibility under Art. 25 AI Act.
- Risk class: no prohibited practice under Art. 5 and no high-risk AI system under Art. 6 in conjunction with Annex III. The features take no decisions with legal or similarly significant effect within the meaning of Art. 22 GDPR; ratings such as seniority or fit are suggestions the user checks.
- The Customer sets the criteria: score columns add points according to rules and weights the Customer sets itself; a rule can be a statement of the Customer that an AI model answers per record with yes, no or unclear. AI judgement columns likewise check a statement of the Customer, and the research's fit assessment measures hits against the Customer's search description. Whether, by which criteria and with which weighting persons are classified is thus decided by the Customer; ListPlus sets no assessment standards of its own and does not monitor persons continuously.
- Transparency: the AI help discloses that it is an AI (Art. 50(1)). ListPlus does not send e-mail drafts; the user reviews and sends them.
- AI literacy: the help centre explains what the AI features see of the data and how results are to be checked; this supports the Customer's measures under Art. 4 AI Act.
Testing and changes
Before changing models or instructions, ListPlus tests the affected features with fixed test cases (among others 210 sentences for the list assistant, real questions with expected answers for the AI help, test cases for understanding search queries and column recognition). A change of the model provider is a change under § 7; ListPlus documents a change of the model version at the same provider in this annex.
Risk assessment
| Risk | Measures | Remaining risk |
|---|---|---|
| Incorrect or invented results | Results are suggestions the user checks before use (§ 10(2) of the Terms); research hits carry source and evidence; the AI help answers only with a source it has read; ratings are short classifications with reasoning | Low, as long as the Customer observes the duty to check under § 4 |
| Disclosure to the model provider | Calls only from ListPlus's servers; only the necessary excerpt; EU data centres by default; no training, no retention after the request, “do not store” | Low; the provider may retain requests flagged as abuse |
| Transfers to third countries | AI models in the EU by default, outside the EU only after the workspace owner switches it on; Jev with EU processing only without personal reference; searches via Parallel's web index (USA) run by default, research with cited sources only on a click with a notice, both can be switched off; safeguards under § 8 | Low with Parallel switched off; otherwise medium, because search terms with names go to the USA by default |
| Injected instructions in third-party content (forwarded e-mails, web pages, webhook data) | Model output is used only as data or suggestions in the Customer's workspace; models have no access to access keys or other workspaces; commands only from a fixed command set; where the application works on with an answer (commands, recognition, ratings), it requests structured data and checks it before use | Low; at worst a wrong suggestion in the Customer's own workspace |
| Rating of persons (seniority, fit) | Only details from the professional context; no data under Art. 9 GDPR (§ 4); reasoning visible; fit rating can be switched off; no automated decision | Low |
| Failure of a model | The feature reports an error; no Customer Data is lost; no fallback processing outside the EU | Low |
Suggested wording for informing data subjects
For its privacy notices under Art. 13 and 14 GDPR, the Customer may write, for example: “To maintain and complete our business contacts we use the ListPlus service of salesperformer GmbH, Krailling, Germany, as a processor. Business contact data (e.g. name, position, company, business e-mail address) is checked, completed and classified, also with the help of AI models, including an assessment of the professional role and of the fit with our target group (profiling). By default the models run in data centres in the EU and do not use the data for training. Missing business details may be requested from specialised data providers (list of sources: listplus.ai/en/subprocessors, Part B). No automated decision within the meaning of Art. 22 GDPR takes place.” The Customer adapts the text to the features it uses.
Annex 5: ContactPlus
This Annex applies to ContactPlus (contactplus.app), a service of salesperformer GmbH. It is agreed with the ContactPlus terms (contactplus.app/terms, § 10). The Customer is the holder of a ContactPlus account (“Account Holder”); ContactPlus is offered to businesses only. Unless this Annex provides otherwise, the sections of this DPA and Annexes 2 and 3 apply accordingly; Annex 1 applies to ListPlus only, Annex 4 only to the features named here. Where the DPA refers to the ListPlus Terms, the ContactPlus terms take their place; where it refers to the workspace, its policy, members or the privacy package, the account and its settings. By way of derogation from Annex 2 (“no shared accounts”), the Account Holder may enable the account on further devices within their company; they are responsible for them, see them in the account and can sign out each one (§ 3(2) of the ContactPlus terms).
Subject matter and instructions
Search for individual business contacts: the Account Holder searches for people (name with company, role at a company, address of a LinkedIn profile or business e-mail address), opens their professional profile and, on their click, retrieves extras. Every search, every opened profile, every click on an extra or a research, every export, every shared link and the setting up of an own endpoint is an instruction of the Account Holder (§ 3(2)). The Account Holder is authorised to give instructions and to receive notices; notices under this DPA go to the e-mail address of the account.
Purposes of processing
ContactPlus processes the data exclusively for the following purposes:
- Searching: understanding the input (language model, Annex 4), querying public search results (Google Search via Serper and, unless the Account Holder switches it off, Parallel's web index) and showing matching people;
- Opening a profile: retrieving and showing a person's publicly visible professional profile and the details of their company;
- Extras: on the Account Holder's click, retrieving the business e-mail address with a deliverability check, a phone or mobile number, the owner of an entered business e-mail address, posts and news, further people at the company, and web research with sources (company briefing, questions about a company or person);
- Keeping: keeping the copy of an opened profile with the retrieved details, folders and “Recently viewed” in the account; export as CSV or vCard;
- Passing on: at the Account Holder's request, sharing a profile as a link or sending it to their own endpoint.
ContactPlus does not process these data for its own purposes; nothing is shared between accounts. salesperformer GmbH processes as an independent controller only data under § 2(2) — for ContactPlus according to its privacy policy (contactplus.app/privacy), in particular the account, purchases, abuse prevention and the joint suppression list with which objections are honoured for ListPlus and ContactPlus.
Data subjects and data
People the Account Holder searches for or whose profile they open, and people who appear in an opened profile (e.g. employees of the same company, people who reacted to a post; contact details there only masked). Data: name, profile photo, position and headline, career, education, skills, languages, location, address of the LinkedIn profile, number of connections, details of the employer; only on retrieval the business e-mail address with its deliverability status and a phone or mobile number; public posts and news; results of web research with sources. No data under Art. 9 and 10 GDPR; private (free-mail) e-mail addresses are not looked up.
Retention and deletion
| Data | Retention |
|---|---|
| Copy of an opened profile with the retrieved details | At most 30 days from opening or the last retrieval, then deleted automatically |
| Cache of the account's retrievals (for that account only) | 30 days from the retrieval at the provider |
| Folders and “Recently viewed” | Until deleted by the Account Holder or until the account is deleted |
| Shared links | 7 days after last opened |
| Logs at the hosting provider | At most 30 days |
Whoever needs details longer exports them in the account. If the Account Holder deletes the account, ContactPlus deletes these data at once; the deletion is an instruction of the Account Holder, the retrieval period under § 11 does not apply to that extent.
Sub-processors and data providers
Of the service providers named in Annex 3, ContactPlus uses: as sub-processors (Part A) Vercel Inc., Redis EMEA Ltd. (Redis Cloud), Amazon Web Services EMEA SARL (Amazon S3), OpenAI, Apify Technologies s.r.o., Parallel Web Systems, Inc.; as data providers and sources (Part B, § 2(3)) Prospeo, FullEnrich, CompanyEnrich, Crustdata, The Companies API, HarvestAPI, MillionVerifier, Serper (Google search). Individual data providers cannot be switched off at ContactPlus. Parallel's web index (USA) is not asked in the search when the Account Holder chooses “No services outside the EU” in the browser; Parallel's research runs only on their explicit click.
Artificial intelligence
Annex 4 applies to understanding the search input, checking whether a hit fits the role searched for, and the web research; the other features named there do not exist at ContactPlus. ContactPlus gives people no scores and makes no automated decisions within the meaning of Art. 22 GDPR; which person to open is decided by the Account Holder.