Privacy notice

1. Who runs this site

Live Roads Singapore (liveroadssingapore.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.
• We use Google Analytics for statistics; you can opt out at any time, and we honour Global Privacy Control. No advertising cookies, no social media pixels, no tracking across other sites.
• We do not sell personal information, and we do not use it for 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 (all of Singapore or chosen expressways), 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 5 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 accidents, never routine road works or heavy traffic, 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, a checkpoint page or an expressway 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 expressways (up to 10) 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 erased after 30 days. If there is no click after 24 hours, one reminder goes out with the same link, never more (this applies to the Vianow waitlist and the alerts below too). Resend tells us whether the confirmation or reminder was delivered, opened, clicked or refused; we keep those states without your address. Every email has a link to change your expressways and an unsubscribe link, and also carries a one-click unsubscribe header your mail app can use. Unsubscribing erases your email address: we keep no list of people who left, only a count of unsubscribes per day. If you are also on the Vianow waitlist, only the emails stop and the waitlist stays until you leave it.

When you unsubscribe, when we remove a sign-up, or after 30 days without confirmation, your email address is erased, and so is any position you gave for alerts. What stays is an anonymous record with no address: the lists you were on, the expressways, how often, your Vianow waitlist answers (if any), and the dates. Nothing can be sent to it and nobody can be identified from it; we keep it only for statistics (how many people sign up, confirm and leave).

The waitlist for Vianow, 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 token used by the confirmation and leave links. We use it only to tell you about Vianow: when there is a version to try and when it launches. It sits in the same table as the email updates: joining the waitlist changes nothing about any email or alert you already get. It is 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. The leave link in every waitlist email takes you off the waitlist only: if you still get other emails from us, the phone and choices you gave are deleted; if you get nothing else from us, your address is erased and only the anonymous record described above (no address) is kept for statistics.

Traffic alerts for your route (email)

When you save a trip at /traffic-alerts, we keep your email address, the names and coordinates of the start and the destination, the driving route between them, the time you leave, the days, and your time zone (from your browser). They are used only to email you, before that time, if there is a closure or an accident on the way. It is double opt-in: without the click in the confirmation email no alert is sent. To avoid repeating an alert, we note the events already sent to you that day. Cancelling (the link in every alert) erases the email, the places and the route at once, and an alert that is never confirmed is erased the same way after 30 days. In both cases only an anonymous record (time, days and dates) is kept, for statistics.

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, number 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, organisation, the type of organisation, 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 IP addresses in the request log are erased after 30 days; the rest of the log is kept. 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.

“Near you” on the home page

Without asking you anything, the block shows what is happening across Singapore. Only if you press “Use my location” does your browser ask for your position, which is rounded to about 1 km 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 the road data it already holds. It is not stored or logged. Your browser keeps only your choice (“use my location” or not), with no coordinates, for your next visit; clearing this site's data removes it.

Google Analytics (statistics), and how to opt out

We use Google Analytics 4 to understand which pages are useful. It runs by default, for statistics only, and stores cookies on your device (_ga and _ga_<ID>, which last up to two years) holding a random identifier that lets it tell a returning browser from a new one.

It 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. 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 service provider: under its data processing terms for Google Analytics it uses this data only to provide the service to us. It is processed in the United States and other countries where Google operates, so it is held outside Singapore.

To opt out, use Opt out of analytics (also in the footer of every page): Google Analytics stops at once in this browser, its cookies on this site are removed, and the choice is remembered. If your browser sends Global Privacy Control (GPC), we treat it as an opt-out automatically. ?notrack=1 also keeps Google Analytics off.

Stored in your browser

The only cookies are Google Analytics's (unless you opt out). The site also 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), your “Near you” choice, the ?notrack opt-out and your analytics opt-out, if you made one. 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. This means the information described here is held outside Singapore; Railway handles it only to run the service for us.
• 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.
• Google: Google Analytics, as our service provider, unless you opt out. It receives the data described under “Google Analytics (statistics), and how to opt out”.

Fonts are served from our own domain. The government and agency feeds we use for road data (the Land Transport Authority, through Roadscore) 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 personal information

We do not sell personal information, and we do not use it for advertising. The site loads no advertising or social media scripts. Our visit count is our own and runs on our own server; the only analytics script from another company is Google Analytics, which you can opt out of, works for us as a service provider and has its advertising features turned off.

7. How long we keep it

• Visit records: 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.
• 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. Counts per alert, with no addresses: 180 days.
• Email updates: your address until you unsubscribe. Unconfirmed sign-ups: 30 days. Vianow waitlist: while you are on the list; leaving deletes what you gave for it. Unconfirmed sign-ups: 30 days. After that, only an anonymous record with no address (lists, expressways, dates) is kept, for statistics.
• Traffic alerts for your route: while the alert exists. Cancelling erases the email, the places and the route; an alert never confirmed is erased the same way after 30 days. An anonymous record (time, days, dates) is kept, for statistics.
• 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: kept, but its IP addresses are erased after 30 days.
• Partner requests: as long as the conversation or partnership lasts. Ask and we delete yours.
• Google Analytics: its cookies last up to two years, or until you opt out or clear them; the data in Google Analytics is kept for 14 months, then deleted by Google.

8. Your choices

• Visit counts: ?notrack=1 opts this browser out.
• Google Analytics: on for statistics unless you opt out, or your browser sends Global Privacy Control. Opt out at any time in Opt out of analytics (also in the footer); it applies straight away.
• 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 expressways or unsubscribe you in one click.
• Anything else: email [email protected] to see what we hold about you, correct it or have it deleted. We will act on the request, usually within a few days. If you are not happy with how we handled it, you can complain to the Personal Data Protection Commission (pdpc.gov.sg). We handle personal data in line with Singapore's Personal Data Protection Act 2012 (PDPA). 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].