Data we expect to handle
Public contact details, support messages, request category, technical security records, and the minimum data needed to respond. Authenticated product data will be governed separately by role, organization, shipment, purpose, and sensitivity.
How data is used
To answer requests, provide product guidance, triage support, protect the service, and maintain an auditable operational record. Public chat does not authorize booking, payment, insurance, compliance, or account-access decisions.
Data minimization
Do not submit passwords, bank details, identity documents, health or qualification records, precise live shipment locations, or payment-card information through public forms or chat.
Sharing and providers
Approved infrastructure, communications, identity, payment, routing, and support providers may process limited data for their configured purpose. Provider names and contractual details remain to be approved.
Retention and requests
Public contact and support retention periods, deletion processes, legal holds, and privacy-request channels require stakeholder and legal approval before launch.