Privacy Policy

This policy explains how LocalDeliveryOS handles information submitted through this website - the Revenue Leakage Review request form and the Founding Fleet beta application. It describes what we collect today, why, and how to reach us about it.

The Revenue Leakage Review request form collects contact and business information you choose to provide: your name, business name, work email, and - optionally - phone number, company website, approximate driver count, current software, delivery volume, accounting platform, contact preferences, and a short description of what you'd like us to examine.

The Founding Fleet beta application collects your name, company, and work email, and - optionally - phone number, city and state, fleet size, current dispatch software, the kinds of deliveries you run, the biggest pain in your operation, how soon you could start, and how you heard about us.

Neither form collects delivery records, invoices, rate cards, payment information, or driver personal data. They are only for asking us to get in touch.

To respond to your request, understand whether a Revenue Leakage Review or the Founding Fleet beta is a good fit for your operation, and contact you about it. That's the purpose - we don't use form submissions for anything else, and we do not sell submitted information.

Revenue Leakage Review requests are sent to us as an email notification and are not stored in a LocalDeliveryOS database. Founding Fleet beta applications are stored in the LocalDeliveryOS leads database so we can review, score, and follow up on each application; access is limited to the LocalDeliveryOS platform team.

We use Resend, an email delivery service, to deliver notification and confirmation emails, so Resend processes submissions for that purpose. Notification emails, application records, and any correspondence that follows are retained as reasonably needed to respond to you and conduct ordinary business.

The LocalDeliveryOS application uses Sentry, an error-monitoring service, to capture unhandled errors so we can find and fix defects. When an error occurs, Sentry receives technical details about it - the error itself, the route or screen it happened on, browser or device basics, and limited account context: the company identifier and the user's role (for example, dispatcher or driver). Error payloads are scrubbed before sending so that passwords, tokens, cookies, and similar secrets are removed, and we do not send names, email addresses, phone numbers, or street addresses as error context.

The application uses Microsoft Clarity to record anonymized session replays - how screens are navigated - so we can improve the product. Clarity is configured to mask all text content by default, so replays do not show addresses, names, emails, phone numbers, prices, or free-text notes in the clear. Clarity does not run on driver-facing screens. Recordings are processed by Microsoft under Microsoft's own terms and retained per those terms. Clarity is only active when enabled for the deployment; the website forms described above work the same with or without it.

You can ask us what information we hold from your submission, ask us to correct it, or ask us to delete it. Email us at privacy@localdeliveryos.com and we'll respond as promptly as we reasonably can.

We take reasonable, proportionate steps to protect information in transit and in our systems — form submissions are validated server-side and transmitted over encrypted connections. No method of transmission or storage is perfectly secure, and we don't promise otherwise.

If our practices change, we'll update this page and its effective date. Material changes will be reflected here before they take effect.

Questions about this policy or your information: privacy@localdeliveryos.com.