Clear boundaries for the visitor map.
The footer on every page automatically loads a MapMyVisitors map. This page explains what is sent, why it is used, and what the isolated widget cannot access.
Last updated · July 16, 2026Automatic, site-wide loading
The visitor map image loads without a click whenever a page containing the global footer opens. Its network request therefore begins during the page visit, even if the footer is not yet visible. No MapMyVisitors JavaScript runs in the parent page; selecting the map opens the provider’s public statistics page.
Data MapMyVisitors may process
According to the provider’s documentation, the service may receive or infer:
- IP address and approximate country, region, city, time zone, coordinates, or postal area
- Browser, operating system, device characteristics, language, and screen information
- The current page and referring URL when the browser makes them available
- Visit time, visit count, and session or interaction metadata
The embedded frame uses a no-referrer policy to minimize page-path disclosure in outbound requests. Browser behavior and future provider code can still affect which fields are available.
Purpose, recipient, and retention
This site uses the information to render the live map, understand broad geographic visitor origins, and review aggregate traffic. Requests go directly to MapMyVisitors. This site does not receive your precise GPS location and does not sell visitor data. Provider-side storage, retention, deletion, and rights requests are governed by MapMyVisitors policies.
What the map cannot access
The provider content is loaded as an image inside an opaque sandbox without same-origin access or camera permission. It cannot directly read the parent page DOM, browser-stored AI keys, camera streams, or research files uploaded to site tools. The provider receives only the network request metadata needed to return and measure the map image.
Local-first tools remain a separate boundary
Many research tools process data locally in the browser, while optional AI features send data only to a provider chosen by the user. Those tool-specific boundaries are described in their interfaces and tutorials. “Local-first” does not mean that the surrounding page makes no third-party request: the footer visitor map is the disclosed exception.
Session identifiers and browser controls
The provider states that it does not use cross-site tracking cookies, although service responses may attempt to set a technical session identifier. Whether it is accepted depends on browser and third-party cookie settings. Browser content blocking or DNS filtering can prevent the MapMyVisitors image request, in which case the map may show an error.
Provider documents
Read the provider’s current documents for its processing, retention, and contact details.
