LinkedIn Company Page Extractor — Privacy Policy

1. Introduction

This privacy policy describes how the LinkedIn Company Page Extractor browser extension ("the extension") handles information when you use it. The extension is published by JSK Business Solutions Pvt Ltd under the NameToProfile brand. The same codebase is distributed both as a Chrome extension (via the Chrome Web Store) and as a Firefox add-on (via Firefox Add-ons, addons.mozilla.org); this policy applies to both distributions.

The extension has one purpose: to help you extract structured data from LinkedIn company pages that you are already viewing in your browser and export that data locally as Excel, CSV, JSON, or clipboard-ready tab-separated text.

This policy applies only to the LinkedIn Company Page Extractor browser extension. It does not cover other NameToProfile products, services, or website features.

2. What data the extension accesses

The extension accesses data only on LinkedIn company pages that you, the user, have actively opened in your browser. Specifically, it reads publicly visible content from pages matching:

https://www.linkedin.com/company/*

On those pages, the extension may read the following fields directly from the rendered page content:

• Company name
• Company ID
• Logo image URL
• Summary
• Overview / "About" description
• Website
• Industry
• Company size
• Followers
• Employees on LinkedIn
• Headquarters
• Founded year
• Specialties

The extension does not access:

• Any page outside https://www.linkedin.com/company/*
• Your LinkedIn account credentials, direct messages, or notifications
• Your browsing history, search history, or unrelated tabs
• Any personal data about you as a LinkedIn user
• Any other website you visit

The extension does not perform any form of general browsing tracking.

3. What data is stored locally in your browser

The extension stores the following items in your local browser profile using the standard browser extension local-storage API (chrome.storage.local in Chrome, the equivalent browser.storage.local in Firefox). This data is kept on your device and is not transmitted to us or to any third party:

• Your NameToProfile API key (required for the extension to function)
• Your NameToProfile API key status, usage status, and remaining credit information (cached from responses to the API calls described in section 4)
• Your field preferences (which optional fields you have chosen to include in exports)
• The most recently extracted company record (used by the "Copy Row" feature)
• Bulk capture session data, including any company records you have captured during an active bulk capture session, stored until you clear them or uninstall the extension

All locally stored data remains on your own device. No locally stored data is uploaded to us, shared with third parties, or backed up to any remote service by the extension.

4. What data is sent to our API

The extension contacts only one backend endpoint, operated by NameToProfile:

https://api.nametoprofile.com

The extension sends requests to this endpoint only for the following purposes:

• API key validation — confirming that the API key you have entered is recognized and active on your NameToProfile account.
• Usage and credit status checks — reading your current credit balance so the extension can display it to you.
• Bulk eligibility checks — confirming that your account is eligible to start a bulk capture session based on your available credit headroom. This check is advisory and does not consume credits.
• Approved brief list — listing your approved ICP briefs so you can choose one to score against. Does not consume credits.
• Account scoring — when you click Fast score or Deep AI score on a company, a snapshot of that company is sent to be scored against your selected brief. This consumes credits (see below) and is the only request that carries extracted company data.

These requests carry:

• Your NameToProfile API key, sent in the X-API-Key request header
• Standard HTTP metadata (request method, path, timestamp, your IP address as seen by the server)
• For scoring only: the company snapshot described below, plus your selected brief's ID

Apart from account scoring, these requests never carry extracted LinkedIn company data — only your API key and standard metadata. The account-scoring snapshot contains the company's public fields shown on the page: name, company ID and LinkedIn URL, industry, company type, size, headquarters and other locations, founded year, specialties, follower and employee counts, and funding information. Fast score costs 1 credit; Deep AI score costs 20 credits; results are cached for 24 hours per company per brief (a cache hit costs nothing). Scoring runs only when you click.

5. Extraction and export run in your browser; scoring is the one exception

The one exception is account scoring (section 4): when you click Fast score or Deep AI score, a snapshot of the company you are viewing is sent to the NameToProfile API to be scored against your selected brief. This happens only on that click. No other extracted company data is transmitted, and the account-status calls (validation, usage, brief list) carry no company data.

6. How the data is used

• Locally stored data is used solely to operate the extension's user-facing features: maintaining your saved API key, displaying your field preferences and credit status, enabling the Copy Row feature, and allowing you to continue or export an active bulk capture session.
• Data sent to our API (API key and request metadata) is used solely to validate your account, return your credit status, and decide whether a bulk capture session is allowed to start.
• No data collected by the extension is used for advertising, profiling, analytics tracking, behavioral targeting, or any purpose unrelated to the user-facing extraction and export feature.

