Lead Qualifier privacy policy

For the Lead Qualifier Chrome extension. Last updated 28 September 2026.

Lead Qualifier reads the website you are looking at, when you click its button, and tells you what the business could be sold and how to reach it. It is built so that nothing about the pages you visit or about you leaves your browser.

What it reads

Only the tab you click the extension on, and only at that moment. Chrome's activeTab permission grants exactly that: the extension cannot see any other tab, and cannot see any page you do not click it on. It reads the page's code, the addresses of files the page loaded, a fixed list of names the page defines (such as fbq for the Meta Pixel), whether a cookie banner is on the screen, and the headers the site sends with the page (asking the site for the page once more, from inside that site). If the page shows no email address, it opens up to three of the same site's contact pages, from inside that site. With Pro's deep checks it also reads the site's public robots.txt file, to see whether the site shuts out the crawlers AI assistants use.

If you use Check a list, Chrome first asks whether the extension may read websites. With your permission it reads the home page of each site you listed (and its contact page when the home page shows no email), the way a search engine would. It never reads a site you did not list, and you can take the permission back at any time in Chrome's extension settings.

What stays in your browser

Everything it reads is analysed inside the extension. Leads you choose to save, the list of sites you checked (for the dashboard's overview) and a count of today's checks (for the free plan's daily limit) are stored in your browser's own extension storage. Your settings (which services you sell, the findings you switched off, the name, company and sending address you sign emails with, the languages and the theme) are kept in Chrome's synced extension storage, so they follow you to other computers where you use the same Chrome profile; if Chrome sync is on, Google keeps that copy as part of it. Nothing is sent to us: there is no account, no analytics, no tracking and no server of ours that receives page content or browsing history. Removing the extension removes its storage.

What it asks of other servers

• Google Tag Manager (googletagmanager.com): the site's own Tag Manager container, the same public file the site itself loads, to see the tags set up in it that wait for cookie consent. Only the container's ID, which is in the page, is sent.
• Google Public DNS (dns.google): public DNS records, looked up by domain name. The domain of an email address found on the page, to check that it can receive mail. With Pro's deep checks, the checked site's domain, to read its public SPF and DMARC records (whether its mail is protected from forgery). With Pro's spam check, the domain of the sending address you entered in the settings, to check the same records for your own mail. Only domain names are sent, never an address, a page or anything about you.
• WordPress.org (api.wordpress.org): the number of the latest WordPress release, at most once a day, to say whether a site is out of date. Nothing is sent.
• ExtensionPay (extensionpay.com), only if you upgrade, start the free trial or log in to a plan you paid for: payment is handled by ExtensionPay and Stripe, who receive the email address and payment details you give them (the trial asks for an email address only). We receive whether your subscription or trial is active.

What we never do

We do not sell, share or transfer any user data, we do not use it for anything but the extension's single purpose, and we do not use it to judge creditworthiness or for lending. The extension's use of information follows the Chrome Web Store User Data Policy, including its Limited Use requirements.

Contact

Lead Qualifier is made by Kostas Skutulas, Vilnius, Lithuania. Questions about this policy: info@itneeds.lt.