Location Privacy Notice

Knowing where your vehicle is, is the difference between help arriving and help driving past. That does not make every kind of location tracking reasonable, so this notice separates them.

Three different things, often confused#

1. Where the vehicle is#

This is the destination. You confirm it once, and it does not move.

It comes from your device's location, if you allow that, or from an address you type — either one on its own is enough. Typing the address is a complete path, not a degraded fallback, and you can use RoadResQ without ever granting location permission.

When a device fix is used, RoadResQ records how accurate the device said it was and shows that honestly. A reading accurate to 800 metres is not displayed as a precise pin.

This location deliberately does not follow you. If you walk to a gas station while you wait, the destination stays with the car.

2. Your phone's live location during an active ResQ#

Optional. Off unless you switch it on, with its own consent step separate from accepting the Terms, and its own version of this notice recorded against your ResQ.

It exists because knowing where you are, as distinct from the car, genuinely helps: confirming you are still with the vehicle, or finding you if you moved somewhere safer to wait.

You can stop it at any point during the job, and the time you stopped is recorded. Declining it does not affect whether RoadResQ comes out.

3. The responder's live location during an active job#

While someone is working your ResQ, their position can be shared with you so that "on the way" is something you can see rather than something you are told.

It is tied to that job. It starts when they start and it ends when the job ends.

What is actually recorded#

For each position: latitude and longitude, the accuracy radius the device reported, and — only when the device supplies them — heading, speed and altitude. A value the device did not provide stays empty. It is never filled in with a plausible guess.

Two times are stored for every fix: when the device took the reading, and when the server received it. They differ when a phone buffers a position through a dead signal, and the first one is what determines whether a position is current.

Who sees it#

• The confirmed vehicle location: the owner and authorised staff, and anyone holding your tracking link.
• Your live location: the owner and authorised staff working the job. It is also shown to you on your own tracking page.
• The responder's live location: you, on your tracking page, during the job.

Nobody buys it, and nobody is given it for marketing.

How sharing starts and stops#

It starts only after you turn it on at the consent step. There is no version of this where sharing is on by default.

It stops when any of these happens:

• You switch it off.
• The ResQ reaches a final state — completed, cancelled, or unable to complete.
• Your tracking link expires.

The moment sharing started and the moment it stopped are both recorded on the ResQ.

The limitation nobody likes admitting#

What RoadResQ does about it is refuse to fake it. If the last position is eleven minutes old, the page says the fix is eleven minutes old and labels it stale — it does not keep a dot glowing as though it were live. If you want your position to keep updating, keep the tracking page open with the screen awake.

How freshness is described#

A position is labelled by age: updating normally, recent, stale, or no signal. A twenty-minute-old fix is never called live, and every label is written in words as well as colour so it reads the same to everyone.

What location is never used for#

Choosing not to share#

You can decline live location sharing completely and still get service. The only location RoadResQ needs is where the vehicle is, and you can type that in.

If you have already denied location permission in your browser, nothing here nags you to change it. The manual path stays fully usable.

When this notice changes#

Changes are published as a new version with its own date. Every ResQ records which version of this notice was shown when live sharing was consented to, and the old version stays readable.