Plain English. Last updated: June 2026.
This section covers www.mapalizer.com. Separate sections below cover the interactive tool pages, the Mapalizer® Toolbar and Widget, and the Customer Portal (portal.mapalizer.com).
✓ No cookies ✓ No Mapalizer-side personal data storage ✓ No cross-site tracking
This website sets no cookies. Mapalizer® itself does not collect or store personally identifiable information about visitors to www.mapalizer.com.
We use Plausible Analytics to understand how visitors use the site. Plausible is a privacy-friendly analytics tool that:
Data is processed by Plausible Analytics (Plausible's Privacy Policy). Mapalizer only sees aggregate statistics. No individual visitor data is available to us.
We also use Google Fonts to load the Open Sans typeface. This request goes to Google's servers and may involve processing of technical request data such as IP address, subject to Google's Privacy Policy.
Because Mapalizer sets no cookies and does not use cross-site tracking, this website does not require a cookie consent banner specifically for Mapalizer. You should still assess any third-party services used on the site under your own legal obligations.
The Configurator, API Examples, Toolbar Themes, and Score Widget pages load the Google Maps JavaScript API. When you open these pages, Google's servers are contacted to load map tiles and the Maps SDK.
The Score Widget page additionally loads the Google Maps Places API to power the address autocomplete field in the live demo. When you type an address into the search box, your input is sent to Google's Places Autocomplete service.
Google Maps JS API and Places API may collect and process:
Google acts as an independent data controller for this data. Mapalizer does not receive, store, or process this information. Please refer to Google's Privacy Policy and Google Maps Platform Terms for full details.
These tool pages do not use cookies, localStorage, or sessionStorage for Mapalizer tokens or UI state.
The Mapalizer® Toolbar (map overlay) and Widget (standalone score badge embed) are distributed as the same JavaScript SDK. Both share an identical Mapalizer-side privacy profile when integrated on a customer website.
Note: The Score Widget demo page on www.mapalizer.com loads Google Maps and Places for its live example UI — that is a characteristic of the demo page, not of the embeddable Widget component itself. When you embed the Widget on your own site, no Google Maps or Places dependency is introduced by Mapalizer; the Widget renders score badges independently.
If you are a developer integrating the Mapalizer Toolbar or Widget on your own website, here is what the SDK does with data:
cdn.mapalizer.com, and score tiles from data.mapalizer.com. All requests are made with credentials: 'omit', which means no cookies or authentication headers are sent by the browser as part of these fetch requests. As with any web request, technical request data such as IP address may still be processed at the network level. The CDN pipeline records only aggregate request counts per registered domain. Individual visitor IP addresses or session data are not stored in the final analytics dataset.Integrating the Mapalizer Toolbar or Widget does not require you to add a cookie consent banner specifically for the SDK. However, you should review your own website's data practices independently.
If you create an account on the Mapalizer Customer Portal at portal.mapalizer.com, the following data processing applies:
localStorage. These are not third-party cookies and are not used for cross-site tracking.Account data is stored in Amazon DynamoDB in the EU (eu-central-1) region, with server-side encryption at rest. Transactional emails are sent via Amazon SES from the mapalizer.com domain.
For any privacy-related questions or requests, please contact:
Emre Dagli