The sovereign architecture eases compliance. Personal data and routes live in your node — not in the ledger — so each jurisdiction applies its own rules to its own data.
The immutable ledger never contains personal data. That's a property of the architecture, not a configuration you have to remember to set.
Each jurisdiction applies its own rules to data held in its own node — never to a shared pool.
Drivers, networks, agents and merchants are verified before they ever operate.
An authority audits its own network against the ledger — cryptographically, on its own evidence.
A contractual continuity plan and full data portability when you leave the network.
Because personal data and routes stay inside your node, each jurisdiction governs its own data directly. The immutable ledger carries no personal data — by design, not by configuration.
Verification is a precondition, not an afterthought. Each kind of participant is checked to the standard their role demands — and to the standard their jurisdiction requires.
Documentary, biometric and background checks per jurisdiction — completed before a driver operates.
Legal-entity verification at onboarding — a network is a verified entity before it joins.
Responsible-party verification before protocol access — no anonymous access to the network.
A transport authority audits its own network against the ledger — verifying reputation and payments cryptographically. Governance decisions are recorded and immutable; routing rules are public and versioned.
The transport authority audits its own network against the ledger — verifying reputation and payments cryptographically, on its own evidence.
Governance decisions — onboarding, sanctions, changes — are recorded and immutable. The record of who decided what, and when, can't be rewritten.
Routing rules are public and versioned — demonstrable neutrality. Anyone can read the rule that applied, and the version that was in force.
| Verifiable against the ledger | Stays in the node (under jurisdiction) |
|---|---|
| Driver identity and verification status | Trip routes and passenger personal data |
| Portable reputation (append-only ledger) | Fares and local operating rules |
| Signed payment events (hash + amount, no personal data) | Local payments and card data |
| Governance decisions and versioned routing rules | Own-brand app and fleet operations |
Build status. The network layer — registry, ledger, roaming and protocol — is on the roadmap and shown as a target architecture, not a live service. The operation plane — node, apps, dispatch, payments and tracking — is what ships today.
A contractual continuity plan keeps you running, and full data portability means leaving the network is a process, not a hostage situation.
Specific certifications will be declared only once obtained, or verifiably in progress. We claim none on this page — and we'd rather earn your trust by showing the architecture than by listing a badge.
What we will do is walk your legal and compliance team through the jurisdiction model, the KYC standards, the audit path, and the continuity terms — under NDA where appropriate.
Protection by jurisdiction, KYC before anyone operates, an immutable and auditable record, public versioned rules, and a clean exit — designed so your team can verify it, not just be told it.
