You're the controller for that request
You decide who to contact through ListPlus, so you answer access, erasure and objection requests yourself, not ListPlus.
Privacy & GDPR
Roles, hosting locations, named subprocessors, retention periods and how the DPA applies — the specifics behind ListPlus's data handling.
You decide who to contact; ListPlus processes your list data on your behalf under a DPA.
Application and files run on Vercel in Frankfurt; the working data cache is in Frankfurt too.
A data processing agreement is available for every plan — email support@listplus.ai.
For the contact data in your lists, the two roles are kept separate.
A tool, not a database. The customer is the controller and in control, on the server. One provider list with every name. A notice and a suppression list for the people in the data. And a section on what is still open — we write that down too.
The same text opens the data protection package.
A data protection officer who objects to one provider or one feature does not have to reject the product.
Everything a data protection officer asks for in one printable page: the workspace switches, the DPA with its annexes, every provider with seat and safeguard, the notice for the people in the data, and the privacy policy. Customers generate the same package with their own switches from the workspace settings — or send it as a 30-day link.
Opens in the browser; print or download from there.
Application, files and the working data cache are hosted in the Frankfurt region.
Subprocessors first, then the data providers that receive only the search key of a lookup. Each handles one part of the product and receives only what that part needs. The complete list with safeguards and the policy switch per provider is at listplus.ai/en/subprocessors.
| Subprocessor | Purpose | Data received | Seat / location |
|---|---|---|---|
| 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 |
| 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 |
| 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 |
| 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) |
| 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) |
| 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 |
| 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) |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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) |
| 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 |
| 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) |
| 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) |
| 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) |
| 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 |
| 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) |
| 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 |
| 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) |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
Some subprocessors process data outside the EU; the safeguard for each transfer and the workspace switch that stops it are on listplus.ai/en/subprocessors.
Your lists stay until you delete them. A few places are deliberately temporary.
| What | Kept for |
|---|---|
| Lists | Until you delete them — no automatic expiry |
| Inbox entries | 14 days after arrival |
| Shared result links | 7 days after the last view — each view starts the week again |
| Background AI Research runs | 7 days from when you start them |
| Recently viewed profiles (Person Search) | 30 days of no further activity — contacts saved to a folder or enriched don't expire |
| Search result sessions (Segment Search, Person Search) | 30 days, sliding — renewed each time you reopen them |
| LinkedIn lookup cache (profile, company, search) | 30 days |
| Provider lookup cache (Prospeo, FullEnrich, Crunchbase) | 30 days, per workspace |
| Repeated Segment Search | 30 days |
| Company data cache (by domain) | 30 days — shared across all customers, company data only (no person fields) |
| AI classification cache | 30 days for confident results |
| Email verification cache | 7 days |
| Inbound e-mail at the provider (Postmark) | 45 days (the provider's default) |
Each AI feature receives only the data it needs for that one job.
It applies to every plan — Basic and Pro — as part of the user agreement; you do not have to request it. A signed copy is available by e-mail to support@listplus.ai. ListPlus itself holds no security certification of its own (no ISO 27001, SOC 2 or similar). Vercel, ListPlus's hosting provider, holds its own certifications, including SOC 2 Type 2 and ISO 27001:2022 — that's Vercel's certification, not ListPlus's, covering Vercel's infrastructure.
That request is addressed to you, not to ListPlus — but ListPlus gives you what you need to answer it.
You decide who to contact through ListPlus, so you answer access, erasure and objection requests yourself, not ListPlus.
The number badge in the sparkles column at the right edge of a row opens the record panel, where each enrichment result is headed with its provider, for example "Prospeo · Contact".
Select the row and use the selection bar's ⋯ menu → Delete (saved automatically; Undo brings it back). This removes it from that list only — not other lists, your watchlist, the Inbox, an export, or a CRM you already pushed it to.
Requests for a signed copy of the DPA and questions about backups and retention at ListPlus's providers go through support. The full subprocessor list is published at listplus.ai/en/subprocessors; deleting your entire account is self-service in Settings → Profile.
support@listplus.ai
On Vercel, in the EU region Frankfurt. The working data cache (Redis Cloud) is also in Frankfurt, on AWS eu-central-1.
You are. ListPlus processes that data on your behalf under a DPA, but you decide who to contact and why.
No, not ListPlus itself. Vercel, its hosting provider, holds its own certifications, including SOC 2 Type 2 and ISO 27001:2022 — that covers Vercel's infrastructure, not a ListPlus certification.
Yes — it applies automatically to every plan as part of the user agreement (listplus.ai/dpa). For a signed copy, email support@listplus.ai with your company name.
No. AI commands see your instruction and column structure; AI checks see only distinct values; an AI Column sees the values your prompt names for each row (plus its enrichment and check details); enrichment providers see only the identifier being looked up.
No, you do — you're the controller for that outreach. The record panel's provider badge on each row shows the source you need.
Lists are kept until you delete them. A few places are temporary by design: Inbox (14 days), shared result links (7 days after the last view), research runs (1 to 7 days, 30 with hand-off to a list), lookup caches about people (30 days per workspace) and a shared company cache without personal data (30 days).
Try the sample list or bring your own starting point.