Privacy

Privacy policy.

Last updated: 21 April 2026

What this page covers

This policy describes how elementeditor.dev (the website) handles visitor data and how the Element Editor library handles data at runtime. It does not cover what you do with features you collect — that's your application's responsibility.

The site (elementeditor.dev)

  • No cookies. The site sets no cookies. We use Plausible for anonymous aggregate analytics; it is cookieless and GDPR-compliant by design.
  • No tracking across sites. No Facebook pixel, no Google Analytics, no third-party advertising trackers.
  • What we see. Plausible records the page URL, referrer, browser type, device type, and country (derived from IP — the IP itself is discarded). This is aggregated with all other visitors; we cannot identify you personally.
  • Contact forms. There are none. If you email us, we store and reply to that email like any other email. We don't add you to newsletters without consent.

The library (Element SDK)

  • No telemetry. Element does not phone home. It has no analytics pixel, no usage reporting, no license- check ping. The library has no idea it's being used.
  • GeoJSON stays with you. The features your users draw are delivered via the onChange callback to your application. Element does not send them anywhere.
  • External calls — routing only. The route drawing tool calls a routing API you configure (OpenRouteService or OSRM). If you don't use the route tool, no external requests are made by Element.
  • Tile providers. Your map tile provider (OpenStreetMap, Mapbox, MapTiler, etc.) serves its own privacy policy. Element does not select a default that makes requests on your behalf — your application decides.

Your rights

If you're in the EU, UK, or similar jurisdictions, data-subject rights under GDPR / equivalent apply. Because we collect so little, most rights don't have anything to act on. To exercise any of them, email [email protected].

Changes

If we change this policy in a way that affects what we collect, we'll post a note on the changelog and update the "last updated" date above.