Privacy-first map infrastructure

Consent-free maps for privacy-first websites.

Serve interactive OpenStreetMap-based maps without third-party tracking, cookies, or external map embeds, with transparent token-based pricing.

Built for companies, agencies, and SaaS platforms that want beautiful map integrations without consent popups, opaque map billing, or unnecessary third-party requests.

  • No tracking cookies
  • No visitor profiling
  • No Google Maps iframe
  • Token-based pricing
  • MapLibre compatible
  • OpenStreetMap based
Live embed exampleA map that can load without consent friction

OpenStreetMap-based tiles rendered with MapLibre and visible attribution.

Traditional map embedVisitor data leaves your page

Visitor -> third-party map provider -> cookies, tracking, consent concerns.

PrivacyMaps.euA controlled tile endpoint

Visitor -> your website -> privacy-first tile API -> no tracking cookies or third-party iframe.

The problem

Most embedded maps create privacy and pricing problems.

Standard map embeds can introduce third-party requests, tracking scripts, cookies, external iframes, and unclear pricing. For privacy-sensitive websites, that often means consent banners, two-click placeholders, legal review, or removing the map entirely.

Consent friction

Cookie banners and map placeholders interrupt the user experience.

Third-party requests

External map embeds can send visitor data to third-party providers.

Opaque pricing

Traditional map platforms often price by map loads, sessions, or complex API usage.

Developer lock-in

Proprietary SDKs make it harder to control styling, data flow, and long-term costs.

The solution

Map infrastructure designed for privacy-first websites.

PrivacyMaps.eu serves interactive vector map tiles through a simple token-based API. Your website can display modern maps without loading third-party map iframes, setting tracking cookies, or sending visitors directly to large advertising-backed map providers.

No tracking by design We serve map tiles. We do not inject analytics, set marketing cookies, or build visitor profiles.
Token-based access Create, rotate, revoke, and separate tokens by customer, website, project, or environment.
Transparent usage Usage is based on tile requests. Customers can see their usage and plan around predictable quotas.
OpenStreetMap based Built on open map data and standard vector tile workflows.
MapLibre compatible Use modern open-source map rendering without proprietary frontend lock-in.
Flexible integration Use a WordPress plugin, npm package, or custom implementation.

Embed options

Embed privacy-first maps your way.

Choose the integration style that fits your project, from no-code WordPress setup to fully custom MapLibre implementations.

For agencies, local businesses, public-sector websites, and non-technical teams.

Add privacy-first maps to WordPress in minutes.

Install the Privacy Map plugin, add your customer ID and API key in settings, then place maps with the Gutenberg block, Elementor widget, or [privacy_map] shortcode.

Best for
  • Company websites
  • Store locators
  • Agency client sites
  • Municipality websites
  • Simple location pages
Gutenberg blockElementor widgetShortcodeMarkersBoundsTheme control
Request WordPress access
Block, widget, and shortcode
// Gutenberg block
Block: privacy-map/map

// Elementor widget
Widget: privacy_map

// Classic editor shortcode
[privacy_map
  theme="standard"
  center_lat="52.5200"
  center_lng="13.4050"
  zoom="13"
  height="420px"
  show_zoom_controls="true"
  show_compass="true"
  markers='[{"lat":52.52,"lng":13.405,"title":"Berlin Office"}]'
]

Transparent pricing

Transparent token-based pricing.

Pay for map tile usage, not confusing map loads or hidden platform fees. Each customer can have one or more API tokens, and all token usage counts toward the customer quota.

Starter

Small websites

100,000 tiles

For small business websites and simple location pages.

  • 1 project
  • 1 token
  • Basic styles
  • Usage visibility
Start small
Business

Higher traffic

2,000,000+ tiles

For higher-traffic websites and privacy-sensitive organizations.

  • Custom domains
  • Higher quotas
  • Priority support
  • Custom styling
  • Agency workflows
Talk to us

No per-seat pricing. No dynamic map load confusion. No surprise API bills. No third-party map platform lock-in.

How it works

Simple infrastructure. Clear data flow.

Instead of embedding a third-party map iframe, your site loads vector tiles from a controlled tile endpoint. The map renders in your frontend using open standards and your selected style.

  1. 1Your website
  2. 2Privacy Maps token
  3. 3Privacy Maps EU tile API
  4. 4OpenStreetMap-based vector tiles
  5. 5MapLibre renders the map

Use cases

Built for teams that care about privacy and control.

Agencies

Offer privacy-first map integrations to German and EU clients without building map infrastructure from scratch.

Public-sector websites

Display offices, districts, public facilities, and contact locations without relying on external map embeds.

Healthcare and insurance

Show providers, clinics, service areas, and offices while minimizing unnecessary third-party requests.

SaaS platforms

Add maps to dashboards, directories, portals, booking flows, and location-based features with predictable usage.

Local business websites

Embed attractive location maps without bloated scripts, cookie banners, or Google Maps iframes.

Compliance-heavy companies

Reduce third-party exposure and simplify the technical explanation for legal teams.

Developers

Developer-friendly by default.

Use standard map tooling and simple API tokens instead of proprietary frontend lock-in.

  • Vector tiles
  • MapLibre compatible
  • Token-based authentication
  • Customer-level quotas
  • Usage endpoint
  • Token rotation
  • CORS-ready
  • Custom style support
  • WordPress, npm package, or direct API integration
API concepts
GET /v1/{customerId}/{z}/{x}/{y}.mvt?key={token}

GET /usage/{customerId}?key={token}

POST /admin/tokens/revoke

Trust and transparency

Built on open data and open standards.

Privacy Maps EU is based on OpenStreetMap data and standard vector tile workflows. You are not locked into a proprietary frontend SDK, opaque map-load pricing, or third-party tracking infrastructure.

  • OpenStreetMap-based
  • MapLibre compatible
  • Transparent token usage
  • No tracking cookies
  • No visitor profiling
  • No external map iframe
  • Simple API architecture

FAQ

Questions privacy teams and developers usually ask.

PrivacyMaps.eu does not set tracking cookies, inject analytics, or load a third-party map iframe. The service is designed to avoid the typical map-consent popup problem. Your full website setup and legal basis should still be reviewed for your specific use case.

Start testing

Add maps without adding another consent problem.

Start with a test token and see how privacy-first maps can work on your website, app, or client project.