Local Storage, Third Parties and Map Attribution

Version: draft, 2026-11-09.

What TrailBuffer stores in your browser, which external servers it contacts, and where the map data comes from.

1. In short

TrailBuffer uses only the local storage it needs to work: this is what lets it run without internet and keeps your walk when the browser restarts. It sets no cookies of its own, and there is no analytics, measurement or advertising code. It therefore does not ask for consent.

[DATA – to be checked] Whether the hosting (Azure App Service, e.g. ARRAffinity) or Cloudflare sets a technical cookie under trailbuffer.com.

[LAWYER – Ü3] Whether this notice is sufficient without a consent dialog.

2. Local storage (localStorage)

The turakopilot_… keys are storage under the app's former name; the app takes over the old data. The app deletes the weather keys of earlier versions (trailbuffer_enrich_…, trailbuffer_mud_factor_enabled) at startup.

Session storage (sessionStorage): the marker of an installed launch (tb_pwa_launched) and the hidden iOS install tip (trailbuffer_ios_banner_dismissed); they are cleared when the browser session ends.

3. IndexedDB and cache

4. External servers

There are no other external requests: fonts (the map labels too) and code libraries come from TrailBuffer's own server, and the vector map shows the downloaded region from the device.

5. Map data and attribution

Offline the region shows the route, the trails, the water and the names; detailed topo (contour lines, relief) is online only, on the OpenTopoMap layer.

[LAWYER – Ü5] The mandatory wording and placement of the attribution (app, website, store), and the license text of the downloadable region package.

6. Deletion

The "Delete all my data" button in the app deletes the local storage above, IndexedDB and the cache from this device in one step; the app then restarts, which needs internet. You can also delete the site data in your browser settings.