1. This website (www.mapalizer.com)

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:

  • Sets no cookies
  • Does not collect or store any personal data or PII
  • Does not use fingerprinting or cross-site tracking
  • Is fully GDPR, CCPA, and PECR compliant
  • Processes data as aggregate page views and referrer counts only

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.

2. Interactive tool pages (Configurator, API Examples, Toolbar Themes & Score Widget)

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:

  • Your IP address
  • Browser and device information
  • Map interaction events (pan, zoom, click)
  • User-typed address queries submitted to Places Autocomplete (Score Widget page only)

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.

3. Mapalizer® Toolbar and Widget (when you integrate them on your website)

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:

  • No personal user data is collected. The Toolbar and Widget do not read, store, or transmit any personally identifiable information about your website's visitors.
  • CDN and data requests. The SDK fetches its JavaScript, CSS, locale files, and category metadata from 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.
  • API call counting. The number of Toolbar or Widget loads is counted in aggregate per registered domain. This aggregate count is used solely for billing and license compliance monitoring. Individual visitor data is never extracted or stored.
  • No cookies. The Toolbar and Widget set no cookies on your visitors' browsers.
  • No third-party sharing. Mapalizer does not sell, share, or transfer any data to third parties.

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.

4. Customer Portal (portal.mapalizer.com)

If you create an account on the Mapalizer Customer Portal at portal.mapalizer.com, the following data processing applies:

  • Account data. When you sign up, we store your email address, a Cognito-issued user identifier, and (if you sign in with Google) the unique provider sub-identifier returned by Google. We use this data to authenticate you, to provision your customer record and API tokens, and to send transactional emails (verification codes, password resets, billing-related notifications).
  • Authentication. The portal authenticates you using Amazon Cognito. Cognito stores the standard authentication tokens (ID token, access token, refresh token) in the browser's localStorage. These are not third-party cookies and are not used for cross-site tracking.
  • Google sign-in (optional). If you choose “Continue with Google”, you are briefly redirected to Google so they can verify your identity. Google's processing during sign-in is governed by Google's Privacy Policy. We receive only your verified email address and a stable Google sub-identifier.
  • Bot protection. The native sign-up form uses Cloudflare Turnstile, an invisible CAPTCHA, to block automated abuse. Turnstile may process technical request data (IP address, browser characteristics) as an independent data processor; see Cloudflare's Privacy Policy.
  • No tracking cookies. The portal sets no advertising or analytics cookies. The only browser storage is authentication state required for Cognito.
  • Account deletion. You can permanently delete your account and all associated data at any time from https://portal.mapalizer.com/accountDanger zoneDelete my account. The deletion is immediate: your sites and API tokens are removed, your profile is purged, and your Cognito identity is deleted. Usage records are anonymized (the link to your identity is removed) but the anonymized counters are retained for the billing-audit period required by EU tax law. If you cannot sign in to use the self-serve flow, email info@mapalizer.com from the address registered to your account and we will process the deletion within 5 business days.

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.

5. Contact

For any privacy-related questions or requests, please contact:

Emre Dagli
Manteuffelstraße 46, 12103 Berlin, Germany
info@mapalizer.com