Data retention

The Open Platform is a separate product from the tenant API primarily because of what it does not store. This page states the retention boundary precisely.

Request data is not retained

The platform holds no orders, shipments, address records or history. A request carries its own data, a response returns the result, and neither is persisted. There is no endpoint that enumerates prior submissions, because no such record exists.

This is enforced rather than asserted. A test in the suite observes every database query issued during a capability call and fails the build if any query writes, or reads outside a narrow allowlist covering only the platform's own credential and entitlement tables.

Three exceptions

1. Usage counters. Recorded per capability, per key, per hour: call count, billed units and elapsed time. Numeric values only; no payload and no client identifiers. Invoices and the usage page are derived from these counters.

2. Redacted call records, retained for 90 days. Sufficient to diagnose a failed call and to resolve a billing dispute, and no more. The following are removed before storage:

• street addresses, unit numbers and building names
• personal names, telephone numbers and email addresses
• coordinates, reduced to two decimal places (approximately 1.1 km)
• all secrets, signatures and tokens

Country, province or state, city, and the first three characters of the postcode are retained deliberately. Without any geographic information a complaint about a route cannot be investigated; this trade-off is recorded in the data processing agreement rather than left implicit. Records are readable in the portal's call log and expire automatically.

3. Job results, retained for 24 hours. An asynchronous solve stores its result until collection. Results are held in memory rather than in a database table and expire regardless of whether they were retrieved.

4. Network scenario questions, retained for 24 hours. A network.site_scenario question is held, in memory, by the planning engine that answers it, and expires on its own 24 hours after it was asked.

5. Distance snapshots, retained for at most eight hours. A distance snapshot opened for editing a plan holds the plan's points and the road legs measured between them, in memory, and nothing else. It is removed one hour after its last use, eight hours after it was opened at the latest, or when it is closed.

Client-created snapshots

A fleet, depot list or plan may be uploaded once and referenced by an opaque identifier for a limited period, rather than resent on every call. Snapshots are held in memory with a mandatory expiry, keyed by account identifier, and no code path writes one without a time to live. They are a bandwidth optimization rather than storage; a requirement for permanent retention indicates a platform account rather than an Open Platform snapshot.

Where persistent state is available

Persistent state is provided by the platform account at api.superroute.ca: hosted orders, tracking pages, driver applications, shipment lifecycle webhooks and the full delivery operation. It is a separate product with a different retention model, and both may be enabled on the same account.