Skip to content
Route Planner by HuntLog
Menu
How it works Route preferences Sports GPX Trips FAQ Download Explore Events Contact Log in
Language
EN IT
Theme
Open the planner
/// Privacy

What we know about you, and what we don't.

All of it, in the order that matters: what the planner stores, what it never asks for, who else sees anything, and how to make the lot disappear. A policy nobody can read protects nobody, so this one is written to be read.

Last updated 2026-08-24.

/// Who is asking

One address, and somebody behind it.

Route Planner is part of HuntLog. The controller of everything described here answers at the address below — the same one that takes a deletion request, a question about this page, or a complaint about how it was handled.

  • Write to info@huntlog.xyz
/// What is stored

Five things, and nothing besides.

Everything kept here is something you typed, drew or uploaded — plus what any web server unavoidably writes down while answering a request.

  • Your account Email address, and the name and picture you choose. Sign in with Google and we receive those three from Google — no contacts, no calendar, no files.
  • Routes and trips The line on the map, its elevation profile, the sport, the name you gave it and when you saved it.
  • Photos and videos The ones you attach to a story. Photos are re-encoded on upload, so the camera's own metadata — the GPS tag included — does not survive the trip to our disk.
  • Your position Only while the map is open, and only if you allow it. It draws where you are, and it is written down only inside a track you asked to record.
  • Server logs IP address, browser, page and time, written by the web server for security and rotated away after a few weeks.

There is no analytics on this site, no advertising, no third-party tracker and no cookie banner — because there is nothing to consent to. The only cookies are the one that keeps you signed in and the one that remembers your language.

/// Location

In the foreground, and only when you say so.

The planner is a map, so it can ask where you are. It asks through the browser's permission prompt — in the Android app, through Android's own — and it uses the answer on the spot.

What that means, precisely

  • Never in the background: the app holds no background-location permission at all, so with the app closed nothing is read and nothing is sent.
  • A position used live is not saved — it moves the dot on the map, and that is the end of it.
  • A track you record is a route like any other: it is yours, and it stays private until you publish it.

None of it is sold and none of it profiles you. There is no advertising on this product, so your position has no second use to be put to.

/// On what basis

Three, and each one says which.

Your account and everything you save are processed to provide the service you asked for (Art. 6(1)(b) GDPR — a contract). Your position and anything you publish rest on consent, given per permission and per item, and withdrawable at any time (Art. 6(1)(a)). Server logs are kept to keep the thing running and to stop abuse, which is a legitimate interest (Art. 6(1)(f)).

The servers that hold all of it are in the European Union.

/// What becomes public

Only what you publish, one item at a time.

A route, a trip or a story is private the moment it is saved. Publishing is a decision you make per item, and undo per item.

When you do publish

  • The map, the numbers and the photos become readable by anyone holding the link, and appear among the Stories — on the Explore map too when the route is a recorded .fit.
  • Your public name and picture go on them. Your email never does.
  • The first and last 500 metres are trimmed by default, so the line does not start at your front door — you can turn that off for a route that starts somewhere else.

Unpublishing takes it out of the feed and off the link straight away.

/// Who else sees something

The four that cannot be avoided, named.

A map is drawn from tiles somebody else serves, and a place name is answered by somebody else's index. Your browser talks to them directly, so they see the request and the address it came from.

  • Map tiles OpenStreetMap, OpenTopoMap and Esri draw the background of every map here. They see which tiles you look at.
  • Place names Photon (photon.komoot.io) turns coordinates into place names and back. It sees the point being looked up.
  • Email Account mail — confirming an address, resetting a password — leaves through our mail provider.
  • Google Only if you pick it: signing in with Google, or installing the Android app from Google Play.

Routing is not on that list. The engine that turns your points into a road runs on our own server, so the route you are drawing never leaves it.

/// How long

As long as it is yours.

Your account and what is in it stay until you say otherwise. Everything else runs on its own clock.

  • Account, routes, photos Until you delete them, or until you ask for the account to go.
  • Server logs A few weeks, then they rotate away on their own.
  • Deleted items Out of the database as you delete them; the files that belonged to them follow within days.
/// Deleting everything

One email, and it is gone.

No form to hunt for, no retention trick, nothing to cancel first. Write from the address the account uses and say so.

  1. Write to info@huntlog.xyz

    From the email address the account is registered to, asking for it to be deleted. Writing from that address is what proves the account is yours.

  2. We confirm, then delete

    The account, the routes, the trips, the stories and every file uploaded with them. Within 30 days, and in practice the same week.

  3. Nothing is held back

    Anything you had published goes with the rest. Server logs age out on their own schedule and name a request, not a person.

/// Your rights

The GDPR ones, in plain words.

At any time, free of charge, and by writing to the address above, you can ask to:

  • See what is held about you, and be given a copy.
  • Correct anything that is wrong.
  • Have it deleted — that is the section above.
  • Take it elsewhere: every route exports as GPX from the site itself, whenever you like.
  • Object to a use of it, or ask that it be restricted.

If an answer never comes, or the one that comes is not good enough, the Italian supervisory authority takes complaints — Garante per la protezione dei dati personali, garanteprivacy.it.

/// Age

Not built for children.

An account asks that you be at least 14 — the age at which Italian law lets you consent on your own to a service like this one. We do not knowingly hold data about anyone younger, and if you believe we do, the address above is how it gets fixed.

/// Changes

This page carries a date.

When what we do changes, this page changes with it and the date moves. It describes the product as it is today, not as it might one day be — and if it ever says something the software does not do, the software is the bug.