Cookie Policy

This Cookie Policy explains how Rouptimize uses cookies, local storage, secure storage, and similar technologies on the public website, web dispatcher, driver mobile app, and related services.

How Rouptimize uses cookies, local storage, secure storage, and similar technologies across the public website, web app, mobile app, and checkout.

Effective date: 13 June 2026

Last updated: 13 June 2026

Rouptimize is based in Australia and works internationally. Company legal details, retention periods, subprocessors, governing law, refund terms, and regional privacy obligations should be reviewed by qualified Australian counsel before public launch.

What Cookies And Similar Technologies Are

Cookies are small files stored by a browser. Local storage stores data in the browser. Mobile secure storage may store authentication tokens in the driver app. Similar technologies can include SDKs, logs, pixels, and device identifiers.

Rouptimize uses these technologies to keep users signed in, remember preferences, protect the service, support checkout, and operate the product.

Where Rouptimize Uses Them

Surfaces

Public landing website.

CMS/admin surfaces where applicable.

Web dispatcher panel.

Driver mobile app secure storage and device/application storage.

Stripe checkout and other third-party pages.

Cookie Categories

Strictly necessary

Authentication/session cookies, access and refresh token handling, security and CSRF-related cookies where used, locale routing, CMS admin cookies, and payment checkout/session handoff cookies controlled by Stripe.

Preferences

Language, locale, dashboard panel, sidebar, and interface preferences stored in cookies or local storage where used.

Analytics and performance

Analytics or performance cookies should be listed only if an analytics provider is enabled. Current code review did not identify a public analytics provider such as Google Analytics, PostHog, Plausible, or tracking pixels.

Marketing and advertising

Marketing or advertising pixels should be listed only if they are added and approved. Current code review did not identify active marketing pixels.

Mobile app storage

The driver mobile app may use secure storage for access and refresh tokens, async storage for sensor-streaming permission state, device IDs, and queued telemetry/sensor data while streaming and sync are active.

Current Cookie Audit Table

Before publishing, audit the public website, pricing page, contact page, panel login, financial settings, CMS/admin domain if public, and a Stripe checkout test session.

Initial cookie audit table Name | Provider | Category | Purpose | Surface | Status --- | --- | --- | --- | --- | --- [cookie name] | Rouptimize | Strictly necessary | Authentication, session, or security | Web dispatcher | Confirm before publishing [locale/preference key] | Rouptimize | Preference | Remember language or interface preference | Website/web app | Confirm before publishing access_token | Rouptimize | Strictly necessary | Web authentication if stored as a cookie by the panel | Web panel | Confirm exact attributes [Stripe cookie] | Stripe | Strictly necessary/payment | Checkout, fraud prevention, and payment processing | Stripe checkout | Confirm through Stripe audit [analytics cookie] | [provider] | Analytics | Website measurement | Website | Only add if enabled [marketing cookie] | [provider] | Marketing | Advertising measurement | Website | Only add if enabled

How Users Can Control Cookies

Controls

Users can block or delete browser cookies in browser settings.

Blocking necessary cookies may prevent login, checkout, security features, or app functionality.

If non-essential cookies are used, users should be able to accept, reject, or change consent preferences where required.

Mobile users can control app permissions through device settings.

Drivers can revoke location permission, but route tracking may be limited or unavailable.

International Cookie Consent Position

In Australia, cookies can involve personal information when they identify or reasonably identify a person, so Rouptimize should describe them transparently in privacy materials.

For EU/UK visitors, non-essential analytics or marketing cookies generally require consent before use. If Rouptimize adds analytics or marketing pixels, a consent banner and preference center should be implemented where required.

Changes And Contact

Cookie practices may change as Rouptimize adds or removes technologies. Updates will be posted with a revised last updated date.

For cookie questions, contact privacy@rouptimize.com or use the contact page.