Privacy Policy

Leadmaps, by Auradevs · Last updated: 18 June 2026

1. Who we are

Leadmaps is a desktop/CLI lead-generation tool published by Auradevs ("we", "us"). This policy explains what data the software touches and how.

2. What the software does with data

• Where it runs: on your machine (or a server you host). It drives a browser to read public Google Maps business listings for the niche and city you specify.
• What it collects: only publicly-available business details (name, phone, website, address, ratings, hours, etc.) for the searches you run. It does not collect data about you.
• Where results go: to the destination you choose — a local file (CSV/Excel/PDF) or your own Notion / Google Sheet. The results are yours; they are not sent to us.

3. Connecting Notion / Google (OAuth)

• When you run leadmaps connect notion or leadmaps connect google, you authorize the app in your browser. The resulting access token is saved only on your computer at ~/.leadmaps/credentials.json with owner-only permissions.
• Scopes we request: Notion — permission to create and write to a "Leads" database in a page you grant. Google — spreadsheets and drive.file, i.e. permission to create and edit only the spreadsheets this app creates. We never request access to your other files, email, or contacts.
• Token exchange: the one-time exchange of an authorization code for a token is performed by our stateless auth broker so that no application secret is shipped in the software. The broker passes the token straight back to your machine and stores nothing — no tokens, no leads, no logs of content.
• Disconnect anytime: leadmaps disconnect notion|google|all deletes the token from your machine. You can also revoke access from your Notion or Google account settings.

3a. Google user data — Limited Use

Leadmaps' use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Specifically:

• What we access. Only Google Sheets and Drive, and only when you choose Google Sheets as a destination. Leadmaps creates one spreadsheet ("Leadmaps — Leads") and appends rows to it. The drive.file scope limits the app to files it created itself — it cannot see anything else in your Drive.
• Why we need it. Writing your leads into your spreadsheet is the feature. There is no narrower scope that permits creating a sheet and appending rows to it.
• We do not transfer it. Your Google data is never sent to us or to any third party. It moves directly between your computer and Google.
• We do not use it for advertising, and we do not sell it.
• No human reads it. Nobody at Auradevs can read your Google data — we hold no token and operate no server that receives it.
• We do not use it to train models, generalised or otherwise.
• Retention. Because we never receive it, we retain nothing. The token on your machine is deleted by leadmaps disconnect google.

4. The MCP server (if you use AI assistants)

If you run Leadmaps as an MCP server for an AI assistant, scrapes run on the machine hosting that server and any connection token is held in that server's memory for your session only. Each user's data is isolated; tokens are never shown in the chat.

5. What we do NOT do

• We do not receive, store, or sell your leads.
• We do not see your Notion/Google content or tokens.
• The software contains no advertising or third-party trackers.

6. Your responsibilities

You are responsible for using Leadmaps in compliance with applicable laws and the terms of the services it interacts with (Google, Notion, Google Workspace), and for how you use the leads you collect.

7. Changes & contact

We may update this policy; material changes will be reflected by the date above. Questions? Contact us at the email listed on our product/support page.