Privacy Policy
Last updated 4 February 2026
RouteKey, Inc. ("RouteKey", "we") provides route optimization and dispatch software to delivery and field-service businesses. This policy explains what we collect, why, and what you can ask us to do about it. It covers this website and the RouteKey service, including the driver app.
1. Who we are
RouteKey, Inc. is a Delaware corporation with its principal place of business in Austin, Texas, United States. For privacy questions, contact privacy@routekey.io.
2. Two different relationships
We handle data in two distinct roles, and it matters which one applies:
- As a controller — for the people who contact us, evaluate the product, or administer a customer account. That's the data you give us directly.
- As a processor — for the operational data a customer runs through the service (stops, driver locations, proof of delivery). The customer decides what goes in; we act on their instructions.
3. What we collect
| Data | Why |
|---|---|
| Name, work email, company, fleet size, and anything you type into our demo form | To reply to you and to prepare a relevant demo. |
| Account details for administrators and drivers | To operate the service, issue API keys, and bill where applicable. |
| Operational data on a customer's behalf — stop addresses, driver GPS points, proof-of-delivery photos and signatures | To sequence routes, show live progress, and attach proof to the customer's orders. |
| Service logs — IP address, timestamp, request path, response status, bytes transferred, user agent | To run the service, investigate abuse, and diagnose faults. |
We do not run advertising, we do not sell or share personal information, and we do not build cross-site profiles. This site sets no cookies and loads no third-party scripts or fonts.
4. Driver and recipient data
Driver locations and proof-of-delivery captures belong to the customer who operates the fleet, and their own privacy notice governs how their drivers and recipients are informed. We collect location only while a driver is on an active shift, at the resolution needed for dispatch and ETAs, and we retain it on the schedule below unless a customer configures a shorter one.
5. Retention
- Service logs — 30 days, then deleted.
- Driver location traces — 90 days by default; configurable per customer.
- Proof of delivery — retained for the life of the customer account so it's available for disputes, then deleted on account closure.
- Demo enquiries — up to 24 months, so we remember prior conversations.
6. Subprocessors
We keep this list short on purpose.
| Provider | Purpose |
|---|---|
| Our cloud hosting provider (United States) | Runs the service and stores operational data and proof-of-delivery media. |
| Our mapping / geocoding provider | Turns addresses into coordinates and estimates drive times. |
| Our email provider | Delivers and receives correspondence. |
We'll tell affected customers before adding a subprocessor that handles their data.
7. Your rights
Depending on where you live, you may have the right to access, correct, delete, or port your personal information, to object to or restrict how we use it, and to withdraw consent. Texas residents have rights under the Texas Data Privacy and Security Act, and residents of other US states have comparable rights under their own laws — including the right not to be discriminated against for exercising them. Since we don't sell or share personal information, there is nothing to opt out of on that front.
Email privacy@routekey.io and we'll respond within 45 days. If a customer is the controller of the data, we'll pass your request to them and help them answer it.
8. Security
Traffic is encrypted in transit. Access to production is limited to the people who need it and is authenticated with hardware keys. We're a small team and we don't claim certifications we don't hold — if you need specifics for a vendor review, ask and we'll answer honestly. To report a vulnerability, see our security.txt.
9. Changes
If we change this policy materially we'll update the date above and, for anything that affects a live integration, tell account administrators directly.