Route Planner Teams — Terms of Service

Last Updated: October 23, 2026

These Terms of Service ("Terms") govern Route Planner Teams ("Teams" or the "Service"): the dispatcher website at courierrouteplanner.com/app, the Teams API and the team features of the Route Planner for Couriers mobile app. The Service is provided by Yevhen Tekhov, an individual (sole trader) based in the United Kingdom, trading as "Route Planner for Couriers" ("we", "us", "our").

By creating a team, subscribing to a paid plan or continuing to use Teams, the business you represent ("Customer", "you") agrees to these Terms, and you confirm that you are authorised to accept them on its behalf. If you do not agree, do not use Teams. Drivers who join a team use the mobile app under our app Terms of Use; these Terms apply to the Customer.

These Terms, our Refund Policy, our Privacy Policy and the Data Processing Terms in Schedule 1 below form the entire agreement between you and us about Teams.

1. Contact

Email: support@courierrouteplanner.com. Address: Abbotsfield, The Den, Wiveliscombe, TA4 2SU, United Kingdom. We send notices about your team to the email address of the team owner.

2. Business Use Only

Teams is a service for businesses (courier companies, delivery fleets, shops and other organisations that deliver goods). By using Teams you confirm that you act for a business and not as a consumer.

3. The Service and Your Accounts

Teams lets dispatchers load delivery stops, check addresses, split stops between drivers, optimise routes, send routes to drivers' phones and follow their progress, including proof of delivery. Through the API (section 9), your own systems can send orders to your team and receive updates about them.

A team has one owner and a number of team members set by its plan (currently up to 5, 10 or 15 people, counting the owner). Everyone in the team is a member and joins with the same invite link or team code; the owner can give any member the Dispatcher role (access to the dispatcher website and route planning) and take it away again, and any member — including the owner and dispatchers — can be assigned routes to drive in the mobile app. There is no separate limit on dispatchers. You decide who you invite. Keep invite links and team codes confidential, remove people who should no longer have access, and make sure that everyone you invite uses Teams in line with these Terms. You are responsible for activity in your team. Each membership is for one person: do not share one member's access between several people.

4. Free Trial, Plans and Allowances

A new team starts with a free trial (currently 5 days). To start the trial, you add a payment method at checkout; you are not charged during the trial. Unless you cancel before the trial ends, your subscription starts automatically at the end of the trial and the first payment is taken then. The free trial is available once per business; creating new teams to restart a trial is not allowed, and we may end such trials.

Plans differ by the number of team members (counting the owner) and the monthly allowances of stops and route optimisations. Automatic splitting of a day's stops into several routes ("Split into routes") is included in the plans for 10 and 15 team members; each route produced by a split counts as one route optimisation. Plans also include fair-use limits on address lookups from files and lists and on label scans that protect the Service from automated abuse; normal use stays well within them. When an allowance is reached, adding new stops (or running further optimisations) pauses until the next monthly reset or until you move to a larger plan; routes that drivers have already started can always be completed. Current plans and prices are shown on our pricing page and at checkout.

5. Prices and Payment

Our order process is conducted by our online reseller Paddle.com. Paddle.com is the Merchant of Record for all our orders. Paddle handles payments, invoices, taxes and refunds; for anything else about Teams, contact us.

Subscriptions are billed monthly in advance and renew automatically until cancelled. Applicable taxes (such as VAT or sales tax) are calculated and added by Paddle at checkout. Paddle's Buyer Terms apply to your purchase.

You can cancel at any time in the Subscription section of the dispatcher website or through Paddle. Cancellation takes effect at the end of the current billing period, and the team keeps its paid features until then; fees for the current period are not prorated. Refunds are described in our Refund Policy.

We will tell you about any price change at least 30 days before it applies to your next renewal. You will always see the final price before you pay.

6. End of Trial and Unpaid Subscriptions

If you cancel during the trial, the team's paid features stop when the trial ends. If a payment fails (including the first payment after the trial), the team has a 3-day grace period. In both cases, until payment is made: drivers can finish routes they have already started (marks, photos and finish); no new team routes can be created or sent; and dispatchers can only pay for the subscription or request deletion of the team. Team data is kept for 30 days and then deleted. If you pay within those 30 days, the team continues as before.

7. Your Data and Your Drivers

Your data. Everything your team adds to Teams — stops, addresses, recipient names and phone numbers, notes, routes and proof of delivery — is your data ("Customer Data"). You give us permission to host and process Customer Data only to provide and support the Service. We do not sell Customer Data and do not use it for advertising.

Service statistics. We may use aggregated, de-identified information about how the Service is used (for example, the number of routes or how long optimisations take), which does not identify you, your drivers or recipients, to operate and improve the Service.

Roles. For Customer Data you are the controller and we are your processor (a "service provider" under US state privacy laws). Schedule 1 sets out how we process it. You are responsible for having a lawful basis to give us recipients' data and for the accuracy of what you upload.

