MAPEWS

Privacy & cookies

What the map needs to work.

This notice explains the information a Mapews browser session can send, the third-party services used by the current implementation, and the choices an operator must complete before serving ads.

Last updated · 30 August 2026This is product information, not legal advice

The browser sends only what the map asks for.

Map and filtersViewport coordinates, category filters, and selected time bounds are sent to the read API to return events in the visible area.
SearchSearch text is sent to the read API when autocomplete or event search is used. Do not enter sensitive personal information.
Technical requestsYour browser, network provider, and hosting services may process ordinary request metadata needed to deliver the page, tiles, fonts, and API responses.
Stored event dataMapews stores event and source metadata server-side for the product, including titles, summaries, times, locations, coordinates, and source links. It does not provide user accounts in the current client.

The current client does not ask for a name, account, or precise device location. Mapews does not use browser geolocation to center the map. Server, hosting, database, and operational logs may still exist under the deployment provider's configuration and retention rules.

Services outside Mapews.

  • MapLibre and OpenFreeMap: the map renderer requests the configured style, tiles, and attribution resources from the map service. See Sources & attribution.
  • Google Fonts: the client styles reference font files from Google Fonts. A browser may request those resources when the map or information pages load.
  • Google AdSense: the production client may load Google's Auto Ads script for a bottom anchor after the map has returned publishable event content. Google may use cookies, local storage, advertising identifiers, and similar technologies according to the serving configuration and Google's policies.
  • Supabase: the read API uses the operator's configured database service to return public event records. Server-only ingestion credentials are not placed in the browser.

Cookies and advertising.

The Mapews client does not intentionally set a first-party login or preference cookie in the current version. Third-party map, font, hosting, or advertising services may set or read cookies or similar identifiers. Their behavior can change with service configuration, browser settings, and jurisdiction.

Ads are not enabled on local development or test hosts. On a production deployment, the operator must confirm the publisher account, site review, Auto Ads settings, and consent configuration before expecting Google to serve advertising.

For visitors in the European Economic Area, the United Kingdom, or Switzerland, configure Google's certified consent solution through AdSense Privacy & messaging as required for the account and serving setup. Configure the applicable US state privacy messages as well. Mapews does not bundle a homemade consent manager and does not claim that this notice alone satisfies a jurisdiction's legal requirements.

Questions, corrections, and privacy requests.

For event corrections, source removals, or privacy questions, use the public channel on the contact page. Include only the information needed to identify the request, such as the event title or source URL. Operators review requests against the deployment's retention, source, and legal obligations.

Always-available privacy and cookie information is linked in the footer of the map and each information page. External providers may offer additional controls through their own sites and browser settings.