Skynat
Provides and runs the technology: the apps, the panels, the servers, security and updates. Licenses the platform to operators and charges a flat fee per order.
Data & contracts
Clear lines: who does what, and who sees what.
A delivery network involves five parties. This page sets out how they relate and where each kind of information lives. The binding detail is in the operator agreement and the terms each party accepts.
The parties
How the contracts fit together.
Operator
Runs a territory under an operator agreement with Skynat. Signs up and approves stores and riders, receives customer payments into its own accounts, pays out earnings and looks after local support.
Store
Sells its products through the platform in the operator's territory, sets its prices and stock, and receives its earnings from the operator.
Rider
Delivers orders in the territory, accepts the jobs they choose, and receives their earnings and tips from the operator.
Customer
Orders from stores in the app, on the web or on WhatsApp, and pays through the methods the operator offers.
Who holds which data
Information stays with the people who need it.
The platform collects what a delivery needs and no more, and shows each party only what their role requires.
| Information | Stored | Who can see it |
|---|---|---|
| Customer account and address | The region's database | The customer; the store and rider for that order only; the operator for its territory |
| Orders and order history | The region's database | The customer, the store that filled it, the operator of that territory |
| Card numbers | Never stored by us | Only the payment provider |
| Payment money | The operator's own gateway account | The operator |
| Rider location | Only while on a delivery | The customer during their delivery, the operator, and anyone the rider shares an SOS trip link with |
| Store and rider documents | The region's database | The operator, to approve them |
| Admin and operator actions | A tamper-evident audit log | Skynat and the operator, for accountability |
Data stays in the country when the law says so
A region can run on its own database in-country. Each country's data-protection requirements are on its launch checklist, and the region cannot go live until they're done.
Consent, recorded
Customers agree to how their information is used when they sign up, and that consent is recorded, as POPIA in South Africa and similar laws elsewhere require.
An audit log that can't be quietly edited
Every admin and operator change is logged with before and after values. Each entry is sealed against the one before it, so an edited or deleted entry shows up.
Questions about the agreement?
We'll take you through the operator agreement in detail once you apply.