Privacy

MapMons Privacy Policy

Effective date: 27 July 2026

MapMons has no analytics, telemetry, advertising system, or MapMons backend account. MapMons does not sell user data. Research-session data stays on the user's device except for the optional, user-triggered transfers described below.

Data MapMons handles

MapMons handles the business information already visible in the user's Google Maps tab to display lead badges, filter the current research session, and export CSV files. This can include business names, visible phone numbers, ratings, review counts, website URLs, addresses, categories, and Google Maps URLs.

Where a listing names an individual sole trader or uses a personal phone number or address, those public business fields can identify that person. MapMons handles them only for the user-facing research and export features described here.

If the user enables Website Audits, MapMons fetches the public homepage linked from a listing. Pages are analysed locally and not sent to MapMons.

Users can disable Website Audits at any time from the MapMons popup or options page. This revokes MapMons's optional website access and returns real-site listings to the unaudited Audit state until access is enabled again.

If the user connects DataForSEO, MapMons sends the supplied API login and password directly to DataForSEO for validation. It sends a business domain to DataForSEO only after the user clicks the cost-labelled backlink button. MapMons never makes automatic paid DataForSEO requests.

If a paid user chooses AI opener polishing, MapMons first displays a prominent per-lead disclosure and asks for confirmation. Only after confirmation, MapMons sends that business's name, rating, review count, Maps category, website-status hook, and three draft openers over HTTPS to the MapMons endpoint and then to OpenAI to generate three refined openers. Phone numbers, addresses, Maps and website URLs, website content, DataForSEO credentials, and the OpenAI credential are not sent. Cancelling the disclosure sends nothing.

Local storage and retention

Current-session lead rows stay in the Google Maps tab. When the user invokes Continue in another area, MapMons keeps the deduplicated Hunt, reads coordinates already present in the visible Maps URL and place-result links, and uses a bundled offline Natural Earth place catalog to select the closest unvisited significant place in the same inferred country. It then submits a visible same-trade Maps query and resumes only after Maps loads it. That continuation action uses no location lookup, AI service, API key, or background area scan; if coordinates or native Maps controls are unavailable, MapMons preserves the Hunt and asks the user to choose the area. Lead rows are deleted when the user clears the session, reloads or closes the tab, or unloads the extension. Chrome local storage holds filter settings, aggregate counts, opener templates, optional DataForSEO credentials, and cached results. Website-audit cache entries expire after 7 days; backlink results expire after 30 days.

MapMons stores only an opaque ExtensionPay payment identifier in Chrome sync storage. When checking whether Pro is active, MapMons sends that identifier directly to ExtensionPay. For an approved AI request, it also sends the identifier to the MapMons endpoint for the same paid-status check; the endpoint does not persist it and sends only a one-way hash to OpenAI as a safety identifier. ExtensionPay's response can contain an email address, paid status, plan, payment date, subscription status, and cancellation date; MapMons reads only the paid boolean in memory and does not retain the returned account record. MapMons deletes account records cached by pre-release builds. It restricts both local and sync storage access to trusted extension contexts. If Chrome Sync is enabled, Chrome may sync the opaque identifier across the user's signed-in Chrome profiles.

MapMons keeps AI-refined openers only in the current badge's memory so the user can copy them. The MapMons endpoint does not persist the lead payload or generated openers. OpenAI API requests use store:false; OpenAI does not use API inputs or outputs for model training by default, but may retain prompts, responses, and related metadata in abuse-monitoring logs for up to 30 days.

DataForSEO credentials are restricted to trusted extension contexts and are not returned to the Google Maps content script. Users can delete them and their backlink cache with Disconnect and delete DataForSEO data in MapMons options. Clear cache deletes cached audit results. Removing MapMons clears its local extension storage from that Chrome installation; Chrome controls any synced copies under the user's Chrome Sync settings.

External services

ExtensionPay and Stripe process checkout and payment-card details outside MapMons; MapMons does not receive or store card details. MapMons's first-party payment client sends the opaque identifier to ExtensionPay and reads only the paid boolean from the returned account record. The MapMons Vercel endpoint processes confirmed AI-opener requests, verifies paid access, calls OpenAI, and returns the three generated lines without application-level payload storage. OpenAI processes the disclosed fields under its API data controls. DataForSEO processes credential validation and user-triggered backlink requests. Public business websites receive a direct homepage request only when Website Audits are enabled. See ExtensionPay, OpenAI API data controls, and DataForSEO for their policies.

Limited Use

MapMons uses handled data only to provide its user-facing Google Maps lead-research, website-audit, filtering, export, optional AI-opener, and optional backlink-check features. The MapMons/OpenAI transfer occurs only after the user's per-lead confirmation and only to provide AI-refined openers. MapMons personnel do not read those payloads or outputs. MapMons does not use or transfer handled data for advertising, credit decisions, data brokerage, profiling, or unrelated model training. MapMons's use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Questions or deletion help: support@mapmons.com.