1. Who is responsible
Live Roads (liveroads.co.uk, “the Service”) is part of the Roadscore group and is run by Maurício Amaro, as an individual. Under the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018, he is the controller of the personal data handled by the Service.
For any request or question about your data, write to [email protected].
2. In short
- No account, no password. You can use the whole site without giving us anything.
- Google Analytics sets cookies only if you accept them in the cookie banner; until you choose, or if you decline, Google receives only anonymous signals with no cookie and no identifier. No advertising cookies, no social media pixels, no tracking across sites.
- We never sell or rent your data, and we never use it for anyone else's marketing.
- We keep only what you give us on purpose (an email address, an alert subscription, a question to the assistant, a partner request) and a visit count that does not store your IP address.
3. What we handle, and why
Counting visits
For each page you open we record: the page address, the page that sent you (referrer), the kind of device (computer, mobile or bot, worked out from your browser's user agent), the country (supplied by Cloudflare from your IP address), the date and time, and a daily visitor code. That code is a one-way cryptographic hash of your IP address, your browser's user agent and today's date, mixed with a secret value. It changes every day at midnight (UTC), so nobody can follow a visitor from one day to the next. Your IP address is not stored, and no cookie is used for this. It tells us how many people use each page.
To leave yourself out, open any page with ?notrack=1 at the end of the address: the choice is saved in your browser and its visits are no longer sent, and Google Analytics stays off too. ?notrack=0 undoes it.
Google Analytics: cookies only with your consent
We use Google Analytics 4 to understand which pages are useful, with Google's Consent Mode. On your first visit a banner asks whether you accept analytics cookies; declining is as easy as accepting.
Before you accept, or if you decline, no analytics cookies are set and nothing is stored on your device for Google Analytics. Google receives only cookieless signals with no identifier (that a page was viewed, the page, the time, and the basic browser and device information any web request carries), which it uses to estimate visit numbers in aggregate. They cannot be linked to you or to your other visits.
If you accept, Google Analytics also stores cookies (_ga and _ga_<ID>, which last up to two years) holding a random identifier, and collects the pages you open and the page that sent you, the time spent and the clicks and scrolls on a page, your type of device, browser, operating system, screen size and language, and an approximate location (country, region and city) that Google works out from your IP address. Google Analytics 4 does not log or store IP addresses. The identifier in the cookies lets it tell a returning browser from a new one. We see only aggregated reports, never anything that names you; we don't send it your email or anything you type, and we don't turn on Google's advertising features (Google signals, remarketing or ad personalisation).
Google acts as our processor under its data processing terms for Google Analytics. To withdraw your consent, use Cookie settings (also in the footer of every page): from then on no analytics cookies are used, and the ones already on this site are removed.
Alerts on this device (push notifications)
When you turn on alerts (on the home page, a road page or a nation page) and allow notifications, your browser creates a delivery address (endpoint, a long link to its notification service, not your name or number) and two encryption keys. We keep those three items, what you chose to follow (roads, nations, or everything), your browser's user agent, and the dates you subscribed and last updated your choices. We don't know who you are: only your browser's push service knows which device an endpoint belongs to.
Alerts are about closures and serious crashes. To avoid sending the same one twice and to keep to a cap of four alerts per hour, we log each (incident, endpoint) pair sent.
Your location, only if you ask
With alerts on, you can choose “Near me”. Your browser then asks for permission, and we receive the position it shares (latitude, longitude and how accurate it is). It has one use: alerting you to incidents within 25 km (about 15 miles). We keep only the latest position, never a history: each new one replaces the last. A position is only used for alerts for 24 hours; when you come back to the site with “Near me” on and permission already given, your browser quietly sends a fresh one. Switching “Near me” off, or turning off all alerts, deletes the position at once. Positions outside the UK are refused.
“Near you” on the home page
Without asking you anything, the block uses the approximate city that our network provider (Cloudflare) associates with your connection, worked out on the server from your IP address; if there is none, it shows a list of the Met Office's warning regions. Only if you press “Use my location” does your browser ask for your position, which is rounded to about 1 km (half a mile) in your browser before it is sent in the body of the request (never in a web address). Our server uses it for that one answer, from data it already holds, and sends it nowhere else. It is not stored or logged, and it is not tied to alerts. Your browser keeps only your choice (the region, or “use my location”), with no coordinates, for your next visit; clearing this site's data removes it.
The morning email
If you sign up, we keep your email address, the roads and nations you chose, how often you want the email (daily or weekly), a random code for the confirmation, settings and unsubscribe links, and the dates you signed up, confirmed, last changed your settings and were last sent an email. It uses double opt-in: nothing is sent until you click the link in the confirmation email, and an address that is never confirmed is erased after 30 days. Without a click after 24 hours, one reminder goes out with the same link, never more. Resend tells us whether the confirmation or the reminder was delivered, opened, clicked or refused; we keep those states without your address. Every email has an unsubscribe link, and also carries the one-click unsubscribe header that email apps such as Gmail show as an “Unsubscribe” button. Unsubscribing erases your email address at once, unless you are also on the Stauven waitlist, in which case only the morning email stops. When an address is erased (you unsubscribe, we remove it, or it is never confirmed within 30 days), we keep only an anonymous record with no address and nothing that leads back to you: the lists it was on, the roads and nations, the frequency and the dates. We use it only for statistics, such as how many people signed up or left.
The fuel price email
If you sign up for fuel prices, we keep your email address, the fuel you chose, and either the postcode you typed (with its coordinates and district, from postcodes.io) or the nation you picked, plus the average price we last told you about and when, so the next email can say how it moved. It sits in the same table as the morning email and uses the same double opt-in, single reminder and 30-day erasure of unconfirmed addresses. The stop link in every fuel email ends only that email, and deletes your postcode and its coordinates at once; if you are on no other list, your email address is erased too. When an address is erased we keep only an anonymous record (the fuel, whether it was a postcode or a nation, and the dates), never the postcode.
Route alerts
If you save a journey at /traffic-alerts, we keep your email address, the start and destination you chose (their names and coordinates), the route between them, the time you leave, the days, a random code for the confirmation and manage links, the dates you set it up, confirmed and cancelled it, and which incidents we have already told you about that day. We use it only to email you, before you leave, when a closure or an accident is on that route. It uses double opt-in: nothing is sent until you click the link in the confirmation email, and an alert that is never confirmed is erased after 30 days. Every alert has a link to pause or cancel it. Cancelling erases your email address, the names and coordinates of your start and destination and the route at once. As with the morning email, we keep only an anonymous record with no address and nothing that leads back to you: the time, the days, the roads and the dates, used only for statistics.
The waitlist for Stauven, the Live Roads app
If you join the waitlist at /app, we keep your email address, the phone you told us you use (iPhone or Android, if you answered), what you want first (if you picked anything), the date you asked and the same random code used by the confirmation and leave links. We use it only to tell you about Stauven: when there is a version to try and when it launches. It sits in the same table as the morning email: if you already get that email, joining the waitlist changes nothing about it. It uses double opt-in too: without the click in the confirmation email you are not on the list, and an address that is never confirmed is erased after 30 days. As with the morning email, one reminder goes out after 24 hours without a click, never more. The leave link in every email takes you off the waitlist only. If you are on another list, the phone and choices you gave are deleted; if you are on no other list, your email address is erased and, as with the morning email, only an anonymous record (no address: the lists, phone type, choices and dates) is kept for statistics.
Traffic assistant
When you ask the assistant a question, we store the text of the question, the answer, the data tools it used, whether the answer came from a short-term cache, whether it was part of a longer conversation, and the same daily visitor code used for counting visits. Your IP address is not stored; it is only held in the server's memory to limit how many questions can be asked in a row. To answer, the question and the earlier messages of the same conversation (up to eight in total) are sent to Anthropic (see section 5). If your question names a place, that place name may be looked up in the place search services listed in section 5.
Questions and answers are kept without a fixed deletion date, to improve the service and understand what drivers ask. Please don't put personal details in your questions: the assistant doesn't need them. If you typed something personal, email us and we will delete it.
Route check
When you check a route, the places you type are sent from our server to a place search service to find them, and the route is worked out on our own routing server. Search results are cached on our server for up to a day so repeat searches don't go out again; nothing else you type there is stored.
Partner requests
Through the form on the partners page, councils, operators and other organisations leave their name, organisation, role, email, phone (if they give it), type of organisation and a message. We store the request and receive a copy by email, only to reply and to set up the partnership.
API keys
If you ask for a key to our public API, we keep the name or project, email, what you said it is for, the website or app link if you gave one, when you agreed to the attribution terms, the plan and the key's dates. Every API request is logged with its IP address, the address and parameters asked for, the answer's status, the browser or program and, where sent, the referring site. We use this to run the trial and the plans, limit abuse and contact key holders about changes. The IP addresses in the request log are erased after 30 days and the rest of the log is kept; the key's details are kept while the key exists. If you ask us to delete them, we erase your name, your email, what you said the key is for, the website or app link and the IP addresses linked to the key, and keep the rest (plan, dates and request log) with nothing that identifies you. Requests made later with a deleted key are refused and logged without the IP address.
In your browser
A few settings live only on your device (in localStorage), never on our server: light or dark theme, the “don't count my visits” choice, and a summary of what you follow with alerts (including whether “Near me” is on), and your answer to the cookie banner. Alerts also install a small service worker that only shows the notifications. Clearing this site's data in your browser removes all of it. The only cookies are Google Analytics's, and only if you accept them; Cloudflare may also set a strictly necessary security cookie to tell people from bots.
Server logs
As with any website, our host (Railway) and our network provider (Cloudflare) log the requests that reach them: IP address, page, browser, date and time. These logs are used for security and to diagnose faults, and are kept by those providers for their own periods.
4. Legal bases (UK GDPR, article 6)
- Consent (article 6(1)(a)): alerts on your device, “Near me” location, the morning email, the Stauven waitlist and Google Analytics cookies. You can withdraw it at any time, as easily as you gave it (article 7(3); see section 7).
- Steps before a contract, at your request (article 6(1)(b)): the partner request form, and API keys and plans.
- Legitimate interests (article 6(1)(f)): counting visits, keeping the assistant's questions and answers to improve it, the cookieless, identifier-free Google Analytics signals sent before you choose, looking up the places you type in route check, and server logs for security. We chose ways that don't identify you (no stored IP address, a code that changes every day) and you can object (section 7).
Cookies and similar technologies. Under the Privacy and Electronic Communications Regulations (PECR), storing things on your device needs your consent unless it is strictly necessary for something you asked for. Google Analytics's cookies are not, so they are set only after you accept them in the cookie banner; before that, Google Analytics runs without cookies or identifiers. Everything else we store in your browser is either a choice you made (theme, alerts, opting out of visit counts, your cookie choice) or needed for security.
5. Who else handles it
Only the providers that make the Service work, each for its own part:
- Railway (USA): hosting for the site, its database and our routing server.
- Cloudflare, Inc. (USA, global network): delivery and protection against attacks. It sees the IP address and requests of everyone who visits and supplies the country used in visit counts.
- Resend (USA): sends the confirmation emails, the morning email, the fuel price email, route alerts and the copy of partner requests to our inbox. It receives the address and content of each email.
- Anthropic, PBC (USA): writes the assistant's answers. It receives the text of the conversation, not your IP address. Under Anthropic's commercial terms, data sent through its API is not used to train its models.
- Browser push services (Google, Apple, Mozilla, Microsoft): deliver the notifications. The content is encrypted with your browser's keys.
- OpenFreeMap: serves the map images, which your browser downloads directly, so OpenFreeMap sees your IP address when the map loads.
- Photon (komoot) and postcodes.io: place search for route check, the assistant and the fuel price email. Our server sends them the place name or postcode, never your IP address.
- Google LLC / Google Ireland Limited: Google Analytics, as our processor. It receives the data described under “Google Analytics: cookies only with your consent”: cookieless, identifier-free signals before you choose, and the full measurement only if you accept.
The traffic, roadworks and weather sources (National Highways, Traffic Wales, the Met Office and the others credited on the site) are queried by our server, not by your browser: none of your data reaches them.
International transfers. Several of these providers are outside the UK, mainly in the USA. Where a provider is certified under the UK Extension to the EU-US Data Privacy Framework, transfers rely on it; otherwise they rely on the UK International Data Transfer Addendum to the standard contractual clauses. Only what is needed to run the Service is transferred.
6. How long we keep it
- Visit counts: after 90 days we erase the daily visitor code (and anything after the path in the referring address). The remaining rows are anonymous (page, referring site, country, device type, time) and we keep them to measure audience over time. Your IP address is never stored.
- Alert subscription: while it is active. It is deleted at once when you turn off all alerts, or automatically when your browser's push service tells us it no longer exists.
- Location: only the latest position, used for 24 hours, and deleted when you switch “Near me” off or turn off alerts.
- Log of alerts sent (incident, endpoint): 14 days.
- Morning email: your address is kept while you are subscribed. Unsubscribing erases it at once, and unconfirmed addresses are erased after 30 days; only an anonymous record (no address: lists, roads, nations, dates) is kept, for statistics.
- Route alerts: your address and journey are kept while the alert exists. Cancelling erases them at once, and unconfirmed alerts are erased after 30 days; only an anonymous record (no address, places or route: time, days, roads, dates) is kept, for statistics.
- Stauven waitlist: your address is kept while you are on the list. Leaving, or 30 days without confirming, erases it, as with the morning email, and only an anonymous record (no address) is kept, for statistics.
- Assistant questions and answers: kept without a fixed deletion date, to improve the service and understand what drivers ask, with no IP address and nothing that links a question to you. Ask us by email to delete anything personal you typed.
- API keys: while the key exists; on request we erase the name, email, stated purpose, website and linked IP addresses and keep the rest; later requests with a deleted key are refused and logged without the IP address. API request log: kept, but its IP addresses are erased after 30 days.
- Partner requests: while we are talking with the organisation, or until it asks us to delete the request.
- Server logs: the periods set by Railway and Cloudflare, usually from a few days to a few weeks.
- Google Analytics: its cookies (only if you accept them) last up to two years, or until you withdraw consent or clear them; the data in Google Analytics is kept for 14 months, then deleted by Google.
7. Your rights
Under UK GDPR you can, free of charge:
- ask for a copy of the data we hold about you (access, article 15);
- have inaccurate data corrected (rectification, article 16);
- have your data deleted (erasure, article 17);
- ask us to limit how we use it (restriction, article 18);
- receive data you gave us in a portable format (portability, article 20);
- object to anything we do on the basis of legitimate interests (objection, article 21);
- withdraw consent at any time, without affecting what was done before (article 7(3)).
We make no automated decisions with legal or similarly significant effects on you (article 22).
Much of this you can do yourself, straight away: “Turn off all alerts” or “Stop alerts” where you turned them on, switching “Near me” off, the unsubscribe link in every email, ?notrack=1 for visit counts, and Cookie settings (in the footer) for Google Analytics. For anything else, write to [email protected]. We reply within one month. Because there are no accounts, we may ask for something that shows the data is yours (for example, writing from the subscribed address).
You can also complain to the Information Commissioner's Office (ICO) at ico.org.uk, although we would be glad to sort it out with you first.
8. Security
All traffic uses HTTPS. The database sits on a private network with restricted access, push subscription keys can only be used to send notifications to that one browser, and each credential has only the access it needs.
9. Children
The Service is not aimed at children. We don't ask anyone's age, and in the UK only people aged 13 or over can give their own consent to services like the morning email or alerts. If you are a parent or guardian and think a child under 13 has given us an email address, write to [email protected] and we will delete it.
10. Changes to this policy
If the Service starts handling data in a new way, this page changes first, with the date at the top updated. Changes that affect a consent you have already given will be announced to subscribers.