What dispatchers see about drivers. On team routes, the app records the time and location of a driver's route events — starting a route, marking a stop as delivered or failed, capturing proof of delivery and finishing a route — and shows them to the team's dispatchers. While a team route that the driver has started is running, the app also shares the driver's live position: the team's owner and dispatchers see the driver's latest position (with its accuracy and direction of travel) on the map of the dispatcher website, updated about every 30–60 seconds while the driver is moving, including when the app is in the background. Live position sharing is part of team routes: there is no setting to turn it off, either in the app or on the dispatcher website. It lasts only until the team route that the driver has started is finished, and it stops when the route is finished, when the driver leaves or is removed from the team, or when the driver uses “Delete my data”. Only the latest position is kept, with no history of movements; it is deleted when sharing stops, and otherwise expires 12 hours after its last update. If a driver revokes the app's location permission in their phone's settings, the app stops receiving their position and the map no longer updates it. Positions are never shared during a driver's personal routes or when no team route is running, and a driver's personal routes outside the team are never visible to the team.

Notices to drivers. Whether your drivers are employees or contractors, you must tell them how Teams is used and give any notices and obtain any consents that the law of the place where they work requires, including workplace-surveillance and electronic-monitoring rules (for example, written policies or advance notice of location monitoring that some states, provinces and countries require). This includes live position sharing during team routes, which drivers cannot turn off in the app. You are responsible for telling your drivers about it before they drive team routes and for having a lawful basis for it under the law that applies to you, and, where the law requires it — for example, the electronic-monitoring notice laws of New York, Connecticut and Delaware, or the transparency duties and, where appropriate, a data protection impact assessment under the UK GDPR and the EU GDPR — for giving that notice and carrying out that assessment. Our Privacy Policy tells drivers to send questions about this monitoring to you, as the controller, and you are responsible for answering them. The app shows drivers a short notice when they join a team, including about live position sharing during team routes; this does not replace your own obligations.

Data you must not upload. Do not upload health information (including protected health information under HIPAA), payment card numbers, government identification numbers or other special categories of personal data. Teams is not designed for such data, we are not a HIPAA business associate, and we do not sign business associate agreements.

8. Acceptable Use

You must not, and must not allow anyone in your team to: use the Service for any unlawful purpose; commit fraud or send spam; infringe anyone's intellectual property or privacy rights; interfere with the security of the Service (including malware, probing, scanning, scraping or circumventing limits); access the Service by automated means other than its own features and the API described in section 9; overload or disrupt the Service; or resell or provide the Service to third parties without our written consent.

You may not use the Service if you, or the business you represent, are subject to UK, EU, UN or US sanctions, or are located in a country or region subject to comprehensive sanctions.

9. API and Integrations

Teams includes an application programming interface (the "API") that lets your own systems send orders to your team and receive updates about them, including through Zapier and similar automation platforms. The API, its limits and its webhooks are described at courierrouteplanner.com/teams/api.

API keys. API keys are confidential credentials: anyone who has one of your keys can act as your team through the API, and their activity is activity in your team. You are responsible for keeping your keys secret, for giving them only to systems that need them, and for revoking a key as soon as you suspect that it has been exposed.

Your systems and data. You are responsible for the systems and third-party services you connect to Teams (including Zapier and similar automation platforms, which are provided under their own terms) and for the data you send through the API. When you set up a webhook, you instruct us to send the information described in the API documentation to the address you choose. Data sent through the API is Customer Data and is processed under Schedule 1 like other team data.

Limits and suspension. We apply rate limits and usage limits to the API. We may suspend or revoke API keys and webhooks that cause abuse, a security risk or excessive load on the Service.

Webhooks. Webhook deliveries are made on a best-effort basis, with retries. We do not guarantee that every delivery arrives, or that deliveries arrive in a particular order or within a particular time; use the API to check the current status of orders.

Beta. The API is currently in beta. We may change it, and where practical we will give reasonable notice of changes that affect existing integrations.

10. Intellectual Property

We own the Service, the app, the website and all related software, content and intellectual property. These Terms give you a non-exclusive, non-transferable right to use the Service during your subscription; they do not transfer any ownership. If you send us feedback, we may use it without obligation to you.

11. Maps, Routes and Safety

Routes, arrival times and addresses come from map and optimisation providers and depend on real-world conditions (traffic, road works, signage, address quality). They are advisory only. Drivers remain responsible for driving safely and lawfully, and must not interact with the app while driving.

12. Availability and Changes

We work to keep Teams available and reliable, but we do not guarantee that the Service will be uninterrupted or error-free. We may carry out maintenance and may change, add or remove features. We will not materially reduce the core features of your plan during a period you have already paid for.

13. Suspension and Termination

We may suspend or terminate a team for material breach of these Terms, non-payment, a security or fraud risk, or repeated or serious violations, or where the law requires it. Where the law and circumstances allow, we will notify the team owner first and give an opportunity to fix the problem.

