GDPR & DSGVO Compliant Maps | GeoUNIT Maps
What is GeoUNIT Maps? Say hello to the powerful and user-friendly Plugin for WordPress that allows you to display maps on your website while ensuring GDPR compliance and protecting your European users’ data.
The best? With GeoUNIT Maps, there’s no need for opt-ins or cookie consent options. The Plugin is designed to be fully GDPR-compliant out of the box, so you can focus on creating amazing maps and delivering great user experiences.
Make your map web engaging, accessible and safe for users with GeoUNIT!
In addition, there are more options than using it in WordPress: now you can also use it with shortcodes or an Elementor widget to display maps on your website.
Amazed? This is not all. With this plugin Maps your users will be protected, due to the tiles provided by the GoeUNIT Tileserver. That means that unlike other mapping services that may transfer your users’ data to servers in other countries (with insufficient privacy laws), such as Google Maps, GeoUNIT offers superior GDPR compliance and privacy protection for your European users, keeping your users’ data safe and secure by using only servers located in Germany. 🔒
Now it’s time to create your amazing map with the more secure plugin. Try GeoUNIT Maps today and see why it’s the best choice for GDPR-compliant maps on your WordPress website! 🧑💻
Privacy Information & External Services
GeoUNIT Maps uses tiles provided by the GeoUNIT Tileserver, a third-party service from Unit08 GmbH in Germany that offers excellent privacy protection.
The Plugin is designed to be fully GDPR-compliant out of the box, and the only external service it uses is the GeoUNIT Tileserver.
The usage of this plugin and Tileservers is completely free. We do not store any information about your page visitors.
This means that your users’ data is safe and secure. More information about Privacy Policy.
Credits
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| f*r*e*e*1*0*p*t*e*.fr (WP 7.0) | F | 2026-06-01 19:42:30 | |
| h*v*k*e*e*b*o*n.com (WP 6.9.4) | F | 2026-05-31 04:46:03 | |
| c*m*d*n.com | A | 2026-05-29 17:51:46 | |
| s*z*e*k*e*l*.de | F | 2026-05-29 10:16:36 | |
| v*l*a*-*l*s*e*s.com | B | 2026-05-28 19:20:27 | |
| e*t*f.p*t*i*i*.ag | F | 2026-05-28 12:20:13 | |
| b*a*t*e*-*u*r*.at (WP 6.7.5) | F | 2026-05-28 04:40:29 | |
| d*s*k*n*o*.biz (WP 6.7.2) | F | 2026-05-27 17:33:44 | |
| f*r*e*e*1*0*p*t*e*.com (WP 7.0) | F | 2026-05-25 20:08:36 | |
| f*r*e*w*h*u*g*f*r*b*i*k.com (WP 7.0) | F | 2026-05-25 19:24:46 | |
| z*b*-*v*n*e*i*c*.de (WP 6.9.4) | F | 2026-05-25 16:00:07 | |
| h*v*k*e*e*b*o*n.de (WP 6.9.4) | F | 2026-05-23 20:26:48 | |
| d*z*6*.de (WP 6.9.4) | F | 2026-05-20 07:34:11 | |
| a*m*r*e*-*p*i*.de (WP 6.9.4) | F | 2026-05-17 22:50:45 | |
| j*l*a*n*c*r*e*t*l.com | F | 2026-05-16 16:39:16 | |
| z*h*a*z*-*u*c*e*.de (WP 6.9.4) | A | 2026-05-15 14:50:43 | |
| z*h*a*z*-*u*c*e*.com (WP 6.9.4) | A | 2026-05-15 13:14:40 | |
| e*u*t*-*o*s*t*u*k*.com (WP 6.7.1) | F | 2026-05-15 11:27:00 | |
| r*d*o*o*i*-*w.de (WP 6.9.4) | C | 2026-05-14 08:44:06 | |
| g*a*d*-*v*c*t*.com (WP 6.9) | F | 2026-05-11 17:25:46 | |
| t*v*s*o*k*n*p*r*m*n.n*s.uk | A | 2026-05-10 23:03:28 | |
| s*h*e*e*-*e*m*i*r.com (WP 6.6.2) | F | 2026-05-07 04:34:43 | |
| k*o*h*.de (WP 6.9.4) | F | 2026-05-06 17:24:07 | |
| g*s*n*h*i*s*a*e*b*d*o*e*.com | F | 2026-05-04 10:38:30 | |
| i*s*i*e*t*u*s.fr | F | 2026-05-04 10:05:55 | |
| b*e*g*r*e*t*u*-*i*p*s.de (WP 6.9.4) | F | 2026-05-03 16:36:16 |