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
| Data | Where it comes from | Where it is kept |
|---|---|---|
| Your searches (business type, place, map pin) | You type them | Chrome'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 websites | Your device |
| Your notes, and saved / contacted / blocked marks | You enter them | Your device |
| Leads you import from a spreadsheet | A file you choose | Your device |
| Zoho Mail credentials, Telegram bot token, AI provider API keys, sender name and postal address — only if you set those features up | You enter them | Your device |
| Your location — only if you press "use my location" in the map picker | The browser, with your permission | Used once to centre the map; not stored |
| Your computer's time zone | The browser | Read 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 up | Your leads, saved searches, blocklist and settings. Keys, passwords, tokens and webhook addresses are left out | A file saved where you choose; the extension does not send it anywhere |
| Diagnostics — only if you press Copy diagnostics | Your version, browser, settings ("set" or "not set" in place of any credential) and recent error messages | Copied 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:
- Google Maps, Bing Maps, Yellow Pages, OpenStreetMap / Overpass, and business websites — to read listings and contact pages.
- A web search engine — to find a website for a business that lists none.
- OpenStreetMap tile and Nominatim servers — to draw maps and look up place names.
- Cloudflare DNS-over-HTTPS — while "Check mail domains" is on (the default), to ask whether a domain accepts mail. The domain name is sent; no email is.
- Your webhook — only if you enter a webhook URL. Leads are then sent to that address, which you chose and control, when you press "Send to webhook" or, if you switch it on, when a search finishes.
- Telegram — only if you enter a bot token and chat id. A one-line summary of a finished search is sent through your own bot. No lead details are included.
- The AI provider you choose — only if you enter an API key and press "Write with AI". The provider is one of Anthropic (Claude), OpenAI, Groq, Google Gemini, OpenRouter, Mistral or DeepSeek, or a server address you enter yourself. The line you type describing your offer, and your sender name and company, are sent to draft an email. No lead is sent. "Find models" sends only your key, to list the models it can use.
- Zoho Mail — only if you set up cold email, to send the messages you compose from your own mailbox, using your own credentials.
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
- It does not sell or transfer data to anyone.
- It does not use data for advertising, profiling or credit decisions.
- It does not read your browsing history or pages unrelated to a search you started.
- It does not log in to sites on your behalf, bypass access controls or solve CAPTCHAs.
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
| Permission | What it is used for |
|---|---|
| Access to websites | Reading map listings and the public pages of the businesses a search finds. Which sites those are is not known in advance. |
storage, unlimitedStorage | Keeping 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, scripting | Opening a Maps search in a tab, reading its results, and closing it when the search ends. |
sidePanel, offscreen | Showing the interface, and parsing fetched pages in the background. |
alarms | Keeping a long search running, and scheduled re-runs if you turn them on. |
clipboardWrite | Copying emails, phone numbers and rows when you press a copy button. |
geolocation | Centring the map on you, only when you press "use my location". |
Your controls
- Settings › Data › Clear all leads removes every stored lead.
- Settings › Data › Back up saves a copy you keep; Restore brings it back on any computer.
- Removing the extension deletes everything it stored. Chrome may then open a short goodbye page on this website, which asks for nothing and stores nothing.
- Zoho access can be revoked at any time in the Zoho API Console; API keys can be revoked with the provider that issued them.
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.