Routerra LogoTeams

ROUTERRA TEAMS — TERMS OF SERVICE

Last updated: August 17, 2026

These terms are the agreement between your business and Routerra for the use of Routerra Teams. Please read section 9 in particular: our Data Processing Agreement forms part of this agreement and is concluded when you accept these terms.

In these terms, “Routerra”, “we” and “us” mean the entity identified in section 1. “Customer” and “you” mean the business that subscribes to Routerra Teams. “Customer Data” means everything you or your team members and drivers upload to, or generate in, Routerra Teams.

1. Who we are and what this covers

Routerra Teams is operated by:

Routerra Anatolii Trubin (sole proprietorship registered in Poland)
ul. Na Zjeździe 11, lok. 5p, 30-527 Kraków, Poland
NIP 6793319069 · REGON 540576549
info@routerra.io

These terms govern your use of Routerra Teams in all of its parts: the Teams dashboard at teams.routerra.io, the Routerra Teams driver app for iOS and Android, and any Teams APIs, webhooks and integrations we make available to you.

Routerra Teams is a business-to-business service and this is a business-to-business agreement. You confirm that you are subscribing in the course of your business, trade or profession. Consumer protection rules therefore do not apply to this agreement — including the 14-day right of withdrawal for distance contracts. If you are an individual using our consumer route planner rather than Routerra Teams, your agreement with us is the separate Terms and Conditions, which do carry those consumer rights.

2. Accounts, teams and drivers

You create a team, and the team is the unit that everything else attaches to: members, drivers, depots, routes and the subscription. Accounts are created and authenticated through our authentication provider; you must give accurate account details and keep your credentials secure.

You add members by sending an email invitation, and each invitation carries the role that member will hold in the team. Roles and permissions inside your team are yours to set and to review — we do not manage them for you. You add drivers to your roster with the details the product needs to plan their work: name, email address, vehicle type and capacity, shift times, depot and routing preferences.

You are responsible for the use your team makes of the service. That includes everything done by your members, administrators and drivers through their accounts, whether or not you authorised it, and it includes removing members and drivers who should no longer have access. Acts and omissions of your members and drivers are treated as your own for the purposes of these terms.

3. Subscription, trial and billing

Subscriptions are per team. Each team carries one subscription, billed monthly or annually.

You are billed per driver seat — one seat for each driver who receives routes in the driver app. You choose how many seats your team has and you can change that number as your fleet changes; the amount you pay is the number of seats multiplied by the per-seat price for your billing period, so adding or removing seats changes the amount billed. Current prices are on our pricing page. So that our internal naming cannot be read as a second, different billing unit: the seat count you choose is stored on your subscription under the name vehicle limit and is sent to the checkout as the line-item quantity. Those are three names for one number — the number of driver seats you bought. Nothing in this agreement bills you by vehicle, by van, by route or by stop.

Free trial. New teams get a 7-day free trial. The trial requires a payment card: you add a card when you sign up, and if you do not cancel before the trial ends, the subscription continues and is charged. Cancel before the trial ends and you are not charged.

Lemon Squeezy is the merchant of record for web purchases of Routerra Teams. That means the sale to you is made through Lemon Squeezy: theirs is the checkout, theirs is the payment processing, theirs is the handling of sales tax and VAT, and theirs is the handling of refunds under their own terms. We never receive or store your card number. Their terms apply to the payment transaction alongside these terms; these terms govern your use of the service itself.

Renewal and cancellation. Subscriptions renew automatically for successive periods until they are cancelled. You cancel, change your plan or update your payment method through the billing portal, which we open for you from the dashboard and which is operated by Lemon Squeezy. Cancellation takes effect at the end of the period you have already paid for; fees already paid are not refunded on a pro-rata basis except where these terms or the law say otherwise.

4. Customer data and your responsibilities as controller

You decide what goes into Routerra Teams. We do not select it, we do not require any particular field, and we process it on your instructions. Under the GDPR you are the controller of the personal data in your team — recipient names, addresses, coordinates, delivery notes and time windows, your driver roster, proof-of-delivery photos, your team audit log, and any driver position data if you enable live tracking (section 5). We are your processor for all of it. We are a controller only for the sign-in accounts of your administrators and drivers, billing, our product telemetry (including crash and error diagnostics from our own apps), our support communications with you, and security and abuse handling. Section 9 and the Data Processing Agreement set out what that split means in practice; section 2 of the Data Processing Agreement is the definitive list.

