MERIDIANio-io.live
connecting…
Privacy & Legal

Your data, our sources, the rules

Meridian is built local-first and tracker-free. This page states exactly what is stored, what leaves your device, where every dataset comes from, and what Meridian is — and is not.

Safety disclaimer — read this first

Meridian is an awareness and education tool, not an official warning service. Data can be delayed, incomplete or wrong. For decisions about your safety, always follow your national meteorological agency and local civil-protection authorities.

Risk forecasts shown here are derived, probabilistic indices built on public model outputs — labelled with their model version — never official warnings.

Privacy — what stays on your device

Meridian has no accounts yet, sets no cookies, and embeds no third-party trackers or ad scripts. Everything personal lives in your browser's local storage:

  • meridian.saved.v1 Places you follow (name + coordinates)
  • meridian.prefs.v1 Interface preferences (motion, data, glyphs…)
  • meridian.detailq.v1 Map-detail upgrade jobs for saved places
  • meridian.analytics.v1 Anonymous usage events pending upload
  • meridian.feedback.v1 Feedback you typed on the Learn page

You can erase all of it anytime: Account → Clear my data on this device.

Analytics — what leaves your device

To understand which features matter, Meridian records a small set of anonymous product events (e.g. app_open, place_follow). Before anything is recorded, coordinates are rounded to roughly 10 km — never precise addresses — and no name, email, IP log or device fingerprint is attached.

Events queue locally and upload in batches to Meridian's own backend only when it is configured — never to a third party. Weather lookups on Explore query Open-Meteo directly with the searched coordinates, governed by Open-Meteo's terms.

Early-access waitlist

If you join the early-access wishlist, the email and location you type are stored on Meridian's own server for one purpose: to plan the rollout and notify you when family plans open. It is never sold, shared, or used for anything else, and you can ask us to delete it at any time by writing to the contact on the Support page.

Your GDPR rights

Because on-device data is local-first, you hold it: access it via your browser's storage inspector, export it with the button on the Account page, and erase it with the clear-data button. For waitlist data held on our server, email us to access or erase it. Once full accounts exist (Phase 2), export and deletion will be built in, and this policy will name the data controller and contact address.

Data licences & attribution
ProviderUsed forLicence
USGSEarthquake feedPublic domain (US Government)
NASA EONETNatural-event feedOpen — NASA data policy
Open-MeteoWeather & geocodingCC BY 4.0 (attribution required)
NOAA CPCENSO / ONI indexPublic (US Government)
Natural Earth / world-atlasLand shapesPublic domain
NASA / three-globeGlobe imageryOpen — NASA imagery guidelines

Full registry: DATA_SOURCES.md in the repository. Attribution stays visible in the app footer and on the Data page — it is a licence requirement, not decoration.

Code licence & intellectual property

Meridian's source code, algorithms, risk-index models and prediction logic are proprietary — all rights reserved. They are not open source and may not be used, copied, modified or reverse-engineered without written permission.

Using Meridian as a service is free, and safety information always stays free — that never requires access to the code. The datasets shown remain under their providers' own licences (table above). Licensing enquiries: via the Support page.