Privacy

Privacy notice

What Live Roads USA collects, why, how long it is kept, and how to have it deleted. Last updated October 8, 2026.

1. Who runs this site

Live Roads USA (liveroadsusa.com, “the site”) is part of the Roadscore group and is run by Maurício Amaro, as an individual. He decides what the site collects and why.

For anything about your data, including the requests described below, write to [email protected].

2. The short version

  • No account and no password. You can use the whole site without giving us anything.
  • No Google Analytics, no advertising cookies, no social media pixels, no tracking across other sites.
  • We do not sell personal information, and we do not share it for cross-context behavioral (targeted) advertising.
  • 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 never stores your IP address.
  • Our database is hosted in the United States.

3. What we collect, and why

Visit counts

For each page you open, we record: the page address, the page that sent you there (referrer), the kind of device (desktop, mobile or bot, worked out from your browser's user agent), your 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 key. It changes every day at midnight (UTC), so it cannot follow anyone from one day to the next. Your IP address is never stored, and no cookie is used for this. It tells us how many people use each page.

To opt out, open any page with ?notrack=1 at the end of the address: your choice is saved in this browser and your visits stop being counted. ?notrack=0 undoes it.

Alerts on this device (push notifications)

If you turn on alerts and allow notifications, your browser gives us a push address (a long link to its notification service, not your name or phone number) and two keys used to encrypt the messages. We keep those together with what you chose to follow (states and highways), your browser's user agent, and the date you signed up and last updated it.

If you choose “near my location”, your browser asks your permission and we also keep your latest position (latitude, longitude and its accuracy) and the alert radius, about 25 miles (40 km). Only the latest position is kept, with no history: each new one replaces the last. It is refreshed quietly when you come back to the site, only if your browser already allows it, and a position more than 24 hours old is no longer used for alerts.

We use all this only to send alerts about full closures and serious crashes, never routine work zones, and at most 4 alerts per hour per device: anything over that is dropped, not queued. To avoid sending the same alert twice, we log which alert went to which push address and when.

To switch off, use “Stop alerts” or “Turn off all alerts” where you turned them on (the home page, or a state or highway page). That deletes the push address, your choices and your position right away. Removing only “near me” deletes the position. If you block notifications in your browser instead, we delete everything the next time an alert cannot be delivered.

Email updates

If you sign up on the email updates page, we keep your email address, the highways (up to 10) and states you picked, how often you want it (every morning or every Monday), a random token that works as your private link, and the dates you signed up, confirmed and were last sent an edition.

Sign-up is double opt-in: nothing is sent until you click the link in the confirmation email. Addresses that are never confirmed are deleted after 30 days. Every email has a link to change your highways and an unsubscribe link, and also carries a one-click unsubscribe header your mail app can use. Unsubscribing deletes your row: we keep no list of people who left, only a count of unsubscribes per day.

Traffic assistant

When you ask the traffic assistant a question, we store the question, the answer, which data tools it used, whether the answer came from a short-lived cache, whether it found any data, the date and time, and the same kind of daily visitor code described above. Your IP address is not stored: it is held only in memory, briefly, to limit how many questions one connection can send.

These records are kept without a fixed deletion date, to improve the service and understand what drivers ask. Please don't type personal information (names, phone numbers, license plates) into your questions. If you did, email [email protected] and we will delete it.

To write the answer, your question and the last few messages of the same conversation (up to eight, each cut to 600 characters) are sent to Anthropic, the company that makes the Claude AI model. Under its commercial terms, Anthropic does not use data sent through its API to train its models.

Partner requests

If you fill in the form on the partners page, we keep your name, organization, the type of organization, your role, email, phone number if you give it, your message and the date. A copy is emailed to our own inbox. We use it only to reply and to set up the partnership.

API keys

If you create a key for the public API, we keep your name or project name, email, what you said it is for, your website or app if you give one, and when you agreed to the attribution terms. We use them to run the key, its trial and plan, and to tell you when something changes. Each API request is logged with the key, the IP address, the user agent, the page that called it, and what was asked; the request log is deleted after 30 days. The key itself stays until you ask us to delete it.

Spam protection

The forms above (email updates, partners, alerts and the assistant) limit how many requests one connection can send per hour. The IP address used for that is held in the server's memory only and is never written to the database.

Stored in your browser

The site sets no cookies for visitors. It keeps a few items in your browser's local storage, which never leave your device unless noted above: your light or dark theme, what you follow for alerts (so the buttons show the right state), and the ?notrack opt-out. You can clear them at any time in your browser settings.

Server logs

Like any website, our hosting provider (Railway) and our network provider (Cloudflare) see your IP address and keep short-lived technical logs to deliver pages and protect the site from abuse. We don't use them to track or profile anyone.

4. How we use information

We use the information above only to:

  • run the site and deliver what you asked for (alerts, email updates, assistant answers);
  • reply to partner requests;
  • understand, in aggregate, which pages and questions matter to drivers, and improve the service;
  • keep the site secure and stop spam and abuse.

We don't build advertising profiles, and we don't make automated decisions about you.

5. How we share it

We share information only with the service providers that run the site for us, and only what each one needs:

  • Railway: hosts the site and the database, in the United States.
  • Cloudflare: sits in front of the site as a network and security layer, and tells us the country of each visit.
  • Resend: sends our emails (confirmations, email updates, partner notifications).
  • Anthropic: writes the traffic assistant's answers from the conversation it receives.
  • Your browser's push service (Google for Chrome and Android, Apple for Safari, Mozilla for Firefox, Microsoft for Edge): delivers alerts to your device. It sees the encrypted message, not what is in it.
  • OpenFreeMap: your browser loads the map tiles from it directly, so it sees your IP address like any website you load something from. We send it nothing else.

Fonts are served from our own domain. The government and agency feeds we use for road data (state DOTs, the National Weather Service and others) are contacted by our server only and receive no information about you. We may also disclose information if the law requires it.

6. We do not sell or share personal information

We do not sell personal information, and we do not share it for cross-context behavioral advertising. The site loads no advertising, analytics or social media scripts from other companies: our visit count is our own, and it runs on our own server.

7. How long we keep it

  • Visit records: 90 days. After that only monthly totals remain (page views, visitor counts, top pages, referring sites and countries), with no visitor codes.
  • Alerts: until you switch them off, or until your browser's push service tells us the address no longer works.
  • “Near me” position: only the latest one, until it is replaced, until you remove “near me”, or until alerts are switched off.
  • Log of alerts sent: 14 days.
  • Email updates: until you unsubscribe. Unconfirmed sign-ups: 30 days.
  • Traffic assistant: without a fixed deletion date, as explained above. Ask and we delete yours.
  • API keys: until you ask us to delete yours. API request log, with IP addresses: 30 days.
  • Partner requests: as long as the conversation or partnership lasts. Ask and we delete yours.

8. Your choices

  • Visit counts: ?notrack=1 opts this browser out.
  • Alerts: “Turn off all alerts” deletes everything at once; you can also block notifications or location in your browser.
  • Email updates: the links in every email change your highways or unsubscribe you in one click.
  • Anything else: email [email protected] to see what we hold about you, correct it or have it deleted. Residents of any state can do this, and we will honor the request, usually within a few days. Because we don't ask who you are, tell us what to look for (for example the email address you used, or the text of a question you asked).

9. Children

The site is a traffic information service for drivers and is not directed to children under 13. We don't knowingly collect personal information from children under 13. If you believe a child has given us some, email [email protected] and we will delete it.

10. Security

All traffic to the site is encrypted (HTTPS), the database is password-protected, and the admin area needs a login. Push messages are encrypted with your browser's keys. No system is perfectly secure, but we keep what we hold to a minimum, which is the best protection there is.

11. Changes

If the site starts doing something new with personal information, this page changes in the same update, and the date at the top and bottom changes with it.

12. Contact

Questions or requests about privacy: [email protected].

Last updated October 8, 2026.