The extension does not inject advertisements into any web page.

7. Data sharing

We do not sell, rent, trade, or share data collected by the extension. Specifically:

• We do not sell extracted LinkedIn company data. We receive a company snapshot only when you score, and we never sell it.
• We do not share your API key or account-status data with any third party.
• We do not use extracted LinkedIn company data for advertising purposes.
• We do not provide data collected by the extension to data brokers, marketing partners, or affiliates.

The only transmission of data outside your device that the extension performs is the account-status API calls described in section 4, and those calls go only to our own backend at https://api.nametoprofile.com.

8. Retention and deletion of locally stored data

All data stored by the extension lives in your own browser's local storage on your device. You remain in control of that data at all times:

• Clearing within the extension — the extension's user interface provides controls to sign out (remove the stored API key), stop a bulk capture session, remove individual captured companies from a bulk session, and clear captured bulk session data stored locally in the browser.
• Clearing via your browser — you may remove all extension storage at any time via your browser's extension settings. In Chrome: chrome://extensions → Details → "Clear storage". In Firefox: about:addons → Extensions → LinkedIn Company Page Extractor → the gear icon → Remove. You can also clear your browser's site and extension data, or simply uninstall the extension — uninstalling removes all of its locally stored data.
• Retention on our servers — company data you extract and export is never sent to us. Company snapshots you score are processed and retained by the NameToProfile API under our main privacy policy (including a 24-hour scoring cache). API calls may be kept in server-side request logs for a limited period for security, debugging, and rate-limit enforcement; those logs contain request metadata and the API key prefix.

9. User controls

You have the following controls over the extension's behavior and data:

• Install and uninstall. Uninstalling the extension removes all of its locally stored data from your browser.
• Enter, rotate, or remove your API key via the extension's popup settings screen. Rotating the API key from your NameToProfile dashboard invalidates the previous key immediately.
• Turn off bulk capture by clicking Stop Session at any time. You may also clear all captured companies from the local session without stopping it.
• Choose which fields to extract via the Fields panel in the extension popup. Deselecting a field prevents it from appearing in previews and exports.
• Manage the extension's permissions via your browser's extension settings (chrome://extensions in Chrome, about:addons in Firefox). You may disable the extension entirely without uninstalling it.

10. Browser permissions in use

The extension requests the following browser permissions using the WebExtensions API (supported by both Chrome and Firefox). Each permission is used only for the purpose stated:

• activeTab — access the currently open LinkedIn company page tab so the extension can read its content when you click Extract Data.
• storage — store your API key, field preferences, most recently extracted company record, and bulk capture session data locally in your browser via the browser's extension local-storage API.
• scripting — inject the extension's content script into the active LinkedIn company page to read its content for extraction.
• clipboardWrite — write the "Copy Row" output (tab-separated company data) to your clipboard when you click Copy Row.
• Host permission for https://www.linkedin.com/* — allow the content script to run on LinkedIn so the extension can read company page content from pages you have already opened.
• Host permission for https://api.nametoprofile.com/* — allow the extension to make the account-status API calls described in section 4.

The extension does not request permissions to read or modify any other site.

11. Security

We take reasonable steps to protect the extension and the limited data it transmits:

• All communication between the extension and our API (https://api.nametoprofile.com) is encrypted in transit using HTTPS.
• The extension's API key is stored only in your own browser's extension local storage (chrome.storage.local in Chrome, browser.storage.local in Firefox) and is transmitted only in the X-API-Key request header when the extension calls our API for the purposes described in section 4.
• The extension does not load remote code at runtime. All extension code ships inside the extension package published to the browser's extension store (Chrome Web Store or Firefox Add-ons).
• If you suspect your API key has been exposed, you can rotate it immediately from your NameToProfile dashboard, which invalidates the previous key.

While we use reasonable safeguards, no method of electronic transmission or storage is perfectly secure. We cannot guarantee absolute security.

12. Children

The extension is not directed to children, and we do not knowingly collect information from children. If you believe a child has provided information in connection with the extension, please contact us at info@nametoprofile.com.

13. Changes to this policy

We may update this privacy policy from time to time. When we do, we will revise the "Last updated" date at the top of this page and publish the revised version on this page.

14. Contact

If you have questions about this policy or about the extension's handling of your data, contact us at:

• Email: info@nametoprofile.com
• Publisher: JSK Business Solutions Pvt Ltd (operating as NameToProfile)
• Website: https://nametoprofile.com

15. Chrome Web Store Limited Use statement