Privacy Policy

Rouptimize is based in Australia and provides delivery route optimization, dispatch, monitoring, proof-of-delivery, reporting, support, and route-order-credit billing software. This Privacy Policy explains how Rouptimize handles personal information when people visit the website, contact the team, use the web dispatcher, use the driver mobile app, interact with support, buy route-order credits, or use integrations.

How Rouptimize handles personal information across the website, web dispatcher, mobile driver app, billing, support, and integrations.

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.

Who We Are

Rouptimize provides delivery route optimization, dispatch, monitoring, proof-of-delivery, reporting, support, and route-order-credit billing software.

This policy applies to the public website, web dispatcher, driver mobile app, billing workflows, support, contact forms, documentation, tutorials, and integrations where enabled.

Personal Information We Collect

Website and contact information

Full name, work email, phone number, company name, company website, company size, monthly scheduled order range, fleet size, operation type, current planning method, inquiry type, response preference, timezone, timeline, message content, consent confirmation, and submission timestamp.

Account, company, and admin information

Company name, address, email, website, verification status, account status, branches, depots, users, roles, permissions, invitations, profile details, and security/account records.

Driver and mobile user information

Driver name, phone, branch, assigned vehicle, license details, working hours, active status, mobile user account details, invite code status, SMS/email notification status, and related metadata.

Mission, customer, and recipient information

Customer or recipient name, phone number, pickup or delivery address, latitude, longitude, mission type, date, time windows, priority, capacity values, service time, notes, pickup details, assigned driver, assigned vehicle, route status, and proof-code verification state.

Routing, monitoring, and reporting information

Routes, stops, route geometry, stop order, planned distance, planned duration, actual execution status, assignment history, mission history, live monitoring data, performance events, and reporting summaries.

Driver mobile location and sensor information

When the driver mobile app has permission and a driver is actively running or navigating a route, Rouptimize may collect location readings, accuracy, altitude, speed, heading, accelerometer readings, gyroscope readings, device context, driver ID, vehicle ID, route ID, and mission execution context.

Billing and payment information

Route-order-credit balances, monthly limits, remaining credits, purchase quantity, amount, currency, status, purchase date, Stripe checkout session ID, payment intent ID, customer ID, and purchase history. Rouptimize should not store full payment card numbers; Stripe handles card processing.

Support, integrations, and technical records

Support ticket subjects, statuses, messages, assigned support users, timestamps, and attachments. Users should avoid uploading unnecessary sensitive data in support requests.

API token names, token prefixes, hashed token values, scopes, creators, expiry, revocation status, webhook endpoint URLs, webhook subscriptions, delivery payloads, responses, and errors where integrations are enabled.

How We Collect Information

Collection sources

Directly from visitors and users through contact forms, registration, settings, imports, billing, support tickets, and app use.

From company admins and dispatchers who enter driver, recipient, mission, vehicle, branch, depot, route, and support data.

From driver mobile devices when location/sensor permissions and active delivery states allow.

From payment processors, notification providers, service providers, logs, cookies, and device/browser metadata.

How We Use Information

Use of information

Provide, maintain, secure, troubleshoot, and improve Rouptimize.

Register and verify companies, authenticate users, manage permissions, and maintain account security.

Configure branches, depots, users, roles, drivers, vehicles, capacities, skills, and working hours.

Import, create, optimize, schedule, assign, monitor, proof, report on, and support delivery missions and routes.

Support driver mobile workflows, navigation context, status updates, delivery history, live monitoring, and proof-code verification.

Process billing, Stripe checkout, route-order-credit balances, purchase history, and payment confirmations.

Respond to contact, onboarding, demo, support, partnership, billing, and product questions.

Send transactional emails, SMS/invite messages, verification messages, security notices, billing notices, and support replies.

Comply with legal obligations, resolve disputes, prevent misuse, and use aggregated or de-identified data for product analytics where appropriate.

Legal Bases For International Users

Final GDPR/UK GDPR controller, processor, and transfer wording should be confirmed by counsel.

Legal bases

Contract, where processing is needed to provide Rouptimize.

Legitimate interests, including security, service improvement, support, fraud prevention, reporting, and business communications.

Consent, including contact form consent, optional marketing, optional non-essential cookies, and mobile location permissions where applicable.

Legal obligation, including tax, accounting, regulatory, data breach, and compliance duties.

Customer Data And Processor Role

Rouptimize customers may control recipient, driver, employee, contractor, route, and operational data they upload or manage. Rouptimize processes that customer data to provide the service.

Customers are responsible for providing lawful data, giving required notices to employees, contractors, drivers, and recipients, obtaining required consents or permissions, and avoiding unnecessary sensitive data.

How We Share Information

A named subprocessor table should be added when vendors and regions are confirmed.

Sharing categories

Hosting, infrastructure, database, and storage providers.

Email, SMS, notification, support, and contact-form providers.

Payment processors, including Stripe.

Mapping, geocoding, navigation, routing, optimization, analytics, monitoring, logging, and security providers where used.

Professional advisers, insurers, auditors, legal advisers, authorities, regulators, or business transfer parties where required or appropriate.

International Transfers

Rouptimize is based in Australia and may process or store information in Australia and other countries where its service providers operate. International customers should expect cross-border processing where needed to provide the service.

Rouptimize should use appropriate safeguards for international transfers where required by applicable law.

Security

No online service can guarantee absolute security.

Security controls

Company-scoped access controls and tenant isolation.

Role and permission management.

Database row-level security in the backend data layer.

Hashed passwords and tokens where applicable.

HTTPS/TLS in production.

Limited administrative access and operational monitoring.

Stripe-handled payment card processing.

Retention

Exact retention periods should be confirmed before launch, especially for mobile telemetry and sensor data.

Retention approach

Account and company data is retained while an account is active and for a reasonable period after closure.

Billing records are retained as required for tax, accounting, dispute, and compliance purposes.

Route, mission, proof, support, telemetry, reporting, auth, security, and backup records are retained as needed for service operation, legal obligations, safety, support, and troubleshooting.

Deletion requests may be limited by customer-controller instructions, legal obligations, billing duties, security needs, backups, or dispute resolution.

Access, Correction, Deletion, And Other Rights

Rights and choices

Request access to personal information.

Request correction of inaccurate information.

Request deletion where applicable.

Object to or restrict certain processing where applicable.

Request portability where applicable.

Withdraw consent where processing relies on consent.

Disable mobile location permissions through app or device settings.

Complain to Rouptimize and, where applicable, to the OAIC or another supervisory authority.

Driver Location And Mobile Permissions

The Rouptimize driver mobile app may request foreground and background location permission. Location and sensor data support active delivery route tracking, monitoring, operational visibility, route performance, and safety context while a driver is working.

Background location may be used so tracking can continue when a driver switches to Google Maps, Waze, or another navigation app. The app should not collect route tracking data when the driver is not authenticated, has not granted permission, or is not actively running or navigating a route.

Cookies And Similar Technologies

Rouptimize uses cookies, local storage, secure storage, and similar technologies for authentication, preferences, security, checkout, and service operation. See the Cookie Policy for details.

Children, Changes, And Contact

Rouptimize is a business delivery operations product and is not intended for children.

Rouptimize may update this policy from time to time. The latest version will show a revised last updated date, and material changes may be notified through the site, app, or email.

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