Privacy Policy

RouteZen is a delivery route planning tool for Chennai. This draft describes the data this version handles. Who is responsible for that data (the "operator") depends on who deploys it; the operator must be named here before launch.

You enter locations, packages (reference, recipient name, address, weight, deadlines), vehicle profiles, plans, scenarios, delivery status events and workspace settings. Recipient names and addresses can be personal data. Enter only what you need to plan a delivery.

This version has no user accounts or sign-in. All data belongs to a single shared workspace in the backend database, so anyone who can reach a deployment can read and change that workspace. Do not expose it publicly with real customer data.

• Routing service (OSRM). The backend sends stop coordinates to the configured OSRM server to obtain road distances and geometry. The default public demo server is not meant for production or personal data.
• Map tiles. Your browser requests tiles from OpenStreetMap or Esri World Imagery, which can see your IP address and the map area you view.
• Fonts. Fonts may be fetched from Google Fonts at build time; check your deployment.

The app stores your light/dark theme choice in local storage. In demo mode it also keeps settings in local storage. See the Cookies and storage page.

RouteZen does not include advertising, analytics or tracking scripts and does not read a vehicle's GPS position. Tracking relies only on status events that people report manually.

Data stays in the database until someone deletes it using the app or database tools. There is no automatic retention schedule yet; the operator must define one. Optimisation run history is held in server memory and is lost on restart.

Rights depend on where you and the operator are located. The operator must publish a contact and process for access, correction and deletion requests before commercial launch (see Contact).

The current build has no authentication and is intended for development and evaluation. We make no claim of certification or audit. Production use requires access control, transport encryption and backups configured by the operator.

This draft will change as the product does. Material changes should be dated and announced once a version is published.