Privacy policy

How LeadCart handles personal data.

This page says what we collect about our customers, the visitors to this website, the people in our database and the people who use our extension for Chrome, why we collect it, who handles it for us, how long we keep it and what you can ask of us. Everything on this page is how LeadCart works today. Last updated on .

Who we are

LeadCart, and how to reach us.

LeadCart is a B2B lead database. Our customers search people and companies, reveal work emails and mobile numbers, and send their lists to the tools they use. LeadCart is run by NuMail Inc., a Delaware corporation whose registered office is at 651 N Broad St, Suite 201, Middletown, DE 19709, USA. NuMail Inc. also runs OutboundPass. This policy covers this website, the LeadCart app at www.leadcart.io, its API and MCP server, and the LeadCart extension for Chrome. In it, “we” means NuMail Inc., the company that runs LeadCart.

Write to us

Send questions and requests about personal data to founders@outboundpass.com, with the subject line “Privacy”. You can also write to us by post: NuMail Inc., 651 N Broad St, Suite 201, Middletown, DE 19709, USA.

If you use LeadCart

What we keep about you and your workspace.

You give us some of it when you sign up. The rest comes from what you and the other members of your workspace do in LeadCart.

Account

Who you are

Your email address, your name if you give it, the address of your profile picture if there is one, and whether you use LeadCart in English or Arabic. Clerk, the service that signs you in, keeps your sign-in codes and sessions.

Workspace

Your workspace

Its name, logo and time zone, its plan and credits, its members with their roles, and the email address of each person invited to join it, which the workspace’s audit log also records.

Your work

What you keep in LeadCart

Your lists and the records in them, saved searches and table layouts, the contacts your workspace revealed and the notifications we show you. When someone exports a list, we keep a copy of the CSV file, with the emails and mobile numbers in it.

Uploads

CSV files you upload

A CSV file you upload for enrichment becomes a list in your workspace, with all of its columns, and the task that processes it keeps the file’s name. To match a row to a profile, we send our data provider the row’s LinkedIn address, its email address, or the person’s name and company domain.

Connections

Tools, webhooks and keys

The tools you connected and their keys, the webhooks you added and the API keys you created, those made when you connect our Chrome extension included. Each time a list is sent to a tool, we keep a record of the tool, the campaign or list it went to, and how many leads were sent.

AI

Your AI settings

Your answers when you set up your workspace, such as your role, what you sell and who you sell to, which become your workspace’s instructions for AI, with the tone and model you choose. The prompts you write for a list and the answers written for its rows. Your own AI key, if you add one.

Signals

Watched job titles and signals

The job titles you watch, with their countries and the words you leave out, and the signals LeadCart finds for your workspace, such as a company that is hiring or has raised funds.

Records

Who did what, and what it cost

Each reveal, with who made it, when, and the credits it used. Your workspace’s audit log of actions such as reveals, exports, connected tools and API keys, with who did each and when. Counts of searches and lookups, with the names of the filters a search used but not what was searched for. When each API key was last used, and a log of the calls AI agents make over MCP, without what they sent. The progress and result of longer tasks, such as a bulk reveal or an enrichment.

Payment

No card details

LeadCart takes no payments on its own pages today. Until self-serve billing is connected, our team switches on a paid plan on request, and we keep the plan with your workspace. OutboundPass bills its own plans, on its own terms.

Not for sale

We don’t sell your data.

Visitors to this website

This website sets no cookies.

Its pages run no script, and set no cookie of their own.

  • No analytics, no ad pixel, no chat widget and no script of any other kind.
  • Fonts, pictures and the video come from this website only, so no other site learns of your visit through them.
  • Like any website, ours is served by a host, Vercel, which receives each request with your IP address and your browser’s details. We run no analytics on them.
  • If you are signed in to LeadCart, your browser sends the app’s cookies with each request to www.leadcart.io, the pages of this website included, and Clerk may renew its sign-in cookies.

Cookies in the app

A few cookies, none of them for ads.

When you sign up or sign in, the LeadCart app uses these cookies, all set for leadcart.io. None of them is used for analytics or advertising.

__session, __client_uat

Keeping you signed in

Clerk’s sign-in cookies, with the others Clerk sets for the same purpose. Clerk’s settings decide how long they last.

NEXT_LOCALE

Your language

Remembers whether you use LeadCart in English or in Arabic.

lc_onboarding_seen

The first setup

Remembers for one year that you left your workspace’s first setup, so this browser does not show it again.

lc_workspace

Which workspace to open

For someone who belongs to more than one workspace, the one to open. It lasts one year.

lc_slack_oauth

Connecting Slack

