GDPR

Holds the map back until the visitor has consented to it.

Why this matters
Loading a map sends the visitor’s IP address to a third party — Google, Mapbox, Stadia or OpenStreetMap — before they’ve agreed to anything. GDPR treats that as personal data needing consent, so an EU-facing site usually has to ask first.

GDPR consent handled by

  • None — the map loads immediately. Correct only if you have no EU visitors, or another mechanism already blocks the map.
  • WP Store Locator — the plugin shows its own placeholder with the description below, and loads the map when the visitor accepts.
  • Borlabs Cookie — hands the decision to Borlabs. Only offered while that plugin is active.
  • Complianz — hands the decision to Complianz, which loads the map once the visitor accepts the marketing category. Only offered while that plugin is active.

A handler you saved before deactivating its plugin stays in the list, so saving an unrelated setting can never quietly drop your consent check.

Two things to check if the map loads when it should not. Complianz only blocks anything once its own setup wizard has been completed — an unfinished wizard blocks nothing. And with Borlabs, the plugin needs to be configured to recognise the map; see its own documentation.

Description
The text shown in the placeholder where the map would be, when WP Store Locator is the handler.

Say what the visitor gets by accepting and who receives their data — “Load the map to find your nearest branch. This will contact Google Maps.” A blank grey box with a button converts badly and explains nothing.

Related