Deliveries Privacy Notice
Effective Date: 18 September 2026 Last Updated: 24 September 2026
This notice covers DiscoverWorthy Deliveries, the driver's app. It sits alongside our Privacy Policy and adds to it — everything in that policy still applies. Where this notice is more specific about the driver's app, this notice governs.
It exists because a delivery round is different from the rest of the platform. The app carries a list of real people's names, addresses and phone numbers to their front doors, and it can take a card payment on the doorstep. Both deserve saying plainly rather than folding into a general policy.
1. Who is responsible for what
For the driver's own account — the pairing that links a phone to a shop, and the rounds assigned to it — we are the data controller.
For the customers on the round — their names, addresses, phone numbers, what they ordered and what they paid — the shop is the controller and we are its processor. We hold that information because the shop asked us to, and we act on its instructions. We do not use a shop's customer list for DiscoverWorthy's own purposes, and we never contact anybody on it ourselves.
2. Location
The app asks for location, and only for one reason: taking a card at the door.
Tapping a card uses Stripe's Terminal SDK, and that SDK refuses to take a payment unless it can establish where the payment happened. It is a fraud and dispute control, and it is Stripe's requirement rather than ours.
What that means in practice:
- The permission is requested at runtime only when card tapping is switched on. A driver who never takes a card at the door is never asked for location, and never sees the prompt.
- It can be declined. Card tapping then does not work; the rest of the round — the stops, the visits, marking a delivery — works exactly as before.
- The location goes to Stripe, with the payment. DiscoverWorthy does not record where a driver is, and the app has no tracking of any kind: no breadcrumb trail, no live map of the van, nothing a shop could use to watch a driver's movements.
On Android, depending on the phone's version, this is coarse or precise location. On iPhone it is location while the app is in use, and never in the background. Neither is kept by us.
3. Taking a card at the door
Card details are read by the phone and go to Stripe. They do not pass through the Deliveries app, and they do not pass through us. What we record is the outcome — that a payment of a certain amount succeeded, and its reference.
4. What is held on the phone
The round, its stops and the visit records are stored on the device, so that a driver in a spot with no signal can still work. A stop marked delivered is recorded locally and queued, then sent when there is signal again.
That is deliberate: nothing on the doorstep path waits on a network. It does mean a phone holds a copy of that round's customer details until it syncs, which is worth knowing when deciding who carries the phone.
5. Handing a stop to a maps app
Tapping Navigate passes the stop's address to whatever maps app the driver already has installed, such as Apple Maps, Google Maps or Waze. At that point the address is in that app's hands and its own privacy policy applies. We pass the address and nothing else: no customer name, no phone number, no order.
6. Scanning a bag
The app can use the camera for one thing: reading the code printed on a delivery docket.
A delivery order's kitchen docket carries a small square code. Pressing Scan a bag opens the camera so the driver can point it at that code and take that delivery, instead of finding it in the list.
- The camera permission is asked for only when Scan a bag is pressed. A driver who never scans is never asked. Saying no costs nothing but the scanner: every delivery can still be taken by tapping Take it on the list.
- The code is read on the phone itself (by a reader in the app on Android, and by the iPhone's own built-in reader on iPhone). No picture is taken, kept or sent anywhere, and nothing the camera sees leaves the phone.
- All the code contains is which order it is. The only thing sent to us is the same request Take it sends: that this phone is taking that order.
7. What the app asks permission for
The Deliveries app requests these Android permissions and no others (on iPhone it only ever asks for location and the camera, for the same reasons):
- Internet and network state — to pair, read the round and send visits back, and to know whether it currently can.
- Location — only for card tapping, as set out in section 2.
- Camera — only for scanning a bag, as set out in section 6.
Stripe's SDK also brings in coarse location and wifi state. It does not ask for contacts, microphone, or access to your files. There is no advertising identifier in the app, and no analytics or crash-reporting tool of any kind — the app reports nothing about how a driver uses it.
8. The demo round
The app offers a pretend round for anyone without a pairing code, so it can be seen before it is set up.
A demo round holds no credential of any kind and never contacts our servers. The street, the customers and the orders in it are fictional. Nothing done in a demo leaves the phone, including the fact that it was tried.
9. Where it is kept, and your rights
Round and payment records are stored in Microsoft Azure in the Australia East region. Retention, your rights, and how to make a request are as set out in the Privacy Policy. Questions specifically about the driver's app can go to support@discoverworthy.com.