You warrant that you have a lawful basis under the GDPR, and any other applicable law, for the personal data you put into the service — both the personal data of your own customers and recipients (names, addresses, phone numbers, delivery notes) and the personal data of your drivers and staff. You warrant that you have the right to disclose that data to us and to have us process it for you.

You are responsible for giving those people the information the GDPR requires under Articles 13 and 14, and for handling their requests to exercise their rights. We assist you with those requests on the terms of the Data Processing Agreement, but the notice is yours to give: only you know why you hold the data, on what basis and for how long you keep it in your own systems.

We publish a Driver Privacy Notice describing what happens to driver data inside Routerra Teams, so that your drivers can see it and so that you can point to it. It is offered as help, and it is not a substitute for your own notice to your drivers — that notice is a controller obligation and an employment matter, and it can only come from you as their employer.

5. Live driver tracking

Live driver tracking is an optional feature. It is off by default, and it applies only if and when it has been enabled for your team at your decision. Where it has not been enabled, no driver position data is collected at all, and the rest of this section does not apply to you.

How it works where it is enabled. The driver app does not stream GPS. When a driver taps Navigate for a stop, the app hands off to Google Maps or Waze through Google Navigation Connect. Google then publishes the progress of that navigation trip to us, and we record position, ETA and remaining distance while the driver is navigating to a stop — not continuously through the day. Dispatchers in your team can see the latest position per driver and the trail for a route. The position points we record are deleted after 90 days.

The driver’s controls sit with Google. Navigation Connect takes the driver through Google’s own consent screen, shows a tracking indicator in Google Maps while a trip is being shared, and lets the driver switch the sharing off there. We do not build a competing control that would override Google’s.

The decision is yours, and so is the legal basis. Monitoring the location of employees or contractors is a decision only you as the employer can make. You are responsible for the employment-law basis for it, for any consultation with employee representatives or works councils that your jurisdiction requires, for telling your drivers, and for carrying out a data protection impact assessment where the GDPR requires one — location monitoring of workers commonly does. We provide the feature, the technical description and the transparency material; we do not decide whether you may monitor your drivers, and enabling the feature is your instruction to us as your processor.

6. Third-party integrations you configure

SMS notifications run on your own Twilio account. You supply your Twilio account SID and auth token; we store them encrypted and use them only to send messages on your behalf, at your instruction. The consequence matters legally: Twilio is your processor, under your own contract with Twilio — not a Routerra sub-processor. Your Twilio charges, Twilio’s terms, and the data protection arrangements between you and Twilio are yours. For that reason Twilio does not appear on our sub-processor list, and its absence there is deliberate rather than an omission. Because the Twilio account is yours, so is the control over our access to it: you can revoke our ability to send at any time by rotating or deleting the auth token in your own Twilio account, which takes effect immediately and does not depend on us.

The same framing applies to any other integration you configure with your own credentials or your own endpoints, including outbound webhooks to systems you operate. Where you direct data out of Routerra Teams to a destination you choose, you are responsible for that destination, for the lawful basis of sending data to it, and for any contract needed with its provider.

7. Acceptable use

You agree not to:

8. Intellectual property

We keep ours. Routerra retains all rights, title and interest in the Routerra Teams service — the software, the dashboard, the driver app, the APIs, the documentation, the underlying models and the Routerra name and marks. These terms grant you a limited, non-exclusive, non-transferable right to use the service during your subscription, and nothing more.

You keep yours. You retain all rights in Customer Data. You grant us a worldwide, non-exclusive, royalty-free licence to host, store, transmit, process and display Customer Data solely to provide, secure and support the service for you — and, for personal data, only within the scope of the Data Processing Agreement. We do not sell Customer Data, we do not use it for advertising, and we do not use it to train our own models. Where a sub-processor helps parse the files you import, it does so under API terms that exclude the use of that content for model training.

