Privacy should be explicit wherever trade identity and payment data are involved.
This page now exists so the interface no longer routes users to dead links. Replace this draft language with your approved legal copy before launch.
Current privacy coverage in the product
The content below is written to match the platform flows already visible in the UI, but it is not a substitute for formal legal approval.
Information the platform collects
The interface currently suggests business identity details, account credentials, compliance documents, trade communications, and transaction metadata as the main categories of data.
Why the data is used
The product flows imply onboarding, fraud prevention, verification, order execution, shipment tracking, and customer support as the primary legal and commercial reasons for processing data.
How long records are retained
Retention should follow compliance, payment, and dispute requirements. For a live system, exact retention periods should be defined with counsel and reflected here rather than left implicit.
Sharing with operational partners
Some order and identity data will need to be shared with logistics providers, payment processors, and compliance partners when that data is necessary to deliver the service.