A one-time value, kept for 10 minutes while you connect Slack, so that the connection cannot be completed from another browser.

Browser storage

How your screens look

Light or dark mode, table layouts, the widths of panels and whether you have run a first search, kept in your browser. On the sign-in and sign-up pages, the email address you typed is kept until you close the tab. If the extension’s connect page loads itself again to reach the extension, it keeps that page’s address, with its one-time value, until you close the tab.

If you are in our database

What we hold about people at work.

Our customers search a database of people and the companies they work at, to find people to contact for business. If you are one of those people, here is what we hold, where it comes from and how to ask us to remove it.

  • What we hold. Professional details: your name, job title and headline, summary, photo, location, seniority and department, skills, languages, certifications, education and work history, the company you work at, links to your public profiles such as LinkedIn, and your follower and connection counts. Your work email address and mobile number, once a customer reveals them.
  • Where it comes from. From our data provider, a third party whose database LeadCart searches. Customers can also upload a CSV file of people, which we match to our data provider’s profiles.
  • Who sees it. Customers see your professional details in their search results. Your email address and mobile number stay hidden until a customer’s workspace reveals them. Then every member of that workspace can see them, export them and send them to their own tools.
  • How long. The records we fetch are kept in LeadCart’s database and used for every workspace. Nothing deletes them on a schedule today: we delete our copy of yours when you ask us to.
  • Removal. When you ask, we delete the copy LeadCart keeps of your profile, work email and mobile number, pass your request on to our data provider, and reply to you within 30 days.
  • What removal cannot stop. LeadCart searches our data provider’s database, so until our data provider removes you, a new search may find your public professional profile again, and a customer may reveal your work email or mobile number again. Copies already in customers’ workspaces, such as their lists and exports, or sent to their own tools, stay with those customers.

To be removed

Write to founders@outboundpass.com with the subject line “Privacy”, and give us the LinkedIn address or the work email we should look for.

The extension for Chrome

What our Chrome extension keeps, reads and sends.

The LeadCart extension for Chrome opens a side panel that shows the person or company behind the page you have open, and lets you reveal a work email or a mobile number with a key of your workspace. It gets that key in one of two ways: LeadCart makes it when you connect the extension, or you paste an API key. You open the panel from Chrome’s toolbar, or from a small LeadCart tab that the extension shows at the right edge of the websites you visit. This is everything it does with data.

Connecting

A key LeadCart makes, or one you paste

When you install the extension, it opens one tab on LeadCart’s connect page at www.leadcart.io: an ordinary visit to LeadCart, with the app’s cookies as on any other, whose address carries only a one-time value the extension made. If you are signed out, LeadCart asks you to sign in or sign up with the code it emails you. The page then asks the extension whether it is there, and the extension answers with its version, the random id it made once for this installation, whether it has a key and whether the one-time value is its own. When it is, or when you press Connect on that page, LeadCart makes a key in your workspace, and the page hands the key and your workspace’s name to the extension, which keeps the key. When you press Connect, the extension first gives the page a new one-time value. The key is never shown in full, and the extension takes messages from that page only. Connect LeadCart, in the extension, opens the page again. Or press Use an API key instead in its options, and paste a key.

The key

Five permissions, never above your role

A key made by connecting holds five permissions only: it can look people and companies up, read your lists, create lists and add to them, and reveal work emails and mobile numbers. Like any API key, it acts as you and never above the member role, so a viewer’s key can look up and read lists but cannot reveal or save. LeadCart keeps only its hash, names it “Chrome extension” followed by your email address, lists it with your workspace’s other API keys, where its admins and owner see it, and records in the audit log when it is made and revoked. In a workspace you have one such key for each installation of the extension you connect, and five at most: connecting a sixth revokes the one used least recently. Removing the extension and installing it again counts as a new installation, with a new key: the old one stays valid until an admin or the owner revokes it, or the limit of five does.

Kept in your browser

Your key and a few values, on this computer only

Your key, whether it came from connecting or was pasted, whether you closed the note about costs, and the random id the extension made once for this installation, which LeadCart’s connect page uses so that connecting this installation again replaces its key instead of adding one. While you connect, also the one-time value and the tab it was given to, in memory that Chrome clears when the browser closes. They stay in the storage Chrome gives the extension, in this browser profile only. They are never synced, and only the extension itself can read them. The only values Chrome may sync are the two settings of the LeadCart tab, whether it shows and where it sits, described below. The extension keeps no history of pages or lookups.

Read from the tab

The address of the tab, never the page

While its panel is open, the extension reads the address and the title of the tab in front, in that window, to offer the right lookup. Chrome counts this as reading your browsing history. The extension never reads the page itself.