9. Data protection

Our Data Processing Agreement forms part of these terms and is concluded when you accept them. By accepting these terms — by creating a team or by using Routerra Teams — you enter into that Data Processing Agreement with us in the version published at /teams/dpa at that time, as amended from time to time in accordance with section 14, in satisfaction of Article 28(3) GDPR. It is not an optional add-on, it does not need a separate signature, and it is not negotiated separately from these terms. If your organisation requires a signed copy for its records, we will provide one on request to info@routerra.io — that copy records the same terms; requesting it does not change them and is not a precondition of the agreement being in force.

Roles. As set out in section 4, you are the controller of the personal data in your team and we are your processor. We are a controller for the sign-in accounts of your administrators and drivers, for billing, for our product telemetry, for our support communications with you, and for security and abuse handling — section 2 of the Data Processing Agreement lists them in full; our Privacy Policy covers that part.

Sub-processors and transfers. The sub-processors we use are listed at /subprocessors, and changes to that list are published there. Routerra is established in Poland, so a customer in the EEA sending personal data to us is making an intra-EEA transfer. The transfers that need a transfer mechanism are ours onward to sub-processors outside the EEA — above all our hosting in AWS us-east-1 — and those run on the EU Standard Contractual Clauses in the relevant module, and on the EU-U.S. Data Privacy Framework where the vendor holds a current certification. The Data Processing Agreement sets this out in full, and adds the UK International Data Transfer Addendum for UK customers.

Security. The technical and organisational measures we apply are described on our Security page, which is referenced by the Data Processing Agreement.

10. Confidentiality

Each party may receive information from the other that is marked as confidential or that a reasonable person would understand to be confidential — including pricing, roadmaps, security details and non-public business information. Each party will keep the other’s confidential information confidential, use it only to perform this agreement, protect it with at least reasonable care, and disclose it only to those of its people and advisers who need it and who are bound by equivalent obligations.

These obligations do not apply to information that is or becomes public without a breach of this section, was already known to the recipient without a duty of confidence, is independently developed without use of the other party’s information, or is lawfully received from a third party. Either party may disclose confidential information where the law or a competent authority requires it, giving the other party notice where it is lawfully able to do so. These obligations continue for three years after this agreement ends; Customer Data is protected for as long as we hold it, on the terms of the Data Processing Agreement rather than this section.

11. Warranties and disclaimers

We will provide Routerra Teams with reasonable skill and care, and we will not knowingly introduce malicious code into the service.

Beyond that, and to the fullest extent the law permits, the service is provided as is and we exclude all other warranties, conditions and representations, whether express or implied, including implied warranties of merchantability, fitness for a particular purpose and non-infringement. In particular, we do not warrant that route optimisation, ETAs, distances, travel times, geocoded addresses or traffic data are accurate, complete, error-free or uninterrupted. They rest in part on third-party map, routing and traffic data and on real-world conditions that we do not control, and they are estimates and suggestions, not instructions.

The driver remains responsible for lawful and safe driving at all times. A route we suggest never overrides road signs, traffic law, vehicle restrictions, working-time and rest rules, or the driver’s own judgement about whether a road is safe or passable. Drivers must not operate the app while the vehicle is moving.

We do not warrant the accuracy of Customer Data. Where a route is wrong because the address you uploaded was wrong, that is your data, not our defect.

12. Limitation of liability

Nothing in these terms excludes or limits liability that cannot lawfully be excluded or limited — including liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, for wilful misconduct, and for anything else that Polish law does not permit a party to exclude. Nothing here limits a data subject’s rights or either party’s liability to a data subject under Article 82 GDPR.

Subject to that, neither party is liable to the other for indirect, incidental, special, punitive or consequential loss, or for loss of profit, loss of revenue, loss of anticipated savings, loss of business or goodwill, or loss or corruption of data — in each case however caused, and whether or not the loss was foreseeable.

Subject to the first paragraph of this section, our total aggregate liability to you arising out of or in connection with this agreement is limited to the total fees you paid for Routerra Teams in the twelve months before the event giving rise to the claim.

