TfL API keys

If you paste a key for live demos, it stays in this browser under tfl-user-api-key.v1. You can keep it for later visits or limit it to the current tab. Clear it from the same dialog that saved it.

Boards offer two key modes. Save key on this browser stores the key in this browser and omits it from generated Board URLs and QR codes. Another device will need its own key entry.

If that option is off, the Board URL includes the key in the hash fragment after #. This is a portable setup option for another tablet or unattended display. The hash is not sent to this site's server, logs, analytics, or referrers. Anyone with the complete link can use the key and its quota.

Keys are not sent to logs, analytics, or unrelated services from this app. Validation talks to api.tfl.gov.uk from the browser.

A Home Screen Board stores its layout in this browser under tfl-board-installed.v1 and keeps the TfL key in the same credential store. Neither the layout nor the key is sent to this site's server.

Visitor count

A first-party cookie named tfl_vid deduplicates the footer visitor count. It is a random id, not a login. Clearing site data removes it.

Fonts

This site loads P22 Underground from Adobe Fonts (use.typekit.net). Switch to Hammersmith One on Typography to stop that request. Hammersmith One ships with the page.

Other local data

Font preference and feedback drafts can also sit in localStorage. Component installs and GitHub stars are counted on the server from registry requests and the GitHub API, not from a tracker on every page.

Analytics

Page views and a small set of product events (landing, Board setup, docs visits) go to Vercel Web Analytics. TfL keys, searches, and Board URLs are not included. There is no advertising tracker.