Legal
Privacy policy
Last updated 1 November 2026. Published by the ProspectAPIs team.
This policy explains what we collect when you use ProspectAPIs, why, and what you can ask us to do with it.
What we collect
- Account details: your email address and sign-in method. Passwords are handled by our authentication provider and never stored by us in readable form.
- API keys: stored as a one-way hash plus a short prefix so you can tell them apart. We cannot show a key again after it is created.
- Usage records: for each call, the endpoint, status code, records billed, credits used, the key used and the time. These power your usage history and billing.
- Research inputs and results: the identifier, context and purpose you send to the research API, and the brief we return, kept so you can read the job again.
- Payments: our payment processor collects your card and billing details. We receive the payment result, the amount and a customer reference, never your full card number.
- Feedback: what you send through the feedback endpoint, delivered to the team.
- Connected accounts: if you connect your own account, its session, kept encrypted in our database, used only to perform the actions you request and deleted when you disconnect, plus a log of each action (endpoint, time and result). We do not store message content.
- Email verification: a single check or a quick check keeps no address: we store a one-way hash of each address with its domain and result, which powers the result cache, your stats and the bounce guarantee. The delivery outcomes you report are stored the same way. A bulk job keeps its addresses so it can check them over time, and deletes them 7 days after the job completes. The email finder keeps no names.
Why we use it
- To run your account, authenticate calls and bill them correctly.
- To keep the service secure and to investigate abuse of it.
- To answer you when you contact us and to fix what you report.
We do not use your research inputs to build products for anyone else.
Who processes it
- An authentication and database provider that hosts account and usage data.
- A payment processor for card payments and invoices.
- A language model provider that writes research briefs from the sources gathered for each job, including any context you send.
- Hosting providers for the website and the API.
- Google Analytics, for website traffic measurement, only with your consent where consent is required.
- AgentCat, for usage analytics on the hosted MCP server.
How an address is checked
A full check asks the address's own mail server whether the mailbox exists, without sending any mail. A quick check and a domain lookup read only public DNS, our lists and our own earlier results. For a domain we have not seen, we ask the public domain registry (RDAP) when it was registered; that request names the domain, never an address. The form widget runs only quick checks, from the sites its key lists.
People in the data
ProspectAPIs provides professional information about people, such as a name, a role, an employer and public professional activity, taken from public sources (public profile pages, public posts and company websites), and returns it to our customers through the API for B2B prospecting and research. The email finder also returns a person's likely work email address: it works it out from the name and company domain a customer sends and checks it with that company's mail server, without sending any mail.
Funding records and research briefs can name founders, executives and investors as they appear on public pages, such as a company's own team page or a press announcement. We do not buy people data.
The people endpoints read public LinkedIn profile pages, public posts and the public reactions and comments on them at the moment a customer asks, through accounts we operate. A read is not served from a stored copy of anyone's profile. To describe a company's engaged audience, we keep a short record of people who publicly reacted to or commented on that company's posts, or who list it as their employer: a public profile handle or an internal reference, the name and headline shown on their public profile, where we saw them, and when we first and last saw them. It is not a copy of the profile.
We act on a customer's own LinkedIn account only after that customer connects it, and only to perform the actions they request. We log each action (endpoint, time and result) and do not store message content in our database.
If you are named in the data and want a correction or removal, email the address at the end of this page with your public profile link and the name you appear under. We add both to our removal list, which every read that returns a person checks: people reads, company audience answers, the messaging reads of a connected account, funding, launch, company and ad records, funding, launch and ad alerts, research briefs and the email finder. Once you are on it, those reads no longer return you: a request about you is refused, a people read leaves out any result that carries your profile link or your name as its person, and in funding, launch, company and ad records and research briefs your name is taken out: an investor entry that is your name is dropped, and anywhere else your name is replaced with a marker. No new research brief or audience record about you is stored, and a new funding record is stored without your name, apart from the address of its public source, which we keep as the record's source and serve with your name replaced where it appears as words in the address. So a removal also stops any future sale or sharing of your information.
The name match is exact, so a removal by name also hides anyone else with exactly the same name, and a name we were not given is not matched. Removal does not reach into a customer's own inbox, where your messages with that customer live in their account, not ours, and it does not recall what a customer received before it.
Legal basis for people in the data
Under the GDPR and the UK GDPR, we rely on legitimate interests (Article 6(1)(f)): B2B prospecting and research using publicly available professional information. We weighed that interest against the rights of the people named. The information is about their professional life, it comes from pages that they or their companies made public, and objecting or asking for removal takes one email to the address at the end of this page.
You have the right to object to this processing at any time (Article 21). Send your objection to the same address, with the public profile link and the name you appear under, and we handle it as a removal request, with the effect described above.
If you are named in the data you can also ask what we hold about you (Article 15) and ask us to correct it. We answer from the same mailbox. You can also complain to your data protection supervisory authority.
Who receives people data, and for how long
- Our customers, the businesses that call the API, who receive it for B2B prospecting and research.
- The processors listed above that host and run the service, and the language model provider that writes research briefs.
A read of a public profile page or post is not stored. Company audience records have no fixed expiry today; after a removal they are never served again. Funding records are kept as the public record of a round, and launch records as the public record of a launch; once a poster is removed, a launch is served without them.
California: Do Not Sell or Share My Personal Information
Under the California Consumer Privacy Act, as amended by the CPRA, providing professional information about people to our customers, who pay for it, may be a "sale" or "sharing" of personal information. If you are a California resident, you can ask us not to sell or share your personal information.
To make a Do Not Sell or Share request, email emma@prospectapis.com with the public profile link and the name you appear under. It goes to the same mailbox and the same process as a removal request: once it is handled, the opt-out applies to every read listed above, so we no longer sell or share your personal information through the API.
In your browser
The site stores your sign-in session, your theme choice and your analytics choice in your browser's local storage. We do not use advertising cookies.
Analytics
We use Google Analytics 4 to see which pages bring developers to the API and where sign-up or checkout fails. It records pages viewed, the referring site, an approximate location, device and browser type, and events such as signing up or starting a checkout. It never receives your email address, API keys or card details.
In the EEA, the UK, Switzerland and Canada, nothing loads until you accept. Elsewhere, analytics runs by default and you can opt out at any time: accepting (or that default) sets the _ga and _ga_<id> cookies, which Google keeps for up to 2 years by default; declining stops every send and removes them. Analytics data is kept for 14 months. Google Signals and ad personalisation are off.
The hosted MCP server at /mcp sends usage analytics to AgentCat for each tool call: which tool was called, whether it succeeded, how long it took and when, under an identifier that is a one-way hash of the API key's internal id. Each event also carries the server's name and version, the analytics library's version and, when your MCP client sends them, the client's name and version. It never sends your API key, the arguments you pass, the results or error messages you get back, or your IP address. The npm package you run on your own machine sends nothing.
You can change your choice at any time: .
Retention and your rights
We keep account and billing records for as long as your account is open and as long as tax law requires after that. You can ask for a copy of your data, a correction, or deletion of your account.
Contact
ProspectAPIs, which runs prospectapis.com and its API, is the controller of the personal data this policy describes.
For correction, removal, objection or Do Not Sell or Share requests and legal notices, email emma@prospectapis.com.
Building on ProspectAPIs? Create a free account, or read the API docs first.