Privacy Policy

This describes what RoadResQ does with your information. It describes what the application actually does — not a wishlist, and not a generic template.

What RoadResQ collects#

When you request a ResQ#

• Your name and phone number, and your email if you give one.
• Which contact method you prefer.
• The vehicle: year, make, model, trim, colour, plate, type and powertrain, as much as you fill in.
• What is wrong, which service you chose, and your answers to the questions attached to it.
• Where the vehicle is: the coordinates you confirm, or the address you type, or both, plus the kind of place it is (street, driveway, parking lot, highway shoulder), any notes you add, and roadway details like direction of travel or nearest exit when they are relevant.
• How accurate your device said that location fix was.
• Whether you consider the spot safe to wait in.
• Photos, if you choose to attach any.
• Anything you write in the note field.

While a ResQ is active#

• Your phone's live location, only if you turn that on — see the Location Privacy Notice.
• The responder's live location while they are working your job.
• Timestamps for each stage: requested, accepted, on the way, arrived, started, finished or cancelled.
• Messages and status updates exchanged about the job.
• Any extra work proposed, and your approval or refusal, with the time and the way you gave it.

If you create an account#

An account is optional. If you make one: your email, your name and phone, your saved vehicles, and your ResQ history. Your password is stored as a scrypt hash — RoadResQ cannot read it, and neither can anyone who steals the database.

Automatically, for security#

• Your IP address and browser identification when you sign in or submit something, kept so abuse can be traced and rate limits enforced.
• Session records for signed-in accounts.
• An audit trail of actions taken inside the operator's console.

If you contact RoadResQ#

Your name, whichever of email or phone you provide, the category you picked and the message you wrote.

Notifications#

If the owner or a staff member enables push notifications on a device, that device's push subscription is stored so a new ResQ can wake them up. This is operator equipment, not customer devices.

Why RoadResQ has it#

• To provide roadside assistance.
• To locate your vehicle.
• To dispatch someone and get them to you.
• To tell you what is happening with your ResQ.
• To run your account, if you have one.
• To keep a record of the work performed.
• To record your authorisation for that work and its price.
• To detect and prevent fraudulent and abusive requests.
• To keep the platform secure.
• To meet legal, tax and accounting obligations.

What RoadResQ does not do with it#

There is no analytics product, no advertising pixel and no third-party tracking script anywhere on this site. See Cookies and Device Storage.

Who can see your information#

• The owner and any staff they have authorised. Access is limited by role, and actions taken in the operator's console are logged.
• Anyone you give your tracking link to. The link is a key: it opens the status and location information for that one ResQ. Share it with someone coming to meet you; do not post it publicly.
• Outside services that are actually configured. The live list is further down this page.
• Law enforcement or a court, where RoadResQ is legally required to hand something over, or where there is a genuine safety emergency. RoadResQ does not volunteer customer information outside those situations.

Nobody else.

Photos#

Photos are optional. They exist to help with the job — showing a responder what they are walking into, and recording the condition of the vehicle before and after work.

They are not published, not used in marketing, and not shown to anyone outside the job without asking you first.

Keeping it safe#

• Passwords are stored as scrypt hashes, never as readable text.
• Session tokens and tracking tokens are stored as hashes, so a database read cannot resurrect a live link.
• Access to the operator's console is gated by role, and privileged actions are recorded.
• Repeated failed logins lock an account temporarily rather than letting someone grind through passwords.

No system is perfectly secure, and saying otherwise would be a lie. RoadResQ keeps a written incident-response procedure, and if something happened that affected your information, telling you would be part of handling it — not an afterthought.

Your choices#

You can:

• Ask what RoadResQ holds about you.
• Ask for something inaccurate to be corrected.
• Ask for your location trail or your photos to be deleted.
• Turn live location sharing off at any time during a ResQ, or never turn it on.
• Opt out of marketing messages, if you ever opted in. Operational messages about an active ResQ are not marketing and continue.

Use the contact details at the foot of this page. Some records of work actually performed have to be kept — for tax, accounting, or an unresolved dispute — and those cannot be deleted on request.

Children#

RoadResQ is for vehicle owners and people authorised to act for them. The service is not directed at children, and RoadResQ does not knowingly collect information from them.

When this policy changes#

Changes are published as a new version with its own date, and the old version stays readable at its own address. Every ResQ records the version of this policy that was in force when it was requested.