Storage technologies.

1. Current position

ROAD does not currently use advertising cookies, analytics pixels, behavioural profiles, device fingerprinting or cross-service tracking. The technologies listed below support sign-in, security, a user-requested display preference, an in-progress feature or the website opening sequence.

Because the current technologies are used for authentication, security, requested functionality or a simple appearance preference, ROAD does not display a general “accept all” cookie banner. If non-essential tracking is introduced, ROAD will update this notice and implement any PECR consent or objection control required before use.

2. App authentication

Supabase authentication cookies. These keep a member signed in, refresh the authenticated session and protect requests. Their exact names and duration can vary with the Supabase client and session. Disabling them prevents account sign-in and authenticated ROAD features.

ROAD administrator cookie. A signed cookie named for ROAD administrator access authenticates authorised administration. It expires no later than 12 hours after issue. It is not used for advertising or member tracking.

3. Local storage

road_registry_view. Stores the public-registry display choice on that browser so ROAD can remember the view selected by the visitor. It is a preference, not a marketing identifier. It remains until the person changes the preference or clears site data.

Legacy source files contain local-storage utilities for an identity fallback and invitation mock, but the inspected live account flows supply Supabase-backed callbacks and do not rely on those fallback stores. ROAD must update this notice before reactivating them in production.

4. Session storage

Teams issuance draft. Temporarily holds an in-progress team-issuance draft for the current browser or web-view session and is removed when the session ends or the browser clears it.

road-arrival-seen. The public flagship website uses this session flag to avoid replaying the opening arrival sequence repeatedly during the same tab or browser session. It expires with session storage and is not sent to ROAD as analytics.

5. Provider logs

Vercel, Supabase, Resend, Apple and network providers can create request, security, delivery or operational logs on their own systems. Those are not browser cookies set for ROAD advertising. Their contents, locations and retention depend on the provider configuration and contract and must be recorded in ROAD’s production processor register.

6. Controls

• Use browser settings to inspect or delete cookies, local storage and session storage for roadco.uk or app.roadco.uk.
• Private-browsing mode generally removes local session data when the private session closes.
• Deleting authentication cookies signs you out. Blocking them prevents signed-in features.
• Clearing road_registry_view resets the registry preference. Clearing road-arrival-seen allows the opening sequence to play again.
• For help or an objection about the appearance preference, email contact@roadco.uk.

7. Changes

ROAD will update the version and date when a storage technology, purpose, provider or control changes. A new analytics, advertising or tracking tool must not be enabled merely by changing this page; the service must first implement the required technical choice.

See the Privacy Notice for the wider processing record.