Privacy Policy
Last updated: 21 September 2026
RUNMAKER is a web app that builds running routes. This page explains what data it touches, why, and what you can control.
1. Who operates RUNMAKER
RUNMAKER (runmaker.pages.dev) is operated by an individual developer. You can reach the operator through the contact page.
2. Data we process, and why
| Data | Why it is used | Where it goes |
|---|---|---|
| Location you choose (current position, a searched place, or a map tap) | To compute walkable routes around that point. | Sent to our routing endpoint, which forwards the coordinates to a third-party pedestrian routing service (openrouteservice by HeiGIT). Coordinates are not stored by RUNMAKER after the route is returned. |
| Place search text | To find addresses and places you type. | Sent to our geocoding endpoint, which forwards it to a third-party geocoding provider (LocationIQ). |
| Device location (GPS) | Only when you press the "my location" button and your browser grants permission. | Read in your browser and used like any other chosen start point. You can decline the permission and search or tap the map instead. |
| Saved routes, route names, language choice | So My Routes and your language survive a reload. | Stored in your browser's local storage only. Never uploaded. Clearing site data removes them. |
| Shared route links | So a route can be opened on another device. | The route is encoded in the link itself. Anyone with the link can open it. |
RUNMAKER has no accounts and does not ask for your name, email, or payment details.
3. Analytics
When enabled, RUNMAKER uses Google Analytics 4 to understand which steps of the flow are used and where people drop off (for example, "route built" or "link shared"). Analytics runs in Consent Mode: until you grant consent through the consent prompt, only cookieless, aggregated signals are sent. You can change your choice at any time from the consent prompt.
4. Advertising and cookies
RUNMAKER may show a single Google AdSense ad unit on the route result screen. Google and its partners may use cookies or device identifiers to serve and measure ads, and in some regions to personalise them.
- Ad requests are only made after you have responded to the consent prompt (Google's certified consent management platform) where that prompt applies to your region.
- You can opt out of personalised advertising at Google Ads Settings and learn how Google uses data from partner sites at policies.google.com/technologies/partner-sites.
- Other third-party vendors listed in the consent prompt may also use cookies to serve ads; their choices are managed in that prompt.
5. Third-party services
- Cloudflare Pages — hosting. Cloudflare may log requests (IP address, user agent) for security and delivery.
- openrouteservice (HeiGIT) — pedestrian routing for coordinates you choose.
- LocationIQ — place search.
- Google Analytics, Google AdSense, Google Privacy & Messaging — analytics, ads, and consent, as described above.
Each provider processes data under its own privacy policy.
6. Retention
RUNMAKER does not keep a server-side record of routes, locations, or searches. Data stored in your browser stays until you clear it. Analytics and advertising data retention is governed by Google's settings and policies.
7. Children
RUNMAKER is not directed at children under 13 and does not knowingly collect personal data from them.
8. Your rights
Depending on where you live, you may have the right to access, correct, or delete personal data, or to object to certain processing. Because RUNMAKER holds no server-side personal data, most of this is under your direct control (browser storage, consent prompt, Google Ads Settings). For anything else, contact us.
9. Changes
Updates to this policy will be posted on this page with a new "last updated" date.