Know where route data goes.

What is stored

Your sign-in identity, workspace membership, original CSV or XLSX content, confirmed column mapping, fleet rules, route matrix, generated plan, evidence hashes, dispatch checkpoints, exceptions, recipient confirmation, any optional driver location or photo proof, and any Business scope request you submit are stored in the isolated RouteThai Cloud data project. They are used to build and replay your workspace history or respond to your request.

Anonymous Preview · pre-sign-in file inspection

After you confirm and submit one CSV or XLSX file, Anonymous Preview performs a structural check in that request's memory, bounded to 100 KiB, 50 stops, 10 vehicles, and 30 seconds. The first step calls no geocoder or road provider. RouteThai does not persist file bytes, rows, addresses, coordinates, names, demand, rules, or geometry. HMAC-pseudonymous abuse counters and short compute leases expire within 24 hours. The result is Preview only and cannot be saved, shared, dispatched, or used as customer evidence.

For a complete coordinate file, you may separately enter the depot coordinate and consent under routethai-public-road-consent-v1. Only depot and stop coordinates are then sent to the configured public road provider for matrix and geometry evidence—never row references, names, addresses, demand, rules, contacts, or account data. Provider, budget, matrix, or geometry failure is visible and never replaced with straight-line or stale authority.

A complete road result may issue a signed, single-use Preview Receipt for at most 30 minutes. It contains only opaque ids, policy and consent versions, count buckets, and result hashes; it supports post-sign-in attribution only and still requires Workspace resubmission. Acquisition telemetry keeps only coarse size/count buckets, format, consent version, result/error, duration bucket, and campaign values explicitly present in the page URL for 30 days—never the file, locations, file name, source hash, IP address, or network fingerprint.

Optional workbook interpretation

For an unfamiliar Excel layout, you may explicitly allow DeepSeek to draft column meanings. RouteThai sends only column labels, aggregate type counts, and bounded operation, time-window, or vehicle-tag categories. It does not send source rows, customer names, addresses, identifiers, coordinates, or map links. The draft cannot plan or dispatch work; you must apply and review it, and deterministic validators still verify every source row. A saved Import Recipe lets the same Workspace recognize that exact column layout later without another model call.

Public road routing

A run sends only the depot and stop coordinates to the configured public OSRM service, and only after you check the consent box. A verified workspace cache is used first. RouteThai does not send your original CSV, customer labels, demand, or fleet rules to OSRM.

Driver and customer links

Driver links can update one assigned route, including optional action location, live location while the route page remains open, recipient-confirmed proof of delivery, and an optional photo. Customer links are read-only and show only one stop’s status plus the driver's latest shared position while that route is active. Raw links are shown only after creation or rotation; RouteThai stores one-way token hashes. Treat each link as confidential and rotate it if it is shared with the wrong person.

Location and photo retention

Live location is opt-in, limited to one update every 30 seconds, and stops when the driver turns it off, leaves the route page, or ends the route. A customer sees only a position updated within the last 15 minutes on an active route. Location rows are removed after 24 hours. Photo proof is limited to JPEG, PNG, or WebP files up to 2 MB, stored in a private bucket, and opened by workspace members through a short-lived signed link.

Access and deletion

Workspace membership controls operator access. RouteThai requires a verified email sign-in and creates one durable personal workspace per account, so drafts and history can be restored across sessions and devices. Planning runs stay in history until an owner, admin, or planner deletes them. A plan attached to a dispatch cannot be deleted because it is execution evidence. Deleting the final unused run for a source also removes that source and its coordinate-bearing road cache. The action cannot be undone.

Optional customer outcomes program

A Workspace owner or admin may opt in from Insights to contribute aggregate outcome counts to RouteThai's customer report. The report excludes demo sessions and never contains Workspace names, source rows, customer comments, addresses, or coordinates. Public results remain hidden below three participating Workspaces and retain the denominator and observation floor for each metric.

You can revoke consent at any time. Revocation excludes the Workspace from future snapshots; it does not rewrite an earlier immutable aggregate snapshot that was already generated without Workspace identity.

Current limits

Synchronous planning supports up to 50 stops and 10 vehicles. Durable asynchronous planning supports up to 200 stops and 20 vehicles on best-effort infrastructure. The service includes workspace restoration, dispatch, opt-in foreground location, photo or drawn-signature proof, optional barcode evidence, configured email or SMS delivery, exception handling, and operator-triggered in-progress re-planning with preserved lineage.

There is no paid availability commitment. RouteThai does not provide continuous background GPS after the route page closes, commercial live-traffic authority, a continuously staffed planning queue, payment settlement, or a guarantee of global optimality. Public road and geocoding providers can be unavailable or change their results.

Driver destination links do not contact Google when the route page loads. If a driver selects Open navigation, that stop's coordinates are sent to Google Maps under Google's own terms. The RouteThai access token is removed from the address before the link can be opened.