Privacy Policy — LinkedIn Sourcer
Last updated: Apr 18, 2026
The short version
LinkedIn Sourcer runs entirely inside your browser. It has no backend server. It does not collect, store, or transmit your data to the developer. The only outbound connections it makes are ones you explicitly initiate — to OpenAI's API using your own key, and optionally to Apify's API using your own key if you choose to enable that feature.
What this extension does
LinkedIn Sourcer helps you find and score candidates on LinkedIn by reading search result pages in your browser, generating Boolean search queries, and scoring candidate profiles against a job description using an AI model. All processing happens locally in your Chrome extension instance.
Data we collect
We collect nothing. There is no developer-operated server, database, analytics service, or telemetry of any kind. The developer has no visibility into your usage, searches, or results.
Data stored on your device
The following is stored locally in chrome.storage.local — on your machine only, never transmitted to the developer:
- OpenAI API key
- Apify API key
- Preferred AI model
- Cached page selectors
- Candidate results
You can delete all locally stored data at any time from the Settings tab, or by uninstalling the extension.
Third-party services
This extension makes direct API calls from your browser to the following services. These connections only happen when you actively start a sourcing run. The developer is not a party to these connections and has no access to what is sent or received.
- OpenAI (api.openai.com): Candidate profile text snippets are sent to OpenAI for fit scoring using your own API key under your own OpenAI account. OpenAI's data handling is governed by their API usage policies.
- Apify (api.apify.com) — optional: Only contacted if you choose to supply an Apify API key in Settings. Calls are made using your own key under your own Apify account. Apify's data handling is governed by their privacy policy.
LinkedIn session
The extension reads LinkedIn search result pages using your existing logged-in browser session. It does not store, transmit, or proxy your LinkedIn credentials, cookies, or session tokens. It does not interact with LinkedIn on your behalf beyond navigating search pages during an active sourcing run.
Permissions used and why
- storage: Saves API keys, model preference, cached selectors, and results locally on your device
- sidePanel: Displays the extension UI alongside your LinkedIn tab
- tabs: Navigates LinkedIn search pages during a sourcing run and detects when pages finish loading
- linkedin.com: Allows the content script to read candidate data from LinkedIn search result pages
- api.openai.com: Allows direct API calls to OpenAI for candidate scoring
- api.apify.com: Allows direct API calls to Apify if you supply an Apify key