Made shorter

Only a profile or a domain

Before anything is sent, the extension shortens the address in your browser. A LinkedIn profile becomes the profile’s address, a LinkedIn company or school page becomes that page’s address, and any other website becomes its domain alone: shop.acme.co.uk becomes acme.co.uk. Browser pages, local and private addresses, LeadCart’s own site, and LinkedIn’s feed and search pages give nothing. The title is only used to show a name on a LinkedIn profile, and is never sent.

Sent to LeadCart

Only to LeadCart, and lookups only when you press a button

When the panel opens, when a new key arrives while the panel or the options page is open, when Chrome gives the extension back its access while the panel is open, and when you press Test connection, Try again or Allow access, the extension checks the key with LeadCart, which answers with your workspace, plan and credits. Apart from what it answers the connect page, as said above, everything else is sent only when you press a button: the short address to find the person or the company, a request for the company’s people 10 at a time, a reveal of the person’s work email or mobile number, a refresh of your credit balance, a request for your lists and the person you add to one when you save a person, and, when you press Disconnect on a key made by connecting, a request that revokes it. The extension’s own requests go only to LeadCart at www.leadcart.io, with your key in a request header and without your browser’s cookies.

Shown in the panel

Results stay only while the panel is open

The panel shows what LeadCart answers: a person’s name, job title, company, location and photo, a company’s details and people, and the contacts you reveal. It forgets them when it closes. A value goes to your clipboard only when you press Copy. Photos and logos load straight from the image hosts the record names, such as LinkedIn’s, without telling them the page they are shown on, but those hosts see your IP address and browser details.

At LeadCart

No list of the pages you looked up

A person or company fetched for a lookup is kept in LeadCart’s database, which serves every workspace. The request, with the short address but not your workspace, is kept for up to two days. LeadCart keeps no list of the addresses you looked up. A reveal or a save is recorded in your workspace like any other, with who did it and when.

On websites

A LeadCart tab that opens the panel, on by default

On every website except LeadCart’s own, the extension shows a small LeadCart tab at the right edge of the window. Pressing it opens the side panel next to that page, as the LeadCart icon in Chrome’s toolbar does. You can drag the tab up or down the right edge, and it stays where you leave it, on every page. The tab reads nothing from the page, not its text, links, forms, address or title, and sends nothing to LeadCart or to the site: a press only asks the extension to open its panel in that window, and the panel then works as this section says. The site’s own scripts can see that the tab is on its page, where it sits on the edge (the same place on every site), and when it is pressed or moved, but nothing inside it. The tab is on by default. Turn off “Show the LeadCart tab on websites”, in the side panel or in the options, and it disappears from every page at once; turn it on and it comes back. The tab’s two settings, whether it shows and where you left it, are kept in Chrome’s synced storage, so they follow your Chrome profile: if you sync Chrome, they reach every Chrome browser you are signed in to, and if you do not, they stay in this browser.

Chrome’s warning

Why Chrome speaks of all websites

Because the LeadCart tab can appear on any website, Chrome warns when you install the extension that it can read and change all your data on all websites. The warning says what an extension that runs on every website could do, not what this one does: it reads nothing from the pages you visit, and changes nothing in them apart from adding its tab.

  • No analytics, no ads, no code loaded from elsewhere, and no requests to anyone but LeadCart, apart from the photos and logos above.
  • To hide the LeadCart tab and keep the extension, turn off “Show the LeadCart tab on websites” in the side panel or in the options.
  • To stop, press Disconnect in the extension’s options. It deletes the key from your browser and, for a key made by connecting, first revokes it at LeadCart; if LeadCart cannot be reached, the key is deleted all the same and stays valid until it is revoked under Settings, API keys. A pasted key is only deleted from your browser: it stays valid until an admin or the owner of your workspace revokes it there, where they can revoke any key. Removing the extension from Chrome deletes what it kept in this browser, but does not revoke its key. Every key also stops working when the member it acts for leaves the workspace.

Limited Use

The use of information received from the LeadCart Chrome extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Why we use it

To run LeadCart for you, and to keep it safe.

  • To sign you in, and to keep you signed in.
  • To give you what you ask LeadCart for: searches and lookups, reveals, lists, exports, CSV enrichment, and lists sent to the tools you connect.
  • To count your credits and your usage, and to show them to you.
  • To keep your workspace’s audit log.
  • To keep LeadCart safe: limits on how many requests can be made, and protection of sign-in.
  • To answer you when you write to us.
  • Not for advertising: LeadCart shows no ads, and neither this website nor the app runs analytics or tracking scripts.

