Put a map on your site. Skip the cookie banner.
A Google Maps embed sends visitor data to the US before anyone has consented to anything, so the map hides behind a banner. Rijwind maps load from EU infrastructure with no cookies and no trackers. The map just shows.
No cookies, no trackers
Map delivery sets no cookies and loads no third-party scripts. There is nothing for a consent manager to block: visitors see the map on first paint, not after a click.
Nothing leaves the EU
Tiles, geocoding and routing are processed on owned infrastructure in the Netherlands. No US subprocessors in the request path means no third-country transfer to paper over.
Not an ad company
Our business model is the subscription, not the data. Request bodies aren't logged beyond billing counters; there's no profile being built on your visitors.
Two ways to embed
An interactive map when visitors should explore, or a static image when the page just needs to show a place (contact pages, order confirmations, emails, PDFs). Both are banner-free.
Static: zero JavaScript
<img
src="https://api.rijwind.com/styles/v1/light/static/4.8896,52.3740,14/600x400?marker=4.8896,52.3740&key=YOUR_KEY"
alt="Map showing our office"
width="600" height="400"
/>Interactive: MapLibre GL
import maplibregl from "maplibre-gl";
const map = new maplibregl.Map({
container: "map",
style: "https://rijwind.com/styles/light.json",
center: [4.8896, 52.374],
zoom: 13,
});
// tile wiring: docs.rijwind.com -> BasemapBuilt for the sites that can't just click accept
Agencies
Stop re-litigating the cookie banner on every client site with a map. One provider, a DPA you can hand to the client, and a map that loads for 100% of visitors.
Public sector & education
EU processing and a signed DPA fit procurement requirements that US map providers struggle with, and the map on your contact page finally works without a consent wall.
Healthcare & finance
Sectors where data flows are audited can't casually ship visitor data to ad companies. A map that's just a map keeps the audit short.
- Interactive and static maps from one API
- Worldwide geocoding and routing included
- Signed DPA available on paid plans
- Free tier to evaluate, no card required
FAQ
- Why does a Google Maps embed need a consent banner?
- Loading the embed sends the visitor's IP address and browser data to Google in the US before they've agreed to anything. EU data-protection authorities have repeatedly flagged exactly this pattern, which is why consent managers block the map until the visitor clicks accept.
- Why doesn't a Rijwind map need one?
- Map delivery sets no cookies, runs no trackers, and is processed on infrastructure in the Netherlands; there's no transfer to a third country to consent to. The visitor's IP is used transiently to deliver the response, like any web request, and request bodies aren't logged beyond billing counters.
- Does this also cover search and routing?
- Yes. Geocoding, autocomplete and routing requests follow the same rule: processed in the EU, no cookies, no advertising identifiers, nothing retained beyond what billing needs.
- Do you sign a DPA?
- Yes, a signed data processing agreement is available on paid plans. Useful for agencies with public-sector or healthcare clients where a DPA is mandatory.
This page is general information about how our service works, not legal advice; your privacy policy and processing register remain your own. Compare providers: Rijwind vs Google Maps · Rijwind vs Mapbox.
Ship the map without the banner.
Free tier, no card. Drop a static map on your contact page in five minutes.