Map plugin data paths
Where WordPress map plugins send map requests
A map on a public page can send visitor requests to an outside map service when the map loads. Some setups load the Google Maps JavaScript API. Others load map tiles from OpenStreetMap or a similar tile host. You can also serve tiles from your own host. This table summarizes the documented setups below. Your engine choice can change where map requests go.
Based on plugin documentation, not tests of your site. Your settings can change what loads. This is not legal advice or a compliance rating.
Scan your site for third-party requestsHow we group map plugins
We compare the map setups named below. A plugin can offer Google Maps and still use OpenStreetMap tiles when you pick that engine. We have not tested when requests start relative to cookie consent or assessed how long map-service logs are kept.
Map plugins
No paid placement. Tiles on your server first, then outside services, then plugins not yet reviewed. Names are alphabetical within each group.
| Plugin | Documented behavior | Receiving domains | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Leaflet Map Leaflet Map listing: default map tiles come from OpenStreetMap, not Google Maps. The plugin README default tile URL is tile.openstreetmap.org. Address lookup can use the OpenStreetMap Nominatim geocoder. You can point the tile URL at your own host. That self-hosted setup is not the default. We have not tested consent timing. | Outside map service | tile.openstreetmap.org | Not assessed | Not tested |
| |
| MapPress MapPress listing: the plugin works without an API key using Leaflet maps on OpenFreeMap (OpenStreetMap data). Google Maps and Mapbox are optional engines that need a key. Map records stay in WordPress; visitor map tiles still come from the engine you pick. The listing does not name a verified receiving host for the OpenFreeMap default. We have not tested consent timing. | Outside map service | Receiving domains not verified | Not assessed | Not tested |
| |
| Maps Widget for Google Maps Maps Widget for Google Maps listing: the thumbnail uses the Google Maps Static API, and the lightbox loads an interactive Google map. Google docs serve Static Maps from maps.googleapis.com. There is no documented non-Google tile engine in the free listing. We have not tested consent timing. | Outside map service | maps.googleapis.com | Not assessed | Not tested |
| |
| WP Go Maps This row covers WP Go Maps when the Google Maps engine is selected. The listing loads the Google Maps JavaScript API for that engine. Google docs serve that script from maps.googleapis.com. Leaflet, OpenLayers, and a zero-cost tile option are separate engines and are not this Google Maps row. We have not tested whether a consent tool on your site delays that script. | Outside map service | maps.googleapis.com | Not assessed | Not tested |
| |
| WP Store Locator WP Store Locator listing: onboarding picks a map service. OpenStreetMap (Leaflet) needs no API key. Google Maps, Mapbox, and Stadia Maps are other options. Store records stay in WordPress; map tiles and geocoding still go to the service you pick. The listing does not name a verified receiving host for a single default engine. We have not tested the built-in consent placeholder. | Outside map service | Receiving domains not verified | Not assessed | Not tested |
|
What this table does and does not prove
This table describes the named map setups. It does not show what loads on your site. Google Maps and OpenStreetMap tiles can both send visitor requests off your server. We have not tested consent timing, and we have not assessed how long map-service logs are kept. The site scan linked below checks for third-party requests; it does not access your WordPress database.
Documentation snapshot: Sep 29, 2026. Sources are linked in each reviewed row.
Scan your site for third-party requests/wp-map-plugin-privacy