Readable only by the consumer
A rider and the consumer it sends to agree on a key using ML-KEM-768, a post-quantum key exchange standardised as FIPS 203. The key itself is never sent anywhere: not to drivers, not to Thummer.
A cargo passes through strangers' phones, so it has to be protected from the moment it's created. Here's how, in plain language.
A rider and the consumer it sends to agree on a key using ML-KEM-768, a post-quantum key exchange standardised as FIPS 203. The key itself is never sent anywhere: not to drivers, not to Thummer.
Every cargo is encrypted on the device with AES-256-GCM under that key, strong enough to stay safe against future quantum computers. Drivers carry it and Thummer routes it, but neither can read it.
Each device makes its own identity and secret, and you claim it into your account by scanning its claim code. Thummer checks every cargo against that secret (HMAC-SHA256), so nobody can send cargo in your device's name, change it in transit, or use up your limits.
Drivers and apps reach the cloud over TLS 1.3, preferring the hybrid post-quantum key exchange X25519MLKEM768. Even over an older connection, the cargo inside is already encrypted end to end.
Delivery receipts are signed with HMAC-SHA256 under a key only the rider and the cloud share. Drivers can carry receipts back but can't fake one.
Every rider, driver, consumer and account is authenticated. Message size and frequency are limited by account class, duplicates are recognised, and sign-in and sign-up attempts are rate limited.
Passwords are stored as bcrypt hashes, and API keys as hashes or encrypted copies. Signing in is rate limited, and administrators can require a password change.
Create an account