Article · 7 min read

What happens to your customer data when you leave your dispatch provider?

The answer is in a clause almost nobody reads before signing.

By the Limozoft team · Last reviewed 2026-10-19

Operators don't outgrow their dispatch software. They outgrow the gaps around it — and then discover that leaving is harder than arriving. Your customer list, your trip history and your corporate contacts are the most valuable assets your business owns. Here is how to make sure they stay yours.

Key takeaways

Explicit clause: operator is data controller, vendor is processor
Self-serve export in CSV or JSON, at any time, at no charge
Forward reservations included with no date-range cap
Defined post-termination access window (30 days minimum)
Documented deletion and certificate of destruction
Booking engine on your domain, not the vendor's subdomain

The three ways data quietly stops being yours

Export caps. A UI that exports 12 months, or 1,000 rows, or excludes future bookings.
Format degradation. A PDF report is not a data export. Insist on machine-readable CSV or JSON with stable IDs.
The domain trap. Bookings taken on vendor-subdomain.com build the vendor's SEO and analytics. You cannot export a ranking.

What a good contract clause looks like

Plain language, no ambiguity: the Customer is and remains the controller of all Customer Data; the Provider will make available a complete, machine-readable export of all Customer Data on request and for at least 30 days following termination, at no additional cost; the Provider will permanently delete Customer Data within 60 days of termination and confirm deletion in writing.

Questions to ask in the demo

Show me the export screen right now.
Does the export include reservations dated 12 months from today?
Is there a fee for export after cancellation?
Is there a public API and are webhooks included on my plan?
Whose domain does the booking engine run on?
Which region is the data stored in, and can I choose it?

How Limozoft handles it

Full self-serve export of every object, any time, no fee, forward bookings included; REST API and webhooks on every plan; your booking engine on your own domain from day one. See the detail on our security page and the platform comparison on our compare hub.

Frequently asked questions

Who owns customer data in taxi dispatch software?+

You should — but only if your contract says so in writing. Check for an explicit clause stating the operator is the data controller and the vendor is a processor, with a defined export format and retention period after termination.

What data should you be able to export?+

Customers with contact details and consent status, all trips with fares, forward reservations, corporate accounts and rate cards, drivers, vehicles, invoices and payment records — in CSV or JSON, self-serve, at any time.

Can a dispatch vendor withhold your data?+

Some can slow-walk it after cancellation or charge an export fee. This is why you export before giving notice, and why a self-serve export API matters more than a promise in a sales call.

Does your booking engine domain affect data ownership?+

Yes. If bookings happen on the vendor's subdomain, the search traffic, analytics history and remarketing audiences accrue to them, not you — and none of it exports.