Respatch Logo
Respatch
Respatch Logo
Respatch

Legal document // TL-01

Terms of Service

Effective date: October 24, 2024
Please read these terms carefully before accessing the Respatch global network.

01Platform usage

Access to Respatch infrastructure is strictly provisioned for authorized entities. Users must maintain secure credentials and adhere to operational quotas as defined in their organizational SLA.

The platform targets high availability for core routing nodes. Respatch is not liable for latency introduced by third-party logistics carriers or edge network fluctuations.

02API license

Subject to these Terms, Respatch grants you a limited, non-exclusive, non-transferable, and revocable license to access and use the Respatch APIs solely for integrating your application with our logistics network.

API keys are strictly confidential. You are solely responsible for all activities occurring under your keys. In the event of a suspected breach, you must rotate keys immediately via the Respatch developer portal.

03Wallet funding & payments

Respatch operates on a pre-funded wallet ledger. Users must maintain a positive balance to initiate delivery requests.

Per-dropoff charging model

Billing is executed deterministically per successful dropoff. Funds may be held upon request initiation and committed to the ledger only upon confirmed delivery by the destination node.

  • Base rate (example zone)Configurable / dropoff
  • Surge multiplierVariable based on network density
  • Failed delivery (client error)Per policy
  • Failed delivery (network error)Refund per policy

Fiat conversions to platform credits are processed via authorized financial partners and may be subject to disclosed fees. Ledger entries are governed by your agreement and applicable law.

04Data sovereignty

Respatch acts as a data processor for payload metadata required for routing. Customer data (PII) should be protected using industry-standard practices including encryption at rest and in transit.

Data residency options may be configurable via product settings or API. By default, metadata may be routed through optimal nodes, which can cross borders. Customers requiring strict localization must specify geographic boundaries in configuration and contracts.

05Termination

Either party may terminate this agreement with written notice as specified in your order form or enterprise agreement. Respatch may suspend access for severe security violations or sustained ledger defaults as described in policy.

Upon termination, active API keys may be revoked. Outstanding wallet balances may be refunded minus applicable fees within a commercially reasonable period, subject to fraud and compliance review.