That cap protects us and does not limit your liability for the following, which sit outside it: fees due to us; breach of the warranties you give in section 4 about your lawful basis for the personal data you put into the service; and breach of the acceptable use terms in section 7. Those are the obligations on which our exposure to third parties depends, so a cap measured by what you have paid us would be no protection at all.

13. Suspension and termination

You may terminate at any time by cancelling your subscription in the billing portal; the cancellation takes effect at the end of the period you have paid for.

We may suspend or terminate your access if you fail to pay a due amount and have not paid it within 14 days of our reminder; if you materially breach these terms and have not cured the breach within 30 days of our notice; or immediately, and for as long as necessary, where your use threatens the security, integrity or lawfulness of the service or of other customers’ data. Where we suspend rather than terminate, we restore access once the cause is resolved. We may also terminate for convenience on 30 days’ notice, refunding prepaid fees for the unused remainder of the term.

What happens to your data. On termination your access to the service ends. What we then do with Customer Data is governed by the deletion terms of the Data Processing Agreement: for 30 days we keep your Customer Data rather than deleting it, so that you can ask us to return it or to delete it even though you can no longer log in; we then delete it on your instruction, or within 90 days if you give none, subject to the residual-copy handling set out there and to any retention the law requires of us — billing records in particular are kept for the period Polish accounting law prescribes. Deleting a team in the product removes that team’s data; what that removal covers for the team audit log, and what it means for the record of the deletion itself, is set out in section 11 of the Data Processing Agreement — these terms deliberately do not restate it, so that there is only one description of it to keep current.

What you can take with you before then. While you still have access, the product lets you download an individual route as a CSV, XLSX or PDF file. There is no bulk export of a whole team, and no export of your address book, your driver roster or your audit log — so if you need more than individual routes, do not plan around exporting it yourself: ask us to return it under the Data Processing Agreement, which is an obligation we owe you rather than a favour.

14. Changes to the service and to these terms

We develop Routerra Teams continuously and may add, change or remove features. We will not make a change that materially degrades the core functionality of the service during a period you have already paid for.

We may change these terms, and the Data Processing Agreement that forms part of them. For a material change we will give you at least 30 days’ notice before it takes effect, by email to your team administrators or by notice in the dashboard. Continuing to use Routerra Teams after the effective date means you accept the change; if you do not accept it, you may terminate before that date and we will refund prepaid fees for the unused remainder of your term. Non-material changes — clarifications, corrections, contact details — take effect when published, and the date at the top of this page changes with them. Changes to our sub-processors are published on the sub-processor page and follow the objection process in the Data Processing Agreement.

Entire agreement. These terms, together with the Data Processing Agreement that section 9 makes part of them, are the entire agreement between you and us for Routerra Teams, and they replace any earlier proposal, quotation, presentation or discussion on the same subject. Terms you put forward in a purchase order or your own supplier paperwork do not apply unless we have agreed to them in writing.

Severability. If any provision of these terms is found to be invalid or unenforceable, it is limited or removed to the minimum extent necessary and the rest of these terms stay in full effect.

Assignment. We may assign this agreement as part of a merger, acquisition or sale of assets; you may not assign it without our written consent, which we will not unreasonably withhold.

15. Governing law and jurisdiction

These terms, and any dispute or claim arising out of or in connection with them or their subject matter, are governed by Polish law, excluding its conflict-of-law rules and excluding the United Nations Convention on Contracts for the International Sale of Goods. The courts competent for Kraków, Poland have exclusive jurisdiction.

This choice of law and forum is effective here precisely because both parties are businesses. The mandatory consumer rules that would otherwise let a customer sue in their own country, and that override a forum clause in a consumer contract, do not apply to a business-to-business agreement (see section 1). Before going to court we would rather talk: contact us and we will make a genuine effort to resolve the matter amicably.

16. Contact

Questions about these terms, requests for a signed copy of the Data Processing Agreement, and anything else about Routerra Teams:

info@routerra.io
Routerra Anatolii Trubin, ul. Na Zjeździe 11, lok. 5p, 30-527 Kraków, Poland

Related documents: Data Processing Agreement, Security, Driver Privacy Notice, Sub-processors, Privacy Policy.