Privacy policy

This policy describes the data the Planet Go website and app use today, and the services we plan to add. The controller and contact details are not filled in yet — placeholders are clearly marked.

1. Data controller

The controller of personal data under Regulation (EU) 2016/679 (GDPR) will be: PROVOZOVATEL_JMENO, address PROVOZOVATEL_ADRESA, email KONTAKT_EMAIL.

These are intentionally empty placeholders until the site operator provides real details. We will update this policy when they are added.

2. What we process today

The marketing site (homepage, blog and these information pages) does not ask you for an account or a form. The app at /app/ remembers state in your browser, not on our server.

Browser storage (localStorage)

The app stores data under the key wp-state-v2 in the localStorage of that origin (same domain, same browser). This typically includes a profile name, height and optional weight, step-length settings, units, map quality and camera, reported steps, route progress and saved custom routes. We do not send this data to our server. It stays on the device until you delete it, clear site data, or, in future, sign in to an account if one exists.

localStorage is not a cookie, but it is data stored on your device. Only a page from the same origin can read it.

Optional online account (Supabase)

You can play without an account. If you create one (email and password, an email link, or Google or Apple where enabled), we store with our provider Supabase (EU servers, Stockholm): your email and sign-in data, public name, status (max. 160 characters), chosen avatar and privacy settings, daily step totals split into manual / screenshot input (for fair leaderboards, capped at 100,000 steps a day), online coins, Party membership, invites, Party chat messages (deleted automatically after 24 hours), likes and cheers, treks saved online, a backup of your game progress and settings (daily steps, coins, medals, custom treks, trek progress, profile and game settings – so they are restored on any device you sign in on), published and bought treks, trek ratings, and points for watched ads or Patreon support. While you play a trek signed in, your position on the trek (name, avatar, distance and point on the route) is briefly shared with other players on the same trek; it is not stored and you can turn it off in your profile.

In your profile you choose what others can see (status, stats, Party, cheers, treks, name in leaderboards, avatar on treks). Everything is public by default. Your name and avatar are always public.

Download and deletion: in the app under Profile → My data you can download everything the server holds about you (JSON) and delete your account with all server data in one step. The legal basis is performance of a contract (providing the online features you asked for). We keep the data until you delete the account.

BYO-key AI trek generator: your API key stays in your browser only and the request goes directly to the provider you choose (OpenAI, Google, Anthropic or compatible). Nothing passes through our server.

3. Third-party services the app actually uses

When you open the map, search, route, satellite imagery, fonts, libraries or the screenshot reader, your browser fetches data from the services below. They may then see your IP address, browser type and an approximate area from map-tile requests (and so a rough sense of the place you are viewing):

  • OpenFreeMap and OpenMapTiles / OpenStreetMap contributors — map style and base map.
  • AWS Terrain Tiles (Terrarium terrain, originally Mapzen) — elevation data.
  • OSRM (typically the public FOSSGIS server) and a Valhalla fallback — foot routing.
  • Nominatim — place search. The app searches only after you confirm (Enter or 🔎), with a delay between requests and a capped cache.
  • Esri World Imagery and an EOX fallback — satellite imagery in the 2D view.
  • unpkg — delivery of MapLibre GL JS and three.js.
  • Supabase — app feature settings and the optional online account (see above).
  • jsDelivr — delivery of supabase-js and of Tesseract.js (and the tesseract.js-core) only when you choose to load steps from a screenshot. The OCR itself runs locally in the browser; the image is not uploaded to jsDelivr or to us. Only the script and language model are downloaded.
  • Google Fonts — the Nunito typeface on the site and in the app.
  • YouTube in youtube-nocookie.com mode — embedded videos on the blog and, where used, at route stops. After playback, YouTube (Google) may process data under its own policy.

These services have their own privacy policies. We do not operate them and do not automatically receive a copy of your data from them.

If you use the location button in the app, the browser will ask for GPS access. Coordinates are used to fill a starting point and are not sent to our server.

4. What we plan and have not switched on yet

  • Google AdSense — ads. Once the account is approved, we will paste the official code and enable Google’s certified consent message (Privacy & messaging in the AdSense account). We will not ship a homemade banner that pretends to be certified.
  • Google Analytics (or similar statistics) — if we add it, we will update this policy with the legal basis and how to withdraw consent.

The ads.txt file is currently only a commented template, with no invented publisher ID.

5. Cookies

The site does not currently set its own tracking cookies. Your browser may store technical data (the app’s localStorage, font and library caches). The third parties listed above may set their own cookies according to their rules when their content loads, especially after a YouTube video is played.

When ads are enabled, cookie and ads consent will be handled by Google’s certified CMP. The Cookie settings link will point to it. Until then, that page is only an overview of what the site uses — not a fake certified banner.

6. Legal basis, retention, your rights

localStorage in the app is processed on your device at your request (using the game). Loading maps and libraries is based on our legitimate interest in running a working site, or on consent where an advertising or analytics tool will require it.

Data in localStorage is kept only in your browser; there is no copy on our server unless you use the optional online account (see section 2). Data held by third parties is governed by their policies.

If we start processing personal data ourselves (especially after accounts launch), you will have the right of access, rectification, erasure, restriction, portability, objection, and the right to lodge a complaint with a supervisory authority (in Czechia, the Office for Personal Data Protection). Contact for these requests: KONTAKT_EMAIL.

7. Changes

We will update this policy when services change, when an account, ads or analytics are added, or when operator details are filled in. Date of this version: 14 November 2026.