Privacy Policy
Last updated: 7 July 2026
NodeHop (“we”, nodehop.cc) is a free planner for cycling routes along the numbered cycle-node networks of Belgium, the Netherlands and Germany. This policy explains what we collect and why. Questions: admin@nodehop.cc.
What we collect
- Account details — if you sign in with Google, Microsoft, Apple, Facebook or email, we receive your email address and, where provided, your name and avatar. That’s it.
- Routes you save — the routes you choose to save (and whether you make them public), plus any likes, follows and comments you create.
- Location — if you tap “Use my location”, your device shares your position with the map to plan a route. We do not store your location history.
- Basic usage counts — anonymous tallies (e.g. routes built) to understand product usage.
How we use it
To provide the service: sign you in, save and share your routes, power the social features, and send routes you request to your Garmin, Wahoo or other bike computer. We do not sell your data or use it for advertising.
Service providers
We rely on a few processors to run NodeHop: Vercel (hosting), Supabase (database & auth), Resend (email), Wahoo (when you send a route to your Wahoo), and OpenStreetMap / BRouter for map and routing data. Each only receives what’s needed for its function.
Cookies
We set only essential cookies: a sign-in session, your saved preferences (language, theme), a short-lived region hint used to show this cookie notice where it’s legally required, and a record of your cookie choice. These don’t need consent. We use no advertising or cross-site tracking cookies. Anonymous analytics are off by default and only run if you opt in. In the EU/EEA, UK and Switzerland you’re asked to choose before any non-essential cookie is set, and you can change your mind anytime: .
Your rights
You can view, edit or delete your saved routes at any time, and request deletion of your account and associated data by emailing admin@nodehop.cc. Under the GDPR you may access, correct, export or erase your personal data.
Changes
We’ll update this page if our practices change, with a new “last updated” date.