Cookies and Device Storage
Effective
The short version
One cookie, and it exists so that signing in works. No analytics, no advertising, no third-party tracking script, and no cookie consent banner — because there is nothing non-essential to consent to, and a banner implying otherwise would misrepresent what this site does. Requesting a ResQ as a guest sets no sign-in cookie at all.
A summary, not a replacement. The full text below is the version that applies.
Most cookie policies are long because most sites carry a lot of tracking. This one is short for the opposite reason.
The whole list#
One cookie. It is called rq_session, and it exists so that signing in to an account works.
- What it holds: a random token. Not your name, not your email, not anything readable.
- Why it exists: without it, every page load would forget who you are.
- Who can read it: it is marked
httpOnly, so page scripts cannot read it at all — only the server sees it. - Cross-site behaviour: it is set to
SameSite=Lax, so a bookmarked link works but another site cannot make your browser use it on a form post. - Encryption: in production it is marked
Secure, so it only travels over HTTPS. - How long it lasts: a session goes idle after about eight hours of no activity, and expires completely after seven days regardless. Signing out deletes it immediately.
That is the entire list. There is no second cookie.
If you never sign in#
You do not need an account to request a ResQ. If you use RoadResQ as a guest, no sign-in cookie is set, because there is no session to remember.
Other things stored on your device#
Your browser caches page files — stylesheets, images, fonts — the way it does for every site, so pages load faster the second time. That cache lives on your device, RoadResQ cannot read it, and it is not a record of you.
If you add RoadResQ to your phone's home screen, your browser keeps a copy of the app's files locally so it opens quickly. Those are the site's own files, not information about you.
No consent banner, and why#
If tracking is ever added, this document gets a new version and the question of consent gets asked properly.
Do Not Track and Global Privacy Control#
These browser signals exist to switch off cross-site tracking. There is no cross-site tracking here for them to switch off.
Outside services#
Some parts of RoadResQ can be connected to outside services — sending an email, drawing a map. Which ones are actually switched on is listed below, generated from this installation's live configuration rather than written down and left to drift.
When this document changes#
Changes are published as a new version with its own date, and the old version stays readable.
Outside services in use right now
Email delivery
In useSending you one confirmation, with your reference and tracking link, when you send a ResQ and gave an email address — and sending a password-reset link if you ask for one. Nothing else: no status updates, no marketing.
Text messages and voice calls
Not usedNo messaging provider is connected. The application sends no text message and places no call.
Photo and file storage
Not usedNo outside storage provider is connected. Photos stay on the server that runs RoadResQ.
Address lookup
Not usedNo address-lookup provider is connected. Addresses are whatever you type, and no location is sent to a lookup service.
Map tiles
In useDrawing the map image behind the location pin. The map provider receives the map area your browser requests.
There is no analytics provider, no advertising network and no third-party tracking script anywhere in RoadResQ, configured or otherwise. The typefaces are served from RoadResQ’s own domain, so loading a page does not call out to a font host.