Skip to content

Terms of Service

Latest version

Published on 28 October 2026.

1. Who we are and what this covers

These terms govern your use of Patrol Dispatch. They are an agreement between LeanCode sp. z o.o., Wrobla 8A, 02-736 Warszawa, Polska, KRS 0000638275 ("LeanCode", "we") and the organization that accepts them ("Customer", "you"). The person accepting confirms they may bind that organization.

Patrol Dispatch ("the Service") is a hosted service that runs an AI agent against your Flutter repositories. Depending on the mode you enable, the agent explores your app, writes or fixes Patrol end-to-end tests, triages failures, and reports back through comments, labels and pull requests on GitHub. It includes the dashboard at app.patroldispatch.ai, the API at api.patroldispatch.ai, the GitHub App and the command-line clients.

The Service is at an early stage. Features, limits and prices may change, and some parts may be removed. Patrol, the open-source framework, stays under its own license and is not covered here.

2. Accounts and repositories

You need a dashboard account and the Patrol Dispatch GitHub App installed on the repositories you want it to work on. Installing the App alone does nothing: the Service acts only on repositories you register in the dashboard, and you can unregister one at any time.

  • You keep your credentials and API tokens secret and tell us at security@leancode.pl if one leaks.
  • You are responsible for what members of your organization do in the Service.
  • You only register repositories you are authorized to let a third party read and change.
  • The GitHub App's permissions are listed on its installation page. The agent itself never holds a GitHub credential that can write; changes reach your repository only as branches and pull requests the Service opens.

3. Your code and data

To do its work the Service clones your registered repositories into isolated workers we operate, builds and runs your app there, and sends parts of your code to an AI model provider. You remain the owner of all of it, and we use it only to provide the Service to you.

What we process:

  • Source code and repository content of registered repositories, read from GitHub for each run and discarded when the worker exits.
  • Run records: the timeline of what the agent did, test results, screenshots and screen recordings, costs.
  • Account data: names, emails and GitHub identities of your members.

What we do not do:

  • Train or fine-tune any model on your code or data, or let our providers do so.
  • Share your code or run records with other customers.
  • Read your code for any purpose other than running, supporting or debugging your runs. A LeanCode engineer looks at a run's records only to fix a problem with it.

Subprocessors: the current list, with what each receives and where, is on the Subprocessors page of the dashboard. We email the owners of your organization at least 30 days before we add or replace one. If you object on reasonable data protection grounds, you can end the agreement under section 9 before the change applies. Changing the list does not change these terms. On the date of this version the list is:

ProviderWhat forWhat it receivesRegion
Google CloudHosting, workers, storageEverything the Service processesEU
AnthropicAI model the agent runs onCode and app screens the agent readsUS
emulator.wtfCloud Android emulators the tests run onYour app build and its testsEU
TypeSafe AIDeciding whether an issue or failure needs a runIssue, PR and failure textUS
WorkOSDashboard sign-inMembers' names and emailsUS

4. What the agent produces

Everything the agent produces for you (tests, code changes, bug reports, recordings) belongs to you once delivered, and we assign to you any rights we have in it. We keep the rights to the Service itself, its prompts and its software.

The agent is an AI system and can be wrong. It can write a test that passes for the wrong reason, miss a bug, or report one that is not there. You review every pull request before merging it; the Service never merges on its own. A passing Dispatch run is not a guarantee that your app works or is ready to release.

5. Acceptable use

You may not:

  • Register a repository you have no right to share with us, or one whose content is unlawful.
  • Try to get the agent or a worker to reach systems other than your own app and its test backends, or to escape the worker's sandbox.
  • Probe, overload or reverse-engineer the Service, or test its security without our written agreement.
  • Resell the Service or use it to build a competing product.

We may suspend a run, a repository or an account that breaks these rules or puts the Service or other customers at risk, and we tell you why when we do.

6. Fees

A new organization starts with a free trial of one month, with no payment details required. Before it ends we contact you to agree a plan; nothing is charged unless you agree to one. If you don't, we stop your runs at the end of the trial and delete your data as section 9 describes.

The Service is billed by subscription at the plan and price published at pricing page or agreed with us in writing, invoiced monthly in advance and payable within 14 days, plus VAT where it applies. Each plan includes a number of credits a month; a run consumes credits according to the rates shown in the dashboard, and unused credits do not roll over.

We tell you about a price change at least 30 days before it applies to you, and never charge you for anything you did not agree to.

7. Confidentiality and feedback

Each side keeps the other's non-public information confidential, uses it only for this agreement, and protects it at least as carefully as its own. Your code and run records are always your confidential information. This survives the end of the agreement for as long as the information remains confidential.

Feedback you give us we may use freely to improve the Service, without naming you. We mention you as a customer publicly only with your written consent.

8. Warranties and liability

The Service is provided "as is", with no uptime commitment and no warranty that it is error-free or fit for a particular purpose, to the extent the law allows. We do our best to keep it running and to tell you about incidents affecting your data within 72 hours.

Neither side is liable for indirect or consequential loss, lost profits or lost data. Each side's total liability under these terms is capped at the fees you paid in the 12 months before the claim, or EUR 1,000 if that is more, which also covers the free trial. The caps do not apply to breach of confidentiality, your payment obligations, or liability the law does not allow to be limited, such as for wilful misconduct.

9. Term and termination

These terms run from acceptance until either side ends them. You can stop at any time by unregistering your repositories, uninstalling the GitHub App, and telling us; fees already paid for the current month are not refunded. We can end the agreement with 30 days' notice, or at once if you materially breach these terms.

Within 30 days of the end, we delete your run records and account data, except what the law requires us to keep, such as invoices. Pull requests and comments already on GitHub stay in your repositories. Sections 3, 4, 7, 8, 10 and 11 survive the end.

10. Law and contact

Polish law governs these terms, and the courts of Warsaw have jurisdiction, without limiting any consumer protections that apply.

Questions: patrol@leancode.pl. Security reports: security@leancode.pl.

11. Changes to these terms

Each version of these terms has a publication date. The current version and every earlier one are in the dashboard. We record which version your organization accepted, when, and which member accepted it.

A change is one of three kinds:

  1. Changes that apply on publication. Corrections of wording or formatting that do not change meaning, updates to our contact details or to the description of features, and changes required by law, a court or a regulator, or needed to fix a security issue, to the extent so required. We announce them in the dashboard.
  2. Changes we notify you of. Any change not listed in point 3, including new features, new usage limits and price changes under section 6. We email the owners of your organization at least 30 days before the change takes effect, and continued use after that date means acceptance. If you object, you can end the agreement under section 9 before the change applies, and we refund fees you paid for the period after it.
  3. Changes that need your explicit acceptance. A change that:
    • lets us or our providers use your code or run records for anything beyond providing the Service to you, including training a model;
    • widens when a LeanCode engineer may access your code or run records beyond what section 3 allows;
    • lowers our liability cap or widens what you are liable for;
    • narrows your rights in what the agent produces under section 4;
    • adds a fee or charge you have not agreed to;
    • changes the governing law or the courts;
    • shortens a notice period in section 9 or in this section.

For a change under point 3, the new version is shown to every member who signs in to the dashboard, before any other page. Only an owner of your organization can accept it, and an owner must do so before using the dashboard further. Until an owner accepts, the version you last accepted keeps applying and your runs continue. If no owner accepts within 30 days of publication, either side can end the agreement under section 9 with immediate effect.