LeadForge privacy policy

Last updated: 18 November 2026

LeadForge is a Chrome extension that finds publicly listed local businesses and their published contact details. This page says what it handles and where that data goes.

In short: LeadForge has no server and no account system. Everything it collects is stored in your own browser, and the developer receives none of it.

What the extension handles

DataWhere it comes fromWhere it is kept
Your searches (business type, place, map pin)You type themChrome's local extension storage on your device
Business listings and contact details (name, address, phone, email, website, social links, rating, short review excerpts if you switch them on)Public pages: Google Maps, Bing Maps, Yellow Pages, OpenStreetMap, and the businesses' own websitesYour device
Your notes, and saved / contacted / blocked marksYou enter themYour device
Leads you import from a spreadsheetA file you chooseYour device
Zoho Mail credentials, Telegram bot token, AI provider API keys, sender name and postal address — only if you set those features upYou enter themYour device
Your location — only if you press "use my location" in the map pickerThe browser, with your permissionUsed once to centre the map; not stored
Your computer's time zoneThe browserRead on your device to add the right country code to local phone numbers from Google Maps; never sent anywhere
Backup files — only if you press Back upYour leads, saved searches, blocklist and settings. Keys, passwords, tokens and webhook addresses are left outA file saved where you choose; the extension does not send it anywhere
Diagnostics — only if you press Copy diagnosticsYour version, browser, settings ("set" or "not set" in place of any credential) and recent error messagesCopied to your clipboard. Nothing is sent; you decide whether to paste it into a message

What leaves your device

The developer receives nothing: no analytics, no telemetry, no crash reports, no copy of your leads.

The extension makes requests only to do what you asked:

Each of those services sees the request the way it would see a browser tab, and handles it under its own privacy policy.

What the extension does not do

Chrome Web Store Limited Use

LeadForge's use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only to provide the lead-finding features described on this page.

Why the extension asks for its permissions

PermissionWhat it is used for
Access to websitesReading map listings and the public pages of the businesses a search finds. Which sites those are is not known in advance.
storage, unlimitedStorageKeeping your leads and settings on your device. The second lets a large lead list grow past Chrome's default 10 MB limit for extensions; it grants no other access.
tabs, tabGroups, scriptingOpening a Maps search in a tab, reading its results, and closing it when the search ends.
sidePanel, offscreenShowing the interface, and parsing fetched pages in the background.
alarmsKeeping a long search running, and scheduled re-runs if you turn them on.
clipboardWriteCopying emails, phone numbers and rows when you press a copy button.
geolocationCentring the map on you, only when you press "use my location".

Your controls

Data about other people

The contact details LeadForge collects describe businesses, but a sole trader's email or phone number can also be personal data. You are the controller of what you collect and how you use it: have a lawful reason to hold it, keep it no longer than you need, and honour objections and opt-outs.

Changes

If this policy changes, the new version is published on this page with a new date.

Contact

Questions about this policy can be sent to the developer contact address shown on LeadForge's Chrome Web Store listing.