RouteWave privacy policy

Last updated: 21 July 2026 · Version 1.0.0 · RouteWave home

The short version

RouteWave has no servers, no accounts and no analytics. It does not collect, store or sell your personal information. What you type stays in your browser, except for the journey searches it must send to Transport for London to get you an answer.

What stays on your device

These are saved in your browser profile using chrome.storage.local and never leave it:

You can download or erase all of it at any time from the settings page.

What is sent, and where

Sent toWhat is sentWhy
Transport for London
api.tfl.gov.uk
The start and destination you typed, your route preference, and any stop name you look up for live arrivals. To plan a journey and return live arrival and disruption information. TfL's own privacy terms apply to this request.
Open-Meteo
api.open-meteo.com
A coordinate rounded to roughly one kilometre. By default this is central London, not your position. To give rain, ice and wind advice. Turn this off in settings and no weather request is made at all.

Neither request carries an identifier, an account, a cookie set by RouteWave, or the contents of any page you visit.

Reading web pages

RouteWave can scan the page you are on for London addresses and station names. This only happens when you press Read this page in the popup, or use the right-click menu on text you have selected. The scan runs entirely inside your browser, results are shown only to you, and nothing from the page is transmitted anywhere. RouteWave does not run in the background on any site.

Feedback and reviews

Ratings and comments are saved locally. Sending one is always a separate, deliberate action: you choose to open an email, a GitHub issue or the Chrome Web Store review page, and you can read and edit the message before sending it. RouteWave never transmits a review by itself.

Children

RouteWave is a general travel tool and is not directed at children. It collects no personal data from anyone, of any age.

Changes and contact

If this policy changes, the updated version ships with the extension update and the date above changes. Questions or concerns: open an issue on GitHub. Keeping questions public means the answers are searchable by the next person who asks. The full source code is public too, so every claim on this page can be checked.