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 · 1 September 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: AdSense is currently disabled on the interactive map root in every state. The root keeps the publisher verification marker and /ads.txt, but does not load Google's Auto Ads script. If a separately reviewed page enables AdSense later, Google and its advertising partners may use cookies, local storage, web beacons or pixels, IP address, browser and device information, advertising identifiers where available, and ad-interaction signals to deliver, measure, limit fraud, or personalize advertising according to the serving configuration and Google's policies. See Google's partner-site technologies information and Google's Privacy Policy.
  • Cloudflare: the Worker, CDN, and edge security layer may process the IP address, request headers, user agent, network/security metadata, and request timing needed to deliver, cache, and protect the site. Cloudflare Worker Observability may retain sampled server-side invocation telemetry under the deployment settings. This repository does not inject a Cloudflare Web Analytics or Insights browser beacon. See Cloudflare's Privacy Policy.
  • 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, or hosting services may set or read cookies or similar identifiers. Their behavior can change with service configuration, browser settings, and jurisdiction.

If a separately reviewed page enables AdSense, Google may process the IP address and ordinary browser or device signals sent with an ad request, including an advertising identifier or approximate location derived from network information where those signals are available. Web beacons, pixels, local storage, and related technologies can help measure reach, frequency, fraud, and conversions. Mapews does not control Google's partner processing; visitors can review Google's Ads Settings and partner technologies information.

Ads are currently disabled on the interactive map, including shared event URLs. A separate page lifecycle and account review are required before any future page requests 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, does not claim that this notice alone satisfies a jurisdiction's legal requirements, and does not represent that a consent message is currently installed unless the operator has completed and verified that external dashboard setup.

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.

The public channel currently uses Google Forms. When you submit a correction or privacy request, the information you enter is sent to Google and may be stored or otherwise processed under Google's service configuration. Google may also process ordinary connection, browser, or device information associated with accessing or submitting the form. See Google's Privacy Policy for Google's current information. Do not include unnecessary personal or sensitive information.

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.