Privacy policy

Effective November 19, 2026. We collect the information needed to run your workspace and understand whether the product is useful.

Account and authentication

We store your email, role, license state, hashed one-time codes, hashed session identifiers, and security rate-limit counters. Session cookies are necessary for sign-in. Codes expire after 10 minutes; expired authentication records are removed by scheduled cleanup. If you choose Continue with Google, we request only Google's basic profile scopes (openid, email and profile) and receive your name, your Google-verified email address and your Google account ID. We store the email and Google account ID to sign you in and match your account later; for a new account, your name pre-fills the sender name in your outreach signature, which you can change. We do not receive your Google password or access to your contacts, Gmail, Drive or other Google data. A short-lived cookie protects the Google sign-in step and expires after 10 minutes.

API credentials and business records

Your DataForSEO API login and password are encrypted using AES-GCM before storage in Cloudflare D1. They are decrypted only server-side for your requests. We store your searches, saved leads, enrichment, notes, and lists. Website contact data comes from public business pages. Business listings returned by DataForSEO are also kept in a shared store of public business facts (name, category, address, phone, website, rating, review count, hours, claim and open status) with a history of how those facts change, together with a compressed archive of each DataForSEO request and response. Your credentials are never written to that store or archive. If you repeat a search within 30 days, we serve the saved results instead of calling DataForSEO again, so it costs you nothing; you can refresh from DataForSEO at any time. Website checks and extracted public emails are shared across accounts by website domain and reused for 14 days instead of crawling the site again. Public business data in these stores may be used across Leads by Map and in our other products and services; it is never linked to your notes, lists or account details.

Analytics and traffic tracker

We record a small first-party event log in D1 for signups, key connection outcomes, search and enrichment counts/costs, exports, checkout, purchases, and refunds. It excludes keys and raw lead contact details. We store first-touch referrer, landing URL, and UTM tags on accounts. On www.leadsbymap.com we also use PostHog for product analytics and session replay. It receives page views, clicks, the named product events above, referrer and UTM tags, browser and device details, and an approximate location derived from your IP address. After you sign in, these are linked to your account ID and email. Session replay records page layout and interactions with every form field masked, so typed text, DataForSEO credentials, email addresses and sign-in codes are never recorded; lead details, extracted emails and your account email are masked as well. PostHog uses a first-party cookie and local storage to recognize your browser. When you follow a DataForSEO sign-up link, we record which page it came from before sending you to DataForSEO's affiliate link. Every page on www.leadsbymap.com also loads the Ship or Die hackathon traffic tracker (verify.js from ship-or-die.com), which lets the contest organizers verify our traffic sources. It receives your IP address, browser details, the page you visit and its referrer. Do not put sensitive information in page URLs.

Service providers

Cloudflare hosts the application, database, jobs, exported files, and authentication email. Google handles sign-in when you choose Continue with Google. DataForSEO processes your searches under your account. Stripe handles payments; we do not store card numbers. Ship or Die receives traffic-tracker data to verify our hackathon entry. PostHog Inc. (US cloud) processes product analytics and masked session replays as our processor, through a first-party path on our domain. OpenFreeMap supplies map tiles. Area suggestions come from our own copy of GeoNames place names (CC BY 4.0) and US Census ZIP code centers, so what you type there stays with us. Areas that aren't in that list are looked up with OpenStreetMap Nominatim with caching; your search location is sent to it. When you choose Use my location, your browser shares your position only after you allow it; we use it to name the nearest town and, if you run that search, as its center.

Retention and deletion

Your workspace remains until you delete your account. Saved search results are reused for up to 30 days and website checks for up to 14 days; the shared business-listing store, its change history, website check history and the DataForSEO response archive are kept indefinitely because they describe public businesses, not you. Public website cache lasts up to 24 hours, geocoding cache up to 30 days, and downloadable files up to 24 hours. Error and email delivery logs are retained for up to 30 days. Deleting your account removes credentials, sessions, searches, lists, leads, notes, and files, and removes your account link from the shared business-listing store, saved search results and response archive. Billing and aggregate event records may remain without an account link for accounting and fraud prevention.

Your choices and contact

Disconnect your API key in account settings, workspace records, or delete your account. Contact support@leadsbymap.com to request access, correction, or help with deletion.