Extension privacy notice Extension privacy notice

What does this notice cover?

This notice covers version 0.5.0 of DataPit — LinkedIn Lookup, DataPit’s extension for Google Chrome. The Chrome Web Store requires every extension that handles user data to post a privacy policy, and this is ours. The DataPit privacy policy covers your account and the rest of DataPit.

What does the extension read on LinkedIn?

On a linkedin.com/in/ profile page, it reads five fields about the person whose profile you’re viewing:

• Their name.
• The profile address, cut down to linkedin.com/in/ and the profile name. Anything after the profile name is dropped.
• Their headline, which the extension treats as the job title.
• Their current company’s name.
• Their location.

To find them, it looks at the top section of the profile and at the browser tab’s title. If it can’t find the top section, it searches the rest of the page. A field it can’t find is left out. It sends nothing else from the page.

The extension also writes what it found to your browser’s developer console. If a field is missing, it also adds the page address, the tab title and up to 60 short lines of page text. That output stays on your computer unless you choose to send it to our support team.

Which pages does it run on?

Chrome loads the extension’s script on linkedin.com pages, because LinkedIn often changes pages without a full reload. The script checks the page address. On anything other than a linkedin.com/in/ profile, it hides its card and reads nothing more.

It also runs a small script on datapit.io. That script only tells the DataPit dashboard that the extension is installed, and which version. Apart from the local test addresses in the permissions table below, the extension doesn’t run on any other website.

What does it send to DataPit, and when?

Until you connect a key, the extension sends nothing. Once connected, it runs one lookup each time you open a profile page, including one you opened before. Lookups are limited to 60 an hour per workspace.

What does DataPit send back?

If the person is in DataPit, it returns their record with any email address partly hidden, plus the reveal price. If your workspace already revealed them, the details come back in full and the reveal is free. After a reveal, it returns the work email. The card shows these on the LinkedIn page, and the extension doesn’t save them.

Clicking a revealed value copies it to your clipboard. Nothing is copied unless you click.

What does it store on your computer?

It keeps up to two settings in Chrome’s extension storage: your DataPit API key, and any API address you save in its options. Without one, it uses https://datapit.io/api/v1. It stores no profiles, lookup results or browsing data.

Only the extension’s popup and background worker handle the key. The part that runs on LinkedIn never reads it, and the LinkedIn page’s own scripts can’t see it. Chrome deletes this storage when you remove the extension.

What does DataPit store from your lookups?

Only DataPit’s own administrators see the queues of missing people and title changes. When they accept a title change, the record’s title changes for every workspace. If DataPit’s team later adds a queued person to the database, every DataPit workspace can search their record.

DataPit’s servers also keep standard request logs, which include your IP address and browser details. DataPit keeps each reveal response, including the email, for 24 hours. A repeated request with the same request ID gets the same answer without a second charge.

How long does DataPit keep this data?

DataPit hasn’t published a retention period for queued profiles, reported title changes or request logs yet. It doesn’t delete queue entries automatically, even after its team resolves them. Its admin log also keeps a note of each resolved entry. Your account and billing records follow the retention section of the privacy policy.

Which permissions does it ask for, and why?

What doesn’t the extension do?

• It doesn’t read your browsing history. Apart from the local test addresses above, it runs only on LinkedIn and DataPit.
• It doesn’t open or load pages by itself. It only reads the profile you have open.
• It doesn’t send your LinkedIn messages, connections, feed or login details to DataPit.
• It sends data only to DataPit’s API, or to the API address you set in its options.
• It doesn’t store the contacts you reveal. They stay in your DataPit workspace.
• DataPit doesn’t sell your workspace’s data to third parties, as its privacy policy states.

How do you disconnect or remove the extension?

1. 1

   Disconnect in the popup

   Click the DataPit icon in Chrome’s toolbar, then Disconnect. This deletes the API key from the extension, and lookups stop.

2. 2

   Revoke the key in DataPit

   Disconnecting doesn’t cancel the key itself. In DataPit, go to Settings → API & Extension and revoke it, so it stops working everywhere.

3. 3

   Remove the extension

   Open chrome://extensions and click Remove on DataPit — LinkedIn Lookup. Chrome deletes the extension’s stored settings, including the key.

Removing the extension doesn’t delete what DataPit already stored from past lookups. The next section explains how to ask about that.

What are your data rights?

Depending on where you live, you may have rights to access, correct, export or delete your personal data. For your DataPit account, contact us and we’ll act on your request once we confirm it’s from you.

If your own details appear as a contact record in DataPit, use the opt-out form on the privacy page. It redacts records that match the email address you enter.

The opt-out form works by email address. It doesn’t clear queued LinkedIn profiles, which have no email address, or reported title changes. To ask about either, contact us.

How do you contact DataPit about privacy?

Use the contact page for any question about this notice or the extension. The last-updated date on this page shows when the notice last changed.

Last updated September 28, 2026