Chrome extension privacy policy

Privacy Policy
Last updated: March 16, 2026

This Privacy Policy describes how the LinkedIn GRC Lead Extractor Chrome extension (“the Extension”) handles information when you use it.

1. Data We Collect
The Extension reads publicly visible information on LinkedIn post engagement pages that you are already viewing while logged into your own LinkedIn account. Specifically, it reads:

Names of people who reacted to a LinkedIn post
Job titles of those people
This data is only collected when you actively click the “Extract GRC Leads” button.

2. How Data Is Used
The collected data is used solely to:

Filter for GRC and Compliance professionals
Generate a CSV file downloaded directly to your device
The Extension does not transmit any data to external servers. All processing happens locally in your browser.

3. Data Storage
The Extension does not store any data persistently. No data is saved to browser storage, cookies, or any remote database. Once the CSV is downloaded, the Extension retains no information.

4. Data Sharing
We do not sell, share, or transfer any data to third parties. The Extension has no backend server and makes no outbound network requests.

5. Permissions
The Extension requests the following permissions:

activeTab – To read the content of the LinkedIn post page currently open in your browser tab.
host_permissions (linkedin.com) – To inject a content script that scrolls and reads engagement data on LinkedIn pages.
No other permissions are requested or used.

6. Third-Party Services
The Extension does not integrate with any third-party analytics, advertising, or tracking services.

7. Children’s Privacy
The Extension is not directed at children under the age of 13 and does not knowingly collect data from minors.

8. Changes to This Policy
We may update this policy from time to time. The “Last updated” date at the top of this page reflects the most recent revision.

9. Contact
If you have questions about this privacy policy, please open an issue on the extension’s support page or contact the developer directly.