Dolomites Planner

Legal

Privacy policy

Last updated: 6 July 2026

This page explains what data Dolomites Planner collects when you visit, plan a route, or create an account, and how we use it. It is maintained by the site owner and reflects current practice, not an independent audit.

1. Who runs this site

Dolomites Planner is an independent project. For privacy questions or data requests, write via our contact page.

2. Data we collect

If you only browse

  • Standard request logs such as IP address, user-agent, requested URL, and timestamp, kept for about 30 days for abuse prevention.
  • With your consent (cookie banner), Google Analytics 4 usage statistics such as pages viewed, referrer, device type and country. Without consent, none of this runs.
  • Anonymous, aggregate counts of a few actions: which huts get clicked through to, and how often a shared route link is opened. These store only a count, a date, and which hut or link it was, with no identifier of any kind, so they cannot be traced back to you and do not depend on the cookie banner.

If you create an account

  • Email address and a hashed password, or your OAuth provider identifier.
  • Account creation date, last sign-in, and your saved routes or preferences.
  • Product activity linked to your account: which hut and guide pages you open, and planning actions such as routes solved, saved or booking statuses you set. We use this only to understand what signed-in users need and to improve the planner; never for advertising, never shared.

If something crashes

  • An error log with the error message, stack trace, URL, and your user id if signed in, used only to fix bugs.

3. What we do NOT collect

  • No tracking before you agree: analytics and marketing tags stay completely off until you accept them in the cookie banner, and you can withdraw via the "Cookies" link in the footer.
  • No payment information, because we do not currently sell anything.
  • No precise location tracking. The planner only uses coordinates you explicitly enter or click.

4. Third-party processors

  • Supabase: hosts account, auth, and saved routes.
  • Cloudflare: hosts the site and routes traffic; like any host it sees request metadata such as your IP.
  • OpenStreetMap, OpenTopoMap, Waymarked Trails: map tiles; these servers see your IP when the map loads.
  • BRouter: computes trail paths between waypoints; only coordinates are sent.
  • Brevo: sends transactional email such as password resets (EU-based).
  • Google Tag Manager / Google Analytics 4: with consent, loads analytics/marketing tags; Google may process this data in the US under the EU-US Data Privacy Framework.
  • Microsoft Clarity: Microsoft Clarity: with your consent (cookie banner), anonymized session replays and heatmaps that show us where the interface confuses people. Typed input is masked by Clarity by default.
  • Meta Pixel: only with consent and only while our ad campaigns run; measures whether our ads led you here.
  • Google: only if you sign in with Google; then Google's own privacy policy also applies.

5. Cookies and local storage

Essential local storage keeps you signed in, remembers your cookie choice and your unsaved route draft; this is required for the site to function. With your consent we additionally load Google Tag Manager with Google Analytics 4 (usage statistics) and, when our ad campaigns run, the Meta Pixel (ad measurement). You can change your choice at any time via the "Cookies" link in the footer.

6. How long we keep data

  • Account data: until you delete your account.
  • Request logs: about 30 days.
  • Error logs: 90 days.
  • Aggregated analytics: indefinitely, without personal identifiers.

7. Your rights (GDPR)

If you are in the EU, EEA, UK, or Switzerland, you can request access to, correction of, or deletion of your personal data; object to processing; and lodge a complaint with your local data authority. Email us via our contact page.

8. Children

The service is not directed at children under 16 and we do not knowingly collect their data.

9. Changes

We may update this policy. Material changes will be flagged on the homepage for at least 14 days. The date above always shows the current version.