You can stop using Teams at any time and ask us to delete your team by emailing us from the team owner's email address. When a team is deleted or terminated, Customer Data is deleted within 30 days, as described in Schedule 1.

14. Limitation of Liability

To the maximum extent permitted by law: the Service is provided "as is" and "as available", and we exclude all implied warranties and conditions; we are not liable for any indirect, incidental, special or consequential loss, or for loss of profits, revenue, business, goodwill or data; and our total liability arising out of or in connection with these Terms in any 12-month period is limited to the greater of the fees you paid us for Teams in the 12 months before the event giving rise to the claim and USD 100.

Nothing in these Terms limits or excludes liability that cannot be limited or excluded by law, such as liability for death or personal injury caused by negligence, or for fraud.

15. Your Responsibility for Claims

You will compensate us for losses and reasonable costs arising from third-party claims (including claims by your drivers, recipients or authorities) caused by Customer Data you uploaded without a lawful basis, by your failure to give drivers the notices described in section 7, or by your team's breach of section 8.

16. Changes to These Terms

We may update these Terms. We will email the team owner about material changes at least 30 days before they take effect. If you continue to use Teams after that date, the updated Terms apply; if you do not agree, you can cancel before then.

17. General

We may transfer our rights and obligations under these Terms to a company that takes over the Service (for example, a company we form to run it); we will tell you if this happens, and your rights will not be reduced. If any provision is found unenforceable, the rest remains in effect. Failure to enforce a provision is not a waiver. Neither party is liable for delays caused by events beyond its reasonable control.

18. Governing Law

These Terms and any dispute arising from them are governed by the laws of England and Wales. The courts of England and Wales have exclusive jurisdiction.

Schedule 1 — Data Processing Terms

This Schedule applies when we process personal data in Customer Data on your behalf. It is intended to meet Article 28 of the UK GDPR and, where it applies, the EU GDPR, as well as the service-provider requirements of US state privacy laws (such as the California Consumer Privacy Act).

1. Details of the processing

• Subject matter and purpose: providing Teams — storing, searching and geocoding addresses, optimising and sending routes, showing route progress, proof of delivery and drivers' live position during team routes to your team.
• Duration: the life of your team, plus the deletion period in point 9.
• Categories of data subjects: delivery recipients; your team members (drivers and dispatchers).
• Types of personal data: recipient names, delivery addresses and coordinates, phone numbers and notes; proof of delivery (photos, signatures, barcode values, ID-check confirmations, notes); driver display names; the time and location of drivers' route events; drivers' live position during team routes they have started (latest position only, with accuracy, direction and speed); dispatcher names and email addresses.
• Special categories: none are intended (see section 7 of the Terms).

2. Instructions

We process personal data only on your documented instructions, which are these Terms and your use of the Service, unless the law requires otherwise (in which case we will tell you, unless the law forbids it). We will tell you if we believe an instruction infringes data protection law.

3. Confidentiality

Anyone we authorise to process personal data is bound by confidentiality.

4. Security

We maintain appropriate technical and organisational measures, including encryption in transit and at rest, per-team access isolation enforced on our servers, least-privilege access, and masking of personal data in technical logs.

5. Sub-processors

You authorise us to use the sub-processors listed in our Privacy Policy (hosting and database, maps, geocoding and route optimisation, text recognition, and payments). We impose data protection obligations on them that are no less protective than this Schedule. We will announce new sub-processors at least 14 days in advance by updating the Privacy Policy and emailing the team owner. You may object on reasonable data protection grounds; if we cannot address the objection, you may stop using the Service and cancel your subscription.

6. International transfers

Personal data may be processed outside the UK and the EEA, including in the United States. Where required, we rely on adequacy regulations (including the UK–US data bridge), the UK International Data Transfer Agreement or Addendum, or the EU Standard Contractual Clauses.

7. Assistance

Taking into account the nature of the processing, we will help you respond to requests from data subjects and meet your obligations on security, breach notification and data protection impact assessments. If we receive a request about Customer Data directly, we will pass it to you.

8. Personal data breaches

We will notify the team owner without undue delay, and in any event within 48 hours, after becoming aware of a personal data breach affecting Customer Data, with the information available to us at the time.

9. Deletion

When your team is deleted or terminated, we delete Customer Data within 30 days, unless the law requires us to keep it. Proof-of-delivery files are deleted together with the team.

10. Demonstrating compliance

We will provide the information reasonably necessary to demonstrate compliance with this Schedule, including answers to reasonable written questionnaires, and will allow audits by you or an auditor you appoint on reasonable written notice, no more than once a year (unless required by a regulator or after a breach), at your cost.

11. US state privacy laws

We will not sell or share personal information in Customer Data, will not retain, use or disclose it for any purpose other than providing the Service, will not combine it with personal information from other sources except as permitted by law, and will comply with the obligations of a service provider under applicable US state privacy laws.