Privacy policy for the ClearHire browser extension. Learn how we handle your data when using profile extraction and auto-fill features.
The ClearHire browser extension is currently in development and not yet released; this policy will apply once it ships. It covers what the extension specifically collects beyond the global ClearHire policy at /privacy. The extension is designed for limited-permission, opt-in interaction: it reads job-description pages only when you click "Log this application", does not read your browsing history, does not scrape sites passively, and does not access cookies or login-related data on host sites. Application metadata you log (URL, role, company, date applied) saves to your ClearHire account. The extension code is reviewed by Chrome Web Store, Firefox Add-ons, and Edge Add-ons for compliance with their privacy policies on every release.
Use cases
Understanding the extension permission model. The extension declares specific host permissions (LinkedIn, Indeed, Wellfound currently) needed to read JD pages on those sites. Activeness is opt-in: nothing happens without your click. The permission model is auditable in the extension manifest.
Confirming the extension does not access logins. The extension reads only the JD page content when you trigger a log action. It does not access cookies, session tokens, or any login-related data on host sites. Your LinkedIn / Indeed / Wellfound accounts stay private to those sites.
Reviewing what data syncs to ClearHire. Application metadata you log: URL, role title, company name, date applied. No JD body content uploads beyond the role title and company; the JD itself stays on the host site. Auditable in your tracker dashboard.
How it works
Read the global policy at /privacy first. The extension policy supplements the global one. Most data principles are the same; the extension policy adds specifics about host-site interaction.
Review the manifest permissions. Chrome Web Store, Firefox Add-ons, and Edge Add-ons all show the permissions an extension declares. Confirm they match the policy.
Audit your application logs in the tracker. Every logged application appears in your dashboard. Audit at any time to confirm what is stored.
Uninstall to remove all extension data. Uninstalling clears local extension storage. Server-side data (your tracker entries) stays in your account. To delete those too, use /data-deletion.
Examples
A privacy-conscious user evaluating the extension. Reads the policy and the planned manifest permissions, and reviews how application logs would be stored. Confirms only the metadata listed in the policy would be stored. Decides the extension will match their privacy bar and plans to install it once it is released.
Frequently asked questions
What will the ClearHire browser extension collect?
The extension is in development and not yet released. By design it will collect only application metadata you actively log (URL, role title, company name, date applied), saved to your ClearHire account. It will not read your browsing history, scrape sites passively, or collect data outside the explicit one-click application logging action.
Does the extension see my LinkedIn / Indeed / Wellfound logins?
No. The extension reads only the JD page when you click "Log this application". It does not access cookies, session tokens, or any login-related data on those sites. Your LinkedIn / Indeed / Wellfound accounts stay private to those sites.
Can the extension be reviewed for privacy compliance?
Yes. The extension is open about what it does; its manifest declares limited permissions. Once it is published, Chrome Web Store, Firefox Add-ons, and Edge Add-ons review every release for compliance with their privacy policies.
How is this extension policy different from the web policy?
Largely the same data principles; the extension policy adds specifics about the host-site interaction (which sites it can read JDs from, what triggers a read). The full extension policy is at /privacy-extension; the global policy is at /privacy.
Tips
The extension is opt-in: nothing happens without your click.
Manifest permissions are auditable in Chrome Web Store / Firefox Add-ons / Edge Add-ons listings.
Application logs are visible in your tracker dashboard at any time.
Uninstalling clears local extension storage; use /data-deletion to remove server-side data too.
For security findings specific to the extension, follow /.well-known/security.txt rather than the public form.
Author: ClearHire Editorial · Last updated: 2026-05-06
Loading the full ClearHire experience. If this page does not load, JavaScript may be disabled — please enable it or browse our sitemap.