Who handles it for us

The services LeadCart runs on.

These services handle personal data for us, each for the part of LeadCart it runs.

Vercel

Hosting

Hosts this website, the app and the API. Every request to www.leadcart.io passes through it.

Neon

Database

Runs LeadCart’s database in the United States, where everything this page says we keep is stored. The app’s connections to it are encrypted.

Clerk

Sign-in

Runs sign-up and sign-in, sends your sign-in codes by email and keeps your sessions. It also checks sign-ups for automated abuse, with a protection service that is part of Clerk.

Our data provider

The source of the database

Answers searches, lookups and reveals. It receives what it needs to answer: the filters of a search, a LinkedIn address or a company domain, its own id for a person, or a person’s name and company domain. From a CSV file you upload, it may also receive a row’s email address.

  • Pictures. People’s photos and company logos load in your browser straight from the image hosts the record names, such as our data provider’s and LinkedIn’s. Those hosts see your IP address and browser details.
  • Tools you connect. When a member of your workspace sends a list to a tool, such as a CRM or an email tool, the leads go to that tool under your own account with it. Slack receives only a list’s name and counts. A webhook you add receives events with counts and ids, and a new signal adds the company; no event carries a revealed email or mobile number. An AI agent you connect over MCP receives what it asks for with your API key.
  • Your own AI key. If your workspace adds its own key for an AI service in its settings, LeadCart sends that service, under your key, what your workspace’s AI requests need, such as the details of the leads in a list.

How long we keep it

Kept while your account is active.

Most of what LeadCart keeps has no end date in the product today. We keep it while your account is active, and when you ask us to delete it, we do so within 30 days. These things have a set lifetime:

  • Search requests. A request sent to our data provider for a search or a lookup, with the list of results it returned, is kept for up to two days, so that the same request can be answered again.
  • Unfinished exports. An export that stopped before it finished is deleted within two days.
  • Cookies and browser storage. lc_onboarding_seen and lc_workspace last one year, and lc_slack_oauth 10 minutes. What a sign-in page or the extension’s connect page keeps in your browser ends when you close the tab.
  • The extension. Your key stays in your browser until you press Disconnect or remove the extension, and the one-time value of a connection until it is used or the browser closes. What else it keeps stays until you remove the extension, the two settings of the LeadCart tab included. At LeadCart, a key made by connecting stays valid until it is revoked: by Disconnect, by an admin or the owner, or when you connect a sixth installation and it is the one used least recently; connecting the same installation again replaces it with a new key. A pasted key stays valid until an admin or the owner revokes it. Removing the extension revokes neither.
  • What you delete. A saved search or a webhook you delete is deleted, and so is a tool’s key when you disconnect the tool. A list you delete leaves your workspace, but its rows stay in our database until you ask us to delete them. A revoked API key stops working at once, and stays listed as revoked, except a key made by connecting the extension: if the same installation connects again, its entry is listed as active again, with a new key.

Your rights

What you can ask of us.

Whether you are a customer or one of the people in our database, you can ask us for any of these.

  • See it. Ask what we hold about you, and for a copy of it. In the app, any list can also be exported to a CSV file.
  • Correct it. Ask us to correct what is wrong.
  • Delete it. Ask us to delete what we hold about you. If you are in our database, see what removal covers above.
  • Close your account. There is no button for this in the app. Write to us from the address you sign in with, and within 30 days we close your account and delete your workspace, with its lists, exports, API keys and connected tools, except any records the law requires us to keep.
  • Stop the extension. Press Disconnect in its options: it deletes the key from your browser and revokes a key made by connecting. A pasted key stays valid until an admin or the owner of your workspace revokes it under Settings, API keys. Removing the extension does not revoke its key.

How to ask

Write to founders@outboundpass.com with the subject line “Privacy”. If you have an account, write from the address you sign in with, so we know the request is yours. We reply within 30 days.

Security

How we protect it.

  • You sign in with a code sent to your email address, so there is no password to guess or leak.
  • Each workspace sees only its own lists, reveals, connected tools and keys.
  • The keys of the tools you connect, your own AI key and the secrets of your webhooks are stored encrypted with AES-256-GCM. API keys are stored only as a hash.
  • The app’s connections to its database are encrypted.
  • The pages of this website run no script, and tell browsers to use HTTPS for every visit.

How we protect your account and your data

Changes

When this policy changes.

We change this page when LeadCart changes what it collects, why it collects it or who handles it for us, and we put the date of each new version at the top of this page.

Start on the free plan.

Create an account with your email address. We send you a code to sign in, so there is no password to remember.