Privacy
This page has two parts. The desktop app: Route Map has no telemetry, no account and no automatic update check; what it sends, to whom and when is below, the same text as PRIVACY.md and Help, Privacy in the app. This website, getroutemap.app, is covered separately at the end: it uses Cloudflare Web Analytics, keeps a download log without addresses, and uses Google Analytics only if you accept it.
Route Map runs on your machine. It has no account, no telemetry and no automatic update check. Nothing is sent anywhere until you run or open a trace.
What leaves this machine
| What | To | When |
|---|---|---|
| Public router hostnames from the trace | CAIDA Hoiho, api.hoiho.caida.org | each trace, unless Hoiho is off in Settings; answers are cached locally for 30 days |
| Public hop IP addresses the offline DB-IP Lite City file does not place (all of them while it is not installed) | RIPEstat, stat.ripe.net | each trace, unless the IP database is off |
| Public hop IP addresses, their routed prefixes and AS numbers, for route details (prefix, RPKI, RIS paths and visibility, BGP updates, AS overview) | RIPEstat, stat.ripe.net | after each trace; abuse contact and RIR only when you open a hop's details |
| The two countries and the public name of a RIPE Atlas anchor, for a typical latency between them | RIPE Atlas, atlas.ripe.net | after each trace; public data, no key, no credits |
| Your RIPE Atlas key and the target, to list your own earlier measurements | RIPE Atlas, atlas.ripe.net | only when you choose Compare with an Earlier Atlas Measurement |
| A download request for DB-IP Lite City and ASN | DB-IP, download.db-ip.com | only when you choose Download on first run, Settings > Update now, or routemap data update |
| PTR (reverse DNS) queries for public hops with no name | your own DNS resolver | each trace, unless reverse DNS is off |
| Your public IP address, to find your city | RIPEstat, stat.ripe.net | at startup, only while no origin is set in Settings |
| Your RIPE Atlas API key, your network's AS number (or your country code if no probe is on your network), and the target | RIPE Atlas, atlas.ripe.net | only when Atlas is on in Settings with your own key and you choose Trace from a RIPE Atlas Probe. RIPE NCC publishes every measurement, target included |
| Your public IP address, to find your network's AS number for the Atlas probe | RIPEstat, stat.ripe.net | only for an Atlas trace |
| Your public IPv4 or IPv6 address (the family of the trace), to be the target of a reverse trace and to find your network's AS so the probe is not in it; the target's address, to find its AS | RIPEstat, stat.ripe.net | only when you choose Reverse Trace (or --reverse) |
| Your RIPE Atlas API key, the probe chosen near the target, and your public IP address as the measurement target | RIPE Atlas, atlas.ripe.net | only when you choose Reverse Trace after agreeing to it (Settings > RIPE Atlas > Withdraw consent stops it), or run --reverse --publish-my-ip. RIPE NCC publishes the measurement, your IP included |
| A request for the latest release tag | GitHub, api.github.com | only when you choose Check for Updates or run routemap --check-update |
A download of the release file for your system, SHA256SUMS and SHA256SUMS.ed25519 | GitHub, github.com and its release-asset host release-assets.githubusercontent.com | only when you choose Download and check after Check for Updates. Not counted by the project site |
Continuous mode (Watch) sends the same ICMP echo probes as a trace, to the target and the routers on the way, once per hop per cycle and at most 30 a second, until you stop it or it reaches its time limit. The lookups above run once for the hops of the first cycle and then only for a hop or router not seen before, never every cycle. It never uses RIPE Atlas.
Paths sends ICMP echo probes to the target and the routers on the way, as a trace does, with different flow identifiers; on Windows it sends TCP connection attempts to the target's port 443 instead, each closed at once (one that reaches the target is an ordinary connection, so the target's operator sees your address, as when you visit it), plus one ICMP echo for each hop where no TCP probe was answered. At most 20 a second and at most 1,500 per discovery. Its lookups are those of one trace, made once for every router any path answered from.
DNS timing looks up the target's name (IPv4 and IPv6) through your system resolver at each trace, and through each resolver you add in Settings > Probes (none by default), nowhere else. Plain DNS is not encrypted. The trace then goes to the address that lookup returned. With Online lookups off (or --offline), only the system resolver is asked: the trace needs that lookup.
Port tests (Ports, or Test these ports with every trace) send one TCP connection attempt to each chosen port of the traced address, at most 32, and for TLS ports a TLS ClientHello with the target's name; each connection is closed at once. The target's operator sees your address, as when you visit it.
Remote agents run on a server you name in Settings > Agents, over your own ssh client: one connection per trace you start, nothing in the background. The server then sends the probes, the DNS lookups and the port tests, from its own address. If the agent is placed "from its public IP", the server looks itself up at RIPEstat, so RIPEstat sees the server's address; "City" makes no lookup. Route Map stores the agent's name and SSH destination only, never keys or passwords, and never receives the server's address: exports name the agent and its place. The provider's first hops of an agent trace are hidden unless you show them. Every lookup about the hops is made from this computer, as for any trace.
The Paths interception check (Windows, part of a Paths run) sends two TCP connection attempts at each of TTL 1 and 2 and up to two ICMP echoes to the target, counted in the same limits.
Settings > Sources > Online lookups switches every row above except the trace itself, the explicit update check and downloads you start: off, nothing new leaves this machine, and hops are placed from the offline data (carrier site codes, DB-IP Lite City and ASN) only.
Private, CGNAT and reserved addresses (your own network and your ISP's carrier NAT) are never looked up anywhere. Your origin coordinates are never sent to anyone, RIPE Atlas included: they only rank Atlas probes on your machine.
Every request to these services identifies the app in its User-Agent (routemap/<version> (+https://github.com/osintph/routemap; traceroute geolocation)), and RIPEstat requests also carry sourceapp=routemap-desktop. The project runs no server of its own that the app talks to.
When this list changes, this file and Help > Privacy change with it. Questions: [email protected].
What stays on this machine
In the config folder (macOS ~/Library/Application Support/routemap/, Windows %APPDATA%\routemap\, Linux ~/.config/routemap/):
settings.json: your settings, including the origin and your RIPE Atlas key if you entered one (readable only by your user where the OS allows).settings.previous.jsonis the same file as the version before an upgrade left it. Asettings.json.unreadableorhistory.json.unreadableis a file the app could not read, set aside instead of written over; delete it once you no longer need it.cache.sqlite3: Hoiho answers for router hostnames, andipgeo-cache.sqlite3: IP database answers for public hop addresses, each kept 30 days by default. Clear both in Settings or withroutemap cache clear.history.json: the last 50 traces, only while history is on. Clear it in Settings or the History panel.site_codes.tsv: only afterroutemap sites update.ripe-cache.sqlite3: RIPEstat route details and Atlas baselines, each kept for its own short lifetime (30 minutes for BGP updates, up to 30 days for registration data).routemap cache clearand Settings clear it too.data/: DB-IP Lite City (when you download or import it) and DB-IP Lite ASN (unpacked from the app on first use). No trace data is written there.
Network adapters. The adapter list, its addresses and gateways are read locally from your operating system. They are never sent anywhere. History and exports keep the adapter's kind and name; addresses and gateways go into an export only when you tick Include this computer's interface addresses and gateways in the Export dialog (--interface-addresses on the command line).
Comparisons are made from routes already on this machine (the current trace, an export you choose, or your own Atlas measurements); nothing is stored for them. Exports are written only to the file you choose.
This website
This part is about getroutemap.app, not the app. The site records visits and downloads for two reasons: download analytics (which platforms and versions people use, and where they find the project) and abuse prevention (telling people from scanners and bots).
Cloudflare
The site is served through Cloudflare and counts visits with Cloudflare Web Analytics, which sets no cookies. Cloudflare's privacy policy applies to what it handles.
Downloads
The download links on this site go through /dl/, which sends your browser on to the
same file on GitHub. For each download the server writes one line to its download log with:
- the time, and the release and file;
- the two-letter country Cloudflare passes on with the request;
- the network the request came from and its operator, as an AS number and name (for example "AS9299 Philippine Long Distance Telephone Co."), and whether that network looks like a home or mobile provider, an organisation, or a hosting provider; this is looked up on the server in IP Geolocation by DB-IP (DB-IP's IP to ASN Lite database, CC BY 4.0) and a list of hosting networks;
- the kind of client: the browser and operating system family (such as "Firefox on Windows"), or the name of a tool (such as curl or a download manager), and whether a byte range was asked for;
- the referring site cut to its address (a page on this site is written as
site); - a daily visitor hash: a code made from your address and a random value that the server creates each day, keeps only in memory and throws away at midnight Manila time. The same address gives the same code for the rest of that day, so downloads within a day can be grouped (an installer and its checksums, for example). The code cannot be turned back into the address, and with the daily value gone, it cannot link downloads on different days.
The download log stores no address and no browser string, in any form; download requests leave no line in the server's error log, and the notifier that reads the download log stores no address either. The maintainer is told about downloads by email, with a daily summary. The lines are deleted after 30 days; from then on only the number of downloads per day is kept. GitHub serves the file itself and sees the download as it sees any other; its privacy statement applies there.
An update made from inside the app (Help > Check for Updates, then Download and check) is downloaded from GitHub directly, not through this site. It leaves no line in the download log and does not appear in the site's download statistics.
Google Analytics
The site also uses Google Analytics, but only if you accept it in the banner that appears on your first visit. Until you accept, and if you reject it, no Google script is loaded, no Google cookie is set and nothing is sent to Google.
- If you accept, Google Analytics sets two cookies on this site:
_ga, to tell visitors apart, and_ga_<ID>, to keep track of a visit; each lasts up to two years (browsers may cut that short). - Google then receives the pages you view, how you arrived, your browser, device and screen, scrolling and clicks on links that leave the site, and which download you click (file, platform and version), so the numbers can be compared with the download log. Google derives a coarse location (country, region, city) from your address; it states that Analytics does not log or store individual IP addresses of users in the EU, Switzerland or the UK.
- The site tells Google that you agreed to analytics only: consent for advertising cookies, for sending your data to Google for advertising, and for personalised advertising is set to "denied".
- Your choice is kept in your browser's local storage, not in a cookie. To change it, use Cookie settings at the foot of any page; withdrawing consent deletes the Google Analytics cookies and stops Analytics from loading.
- Google's privacy policy and how Google uses information from sites that use its services apply to what Google receives.
Server logs and your browser
For every page other than the download links, the web server keeps a standard access log (address, time, page, browser) and an error log for operating the site; both are kept for 30 days. The access log is also copied to another server the maintainer runs, where it is shown as visitor statistics behind a login; the copies are deleted after 30 days as well. Country and network are looked up on that server in local DB-IP databases, and no visitor data is sent to a third party for this. The light or dark choice and your Analytics choice are kept in your browser's local storage; nothing is sent anywhere because of them. Every page reads fully with scripts turned off, and then nothing from Google loads.
Questions: [email protected].