Sales Navigator Lead & Account Extractor — Privacy Policy

1. Introduction

This privacy policy describes how the Sales Navigator Lead & Account 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 capture the LinkedIn Sales Navigator lead and account search results you are already viewing in your own logged-in session, then resolve, score, and export those records — working with your NameToProfile account.

This policy applies only to the Sales Navigator Lead & Account Extractor browser extension. It does not cover other NameToProfile products, services, or website features.

2. Summary

• The extension runs in your browser and has no server of its own.
• It reads Sales Navigator search results from your own authenticated session, only on Sales Navigator pages, and stores them locally on your device.
• It sends data to the NameToProfile API (https://api.nametoprofile.com) only when you explicitly act — saving a page, resolving a URL, or scoring a record.
• We do not sell your data, show ads, or run third-party analytics or tracking in the extension.

3. What data the extension accesses

The extension only activates on LinkedIn Sales Navigator pages that you have actively opened, matching:

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

On those pages it reads the lead and account search results that your browser already loads, by observing the Sales Navigator search responses (it does not crawl, automate browsing, or make extra requests to LinkedIn). The captured fields can include:

• Lead name, headline / job title, and company
• Location and other firmographic fields
• Public and Sales Navigator profile identifiers / URLs
• Account (company) name and attributes
• Activity signals shown on the result (e.g. recent posting / job-change badges)

The extension does not access:

• Any page outside https://www.linkedin.com/sales/*
• Your LinkedIn account credentials, direct messages, or notifications
• Your browsing history, search history, or unrelated tabs
• Any other website you visit

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

4. What data is stored locally in your browser

The extension stores the following in your local browser profile using the standard extension local-storage API (chrome.storage.local in Chrome, the equivalent browser.storage.local in Firefox). This data stays on your device:

• Your NameToProfile API key (required for the extension to function)
• The lead and account records you have saved, plus any resolved URLs and scores
• The approved "brief" you have selected for scoring
• Per-page accounting (which pages you have already saved, so you are not charged twice) and your column / display preferences
• Cached account status (key validity and remaining credits) from the API calls in section 5

All locally stored data remains on your own device. It is not uploaded to us or shared with any third party except for the explicit NameToProfile API calls described in section 5.

5. What data is sent to our API

The extension contacts only one backend, operated by NameToProfile:

https://api.nametoprofile.com

It sends requests there only for these purposes, and only in response to your actions:

• API key validation, usage and brief list — confirming your key is active, reading your credit balance, and listing your approved briefs so you can pick one to score against. These do not consume credits.
• Save a page — when you select a page of results to save, the records on that page are sent to be recorded (1 credit per page, charged once per page).
• Resolve — when you resolve a Sales Navigator URL to a public profile URL (1 credit per resolve).
• Score — when you Fast score (1 credit) or Deep score (20 credits) a record against your selected approved brief. A cached result is not re-charged.

Requests carry:

• Your NameToProfile API key, sent in the X-API-Key request header
• Only the specific record(s) you chose to save, resolve, or score
• Standard HTTP metadata (method, path, timestamp, your IP address as seen by the server)

The extension does not send captured data in the background. Records leave your device only for the specific items you act on. That processing is governed by the NameToProfile privacy policy: nametoprofile.com/privacy.

6. Account isolation on a shared browser

Your saved data is tied to your NameToProfile account. If a different account signs in to the extension on the same browser profile, the extension deletes the previous account's local data and resets to default, so accounts never see each other's records. Rotating your own API key keeps your data intact.

7. How the data is used

• Locally stored data is used solely to operate the extension: your saved leads and accounts, scores, selected brief, preferences, and credit status display.
• Data sent to our API is used solely to record saved pages and to resolve or score the records you choose, and to validate your account and return your credit status.
• No data collected by the extension is used for advertising, profiling, analytics tracking, behavioral targeting, or any purpose unrelated to the extraction, resolve, score, and export features.

The extension does not inject advertisements into any web page.

8. Data sharing

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

• We do not sell your captured Sales Navigator data.
• We do not share your API key or account-status data with any third party.
• We do not provide data collected by the extension to data brokers, marketing partners, or affiliates.

The only transmission of data outside your device is to our own backend at https://api.nametoprofile.com, for the purposes in section 5.

9. Third-party code

The extension bundles the open-source SheetJS library locally to create Excel files. It loads no remote code at runtime — all extension code ships inside the package published to the Chrome Web Store or Firefox Add-ons.

10. Retention and deletion

• Clearing within the extension — you can clear the saved store, remove individual records, sign out (remove the stored API key), and reset preferences from the extension's interface.
• Clearing via your browser — remove all extension storage at any time via your browser's extension settings (Chrome: chrome://extensions → Details → "Clear storage"; Firefox: about:addons). Uninstalling the extension removes all of its locally stored data.
• On our servers — records you save, resolve, or score are processed by the NameToProfile API and retained under the NameToProfile privacy policy. API request logs may be kept for a limited period for security, debugging, and rate-limit enforcement; they contain request metadata and the API key prefix.

11. Browser permissions in use

• storage — to save your captured records, scores, selected brief, and settings locally in your browser.
• Host access to https://www.linkedin.com/* — to read the Sales Navigator search results you are viewing.
• Host access to https://api.nametoprofile.com/* — to call the validate, usage, brief, save, resolve, and score endpoints with your API key.

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

12. Security

• All communication between the extension and our API is encrypted in transit using HTTPS.
• Your API key is stored only in your own browser's extension local storage and is transmitted only in the X-API-Key header when the extension calls our API.
• The extension does not load remote code at runtime.
• If you suspect your API key has been exposed, rotate it from your NameToProfile dashboard — that invalidates the previous key immediately.

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

13. 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, contact us at info@nametoprofile.com.

14. 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 here.

15. Contact

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

16. Chrome Web Store Limited Use statement