Privacy policy

What this website collects, and what the DeliveryFreedom product does with personal data.

Last updated: October 2026

This website

This website sets no cookies, runs no analytics and loads nothing from third parties. Fonts, scripts and images are served from the same address.

The only thing stored in your browser is your theme choice (light, dark or automatic), under the key df-theme. It never leaves your device and you can clear it at any time.

The product and the live demo

The dispatcher console, courier app and tracking page process the following personal data: account details of owners, dispatchers and couriers, and service details (name, phone, warehouses, logo); recipient name, phone number and delivery address; courier location while on shift; proof of delivery (a photo, the receiver’s name, a one-time code check); and cash amounts collected and handed over.

Demo environments may use sample data and may be reset without notice. Do not enter real personal data into a demo.

Why the data is processed

To plan, perform and prove deliveries; to show recipients where their parcel is; to reconcile cash; and to keep an audit history of who changed what. Data is not sold and is not used for advertising.

What recipients see

A tracking link shows delivery status, a coarse courier position, the time of the last update, the ETA and an optional delivery code. It does not show the recipient’s own name or phone number, other stops, route history or internal identifiers. Links are random, stored only as hashes, expire, and can be revoked at any time.

How long data is kept

Courier location history and expired tracking tokens are removed on a schedule. The current defaults are 90 days for location history and 30 days after expiry for tracking tokens. These values are configuration placeholders and will be replaced by periods set by counsel.

The order event history is append-only and kept as a business record. Proof photos can be given a retention limit per deployment.

Where the data lives

Each deployment stores its data on servers its operator chooses. Routing, optimisation and map tiles run on the same infrastructure, so locations are not sent to a third-party map provider.

Your rights

You can ask what data is held about you, ask for corrections, or ask for it to be erased, subject to records that must be kept. Requests go to the operator of the deployment you used. The process is documented in the operations runbook and will be finalised after legal review.

Changes and contact

This draft will change before launch. Contact details for privacy requests will be published here when the legal review is complete.