Last updated: July 2026
Enterprise & Multi-Site Terms
For operator groups running multiple sites, brands or fleets on Cabio. See also: standard Terms of Service
1. Who these terms are for
These Enterprise Terms apply to organisations licensing Cabio under an Enterprise or multi-site agreement — typically operators running more than one depot, brand, or licensing area on a single account, fleet groups, and organisations with procurement, security, or service-level requirements beyond our standard plans. They are agreed between Launchflow and the organisation named in the Order Form ("the Customer").
2. Relationship to our standard terms
These Enterprise Terms supplement our standard Terms of Service and our Privacy Policy & Data Processing Terms, which continue to apply in full. Where a term here conflicts with the standard Terms of Service, this document takes precedence for Enterprise customers. Where a signed Order Form or Master Services Agreement conflicts with either, the signed document takes precedence.
3. Scope of the licence
The Order Form sets out what the licence covers: the number of operating sites or tenants, the number of vehicles or active drivers, the number of administrative seats, the modules enabled, and any usage allowances for messaging, telephony, or mapping. The licence is granted to the named Customer and its subsidiaries listed in the Order Form. It may not be extended to a franchisee, a separately owned operator, or any other third party without our written agreement.
4. Multi-site and group accounts
Enterprise customers may run multiple sites as separate tenants under one agreement, each with its own branding, pricing, drivers, and data. Data is isolated between tenants by default. Where the Customer wants group-level reporting, shared driver pools, or cross-site dispatch, this is configured on request and the Customer is responsible for confirming that sharing data between its sites is lawful under its own licensing and data protection obligations.
5. Onboarding, migration and training
Where onboarding is included in the Order Form, it covers configuration of the platform, import of existing customer, driver, and pricing data supplied by the Customer in an agreed format, and remote training for administrators. The Customer is responsible for the accuracy and lawfulness of any data it provides for migration, and for verifying imported records before going live. Additional migration work, bespoke development, or on-site training is quoted separately.
6. Fees, invoicing and payment
Enterprise fees are set out in the Order Form and are exclusive of VAT. Unless agreed otherwise, we invoice monthly or annually in advance for the licence, and monthly in arrears for any usage-based charges. Invoices are itemised by site. Payment is due within 30 days of the invoice date by BACS or direct debit. Where the Customer requires a purchase order number on invoices, it must supply a valid PO before the billing period begins; the absence of a PO does not defer payment. VAT invoices are issued for every charge.
7. Late payment and suspension
Where an invoice remains unpaid after its due date we may charge statutory interest under the Late Payment of Commercial Debts (Interest) Act 1998. If an invoice remains unpaid 30 days after a written reminder, we may suspend access to the affected sites, having first given at least 10 working days' notice to a named contact so that the Customer can maintain continuity of service to its passengers. Suspension does not relieve the Customer of accrued charges.
8. Service levels
Where the Order Form includes a service level, we commit to a monthly uptime target for the core dispatch and booking functions, measured excluding planned maintenance notified in advance, emergencies, and failures of third-party services or of the Customer's own connectivity. Where we fall below the committed level in a month, the Customer's sole remedy is a service credit against the following invoice, calculated as set out in the Order Form. Service credits must be claimed within 30 days of the end of the affected month.
9. Support and escalation
Enterprise customers receive priority support with target response times set out in the Order Form, banded by severity — from a total loss of dispatch capability through to general questions and feature requests. Support is requested by email to hello@launchflow.co.uk or through the agreed channel, and each Enterprise account has a named escalation contact at Launchflow. The Customer must nominate its own authorised contacts who may raise and escalate tickets, and keep that list current.
10. Planned maintenance and change control
We deploy improvements continuously. Changes that affect how the platform behaves for administrators or drivers are notified in advance to the Customer's named contacts. We will not remove or materially reduce a function the Customer relies on without at least 30 days' notice. Where the Customer requires a change window that avoids specific peak periods — school runs, airport contracts, event nights — we will accommodate reasonable requests agreed in writing.
11. Data protection
For passenger and driver data, the Customer is the data controller and Launchflow is the processor. Our Article 28 processing terms, our sub-processor list, our security measures, and our breach-notification and deletion commitments are set out in Part C of our Privacy Policy & Data Processing Terms. Where the Customer's procurement requires a separately executed Data Processing Agreement, we will sign one on request. The Customer remains responsible for its own lawful basis, its passenger-facing privacy notice, and its retention decisions.
12. Security assurance and audit
On reasonable written request, and no more than once in any 12-month period unless a breach has occurred or a regulator requires it, we will provide the information reasonably needed to demonstrate our compliance with our processing obligations — including a description of our security measures, our sub-processor list, and the results of any security testing we have carried out, subject to confidentiality. Where the Customer requires an on-site or third-party audit, this is arranged by agreement, on reasonable notice, at the Customer's cost, and without disrupting other customers.
13. Business continuity
We maintain backups of Customer data and documented procedures for restoring service following an infrastructure failure. Recovery point and recovery time objectives, where committed, are stated in the Order Form. The Customer is responsible for its own operational continuity arrangements — including the ability to take bookings by telephone and dispatch manually — for the period of any outage.
14. Branding and white-label
Enterprise customers may apply their own brand, colours, logo, domain, and passenger-facing wording to booking pages, tracking pages, notifications, and, where included, to branded driver and passenger applications. The Customer warrants that it owns or is licensed to use the brand assets it supplies and indemnifies us against claims arising from them. Where we publish an application to the Apple App Store or Google Play on the Customer's behalf, the Customer is responsible for meeting those stores' policies and for the accuracy of its store listing.
15. Integrations and API access
Enterprise plans include API access for the Customer's own integrations. API keys are issued to the Customer and must be kept confidential; the Customer is responsible for all activity carried out with them. We may apply fair-use rate limits to protect platform stability, and will discuss higher limits where a legitimate integration requires them. We do not guarantee that a third-party integration the Customer builds will continue to work across platform changes, but we will give reasonable notice of breaking changes to documented API endpoints.
16. Term, renewal and termination
The initial term is set out in the Order Form and renews for successive periods of the same length unless either party gives written notice at least 60 days before the end of the current term. Either party may terminate for material breach that is not remedied within 30 days of written notice, or immediately on the other's insolvency. We may terminate immediately where the Customer operates without the licences required by our standard Terms of Service. Fees for the remainder of a committed term remain payable on termination by the Customer for convenience.
17. Exit assistance and return of data
On termination or expiry, we will provide the Customer with a complete export of its data in a machine-readable format at no charge, on request made within 30 days. Where the Order Form includes exit assistance, we will additionally support the Customer's transition for the agreed period at the agreed rate. We then delete or irreversibly anonymise the Customer's tenant data within 90 days, and purge it from backups within a further 90 days, except where retention is legally required.
18. Confidentiality and publicity
Each party will keep the other's confidential information secure and use it only for the purposes of the agreement. Neither party will name the other in a press release, case study, or marketing material without prior written consent, except that we may include the Customer's name and logo in a customer list where the Customer has agreed in the Order Form.
19. Liability
The limitations and exclusions in our standard Terms of Service apply, except that the aggregate liability cap for Enterprise customers is the amount stated in the Order Form, or if none is stated, the total fees paid in the 12 months before the event giving rise to the claim. Nothing limits liability for death or personal injury caused by negligence, for fraud, or for any other liability that cannot lawfully be limited.
20. Amendments
We may amend these Enterprise Terms on 60 days' written notice to the Customer's named contacts. Where an amendment materially and adversely affects the Customer, it may terminate the affected services without penalty by giving written notice before the amendment takes effect. Terms recorded in a signed Order Form or Master Services Agreement are varied only by written agreement between both parties.
21. Governing law
These Enterprise Terms are governed by the laws of England and Wales and are subject to the exclusive jurisdiction of the courts of England and Wales. Before commencing proceedings, both parties will attempt in good faith to resolve the dispute, escalating first to each party's named commercial contact.
22. Contact
Questions about Enterprise terms, procurement, security questionnaires, or a Data Processing Agreement should be directed to: Launchflow · 103A London Road, Grays, Essex, RM17 5YB · Email: hello@launchflow.co.uk · Web: cabio.cab.
Need a signed MSA, a Data Processing Agreement, or a security questionnaire completed?