Terms of Service
These terms are the agreement between your organisation and MacleodLabs for the use of TeamFlow. They cover who owns an organisation, what a plan buys, what you may not do with the service, and who carries which risk.
Effective 25 September 2026 Last updated 25 September 2026 Applies to codercat.io and the TeamFlow service
1. The agreement
TeamFlow is operated by Macleod Labs FZ-LLC (registration number 0000004088182), of CWEP4972, Compass Building, Al Shohada Road, Al Hamra Industrial Zone-FZ, Ras Al Khaimah, United Arab Emirates. In these terms, we and us mean that company, and you means the person or organisation using TeamFlow.
By signing up, by joining an organisation through an invite, or by sending a report from the plugin or a CI reporter, you accept these terms. If you are accepting them for a company, you are confirming that you may bind it. Our Privacy Policy forms part of this agreement.
2. The service
TeamFlow maps the delivery state of issues in Jira, Linear and GitHub Issues as people and coding agents move them through tests, audits, CI and deploys. Reporters in your editor and your pipelines publish derived state about each issue, the service stores the current state per issue, and the dashboard draws it.
TeamFlow manages your AI software factory. It is not a system of record. Your tracker, your repository and your pipeline remain the authority for the underlying work. What we hold and what a report may carry is fixed by the reporting contract described in the Privacy Policy.
3. Accounts and organisations
The first person to sign up creates the organisation and becomes its owner. The organisation's domain is taken from the owner's email domain. Signing up from the website creates a one-person organisation with that person as owner.
Joining an existing organisation is invite-only. The owner copies an invite link and the person who opens it joins in one step; nobody can type their way into an organisation. An existing member can move into another organisation by accepting an invite while signed in, which moves their membership and their billing. An organisation is archived when its last member leaves, and its data stays readable to its administrators.
As an owner you are responsible for: the accuracy of the details you give us, who you invite and what they do with the service, treating invite links as the keys they are, removing members who should no longer have access, and everything done under your organisation's credentials. Keep your sign-in and any credential the service issues secret, and tell us promptly if one is exposed.
Accounts are personal. Do not share one, and do not let somebody else use your sign-in.
4. Plans, seats and billing
Members subscribe individually, or are covered by a team plan. A team plan covers five reporting seats; a team organisation adds further seats at the solo rate. Prices are in US dollars:
| Plan | Covers | Monthly | Annual |
|---|---|---|---|
| Solo | 1 reporting seat | USD 25 | USD 240 |
| Team | 5 reporting seats | USD 99 | USD 1,140 |
A reporting seat is one person whose sessions report to the service. Every agent, subagent, worktree and machine operating under that person's sessions reports on their seat and costs nothing extra. A viewer signs in and reads the board but does not report. Each viewer takes a paid seat, in the same way as a person who reports. A Solo plan, which is for one person, has no viewers. Continuous integration, tracker connections and agents report without a seat.
Fair use. Reporting is not billed by volume: you pay for seats, never for the number of reports your sessions send, and heavy use by agents is expected because it is what the service is for. We do count reports, as the privacy policy says, but only to tell ordinary heavy use from abuse. Two things pause reporting automatically, and a pause is the whole of it — the board stays readable, nothing is deleted, and the rest of the organisation is unaffected. The first is use far beyond what any normal team produces, which we will ask you to discuss with us as an enterprise arrangement. The second is one machine's credential being used from a second machine, which we treat as a credential to re-issue. A pause lifts once its cause stops, or when we agree terms with you. Anything else we consider abuse — automated traffic that is not delivery reporting, resale of the service, or use that degrades it for others — is reviewed by a person before we act, and suspension is governed by section 9.
The fair use guidelines form part of these terms and say in more detail what each rule means and how a pause lifts: a seat is for one person, a credential is for one machine, and usage far beyond a normal team is handled as a conversation about an enterprise plan. We will not terminate or delete an account for fair-use reasons. Instead the account is suspended automatically: reporting pauses, the board stays readable, nothing is deleted, and it lifts when the cause stops.
Joining an organisation when you already subscribe. Your own plan and an organisation's plan are separate, and joining an organisation never merges them. If you subscribe in your own right and you accept an invitation to an organisation, you take a seat that organisation's plan already pays for. Your own subscription is not moved to the organisation, changed or cancelled, and your own workspace carries on beside the organisation's. Whether you keep your own subscription is up to you; section 5 governs cancelling. If the organisation has no unused seat, you can join once its owner makes room; you are never asked to pay for a seat on somebody else's organisation. A Solo plan is for one person and takes no members or viewers. To add people, its owner upgrades it to the Team plan, which changes the plan on the same subscription: Stripe charges the difference for the rest of the current period, and the workspace and everything in it stay as they are.
Free trial. Paid plans are not open yet. Until they open, every new organisation gets a free trial of the Growth plan for 30 days, and no card is needed. While paid plans are closed, we extend each trial before it ends, so nobody loses access. When paid plans open, we will tell you, and every trial then runs for at least 14 more days so that you can choose a plan. After that, if nobody subscribes before the trial ends, the plugin stops uploading reports: sign-in, the board, its history and the organisation's members all stay, nothing is deleted, and reporting resumes as soon as somebody subscribes.
Stripe processes every payment once paid plans open. By subscribing you also accept Stripe's terms for the payment itself. Subscriptions renew automatically at the same price and period until they are cancelled. If a payment fails we may retry it and, if it keeps failing, suspend the organisation under section 9.
Prices are exclusive of any value added tax, sales tax or similar charge unless we say otherwise at checkout. Macleod Labs FZ-LLC is not registered for VAT, so we charge no VAT. If we register, we will add VAT where the law requires it and tell you before it applies. You are responsible for any withholding tax in your own country.
We may change prices for future periods. An existing subscription keeps its price until the end of the period it has paid for, and we will tell you before the new price applies.
5. No refunds, cancellation and payment disputes
You can cancel at any time. Cancellation stops the next renewal; the subscription runs to the end of the period you have already paid for, and then access ends.
All fees are non-refundable. We do not refund or otherwise compensate a part-used period, or a downgrade or cancellation made part-way through a period. Cancelling stops the next renewal and you keep access until the period you have paid for ends. The only exceptions are a charge we made in error, which we will correct, and any refund right the law gives you that cannot be waived by agreement.
Payment disputes. If you believe a charge is wrong, contact us first so that we can put it right. Opening a payment dispute or chargeback with your bank or card issuer without contacting us is a breach of these terms. While a dispute is open we may suspend the organisation, which means its members lose access and its reports are refused. We will contest a dispute with the records of your use of the service, and we may recover the disputed amount together with any fee the payment processor charges us for it. If a payment is reversed for any reason, the seats it paid for are removed from the organisation.
6. Acceptable use
Use TeamFlow for its purpose and leave other people's data alone. You must not:
- attempt to read, write to or address another organisation's tenant, or to obtain a credential you were not given;
- probe, scan or attack the service, or interfere with anybody else's use of it;
- ignore rate limits. When the service asks you to slow down, wait for the interval it names rather than retrying in a tight loop;
- reverse engineer, decompile or attempt to derive the source of the hosted service, or copy it to build a competing product. This does not restrict anything we publish under an open source licence, and does not override rights you have by law;
- attempt to smuggle content past the reporting allowlist, including prompts, source code, diffs, shell output, secrets, issue bodies or raw logs, by renaming fields or any other means;
- send unlawful, infringing or malicious content, or personal data you have no right to send;
- resell, sublicense or provide the service to anybody outside your organisation without our written agreement;
- use the service to build a profile of an individual's productivity for a purpose that would be unlawful where they work.
You are responsible for making sure the people whose names appear in your reports know that their work is reported, as their employer requires.
7. Your data and our licence
Your data stays yours. You keep every right you have in the reports your organisation sends and in the content behind them. We claim no ownership of it.
You grant us a licence to host, store, copy, transmit, back up and display that data, limited to what is needed to provide the service to you, to keep it secure, and to fix faults in it. The licence lasts as long as we hold the data and ends when the data is deleted. We do not sell your data or share it for advertising.
How the troubleshooting classifier uses your data. TeamFlow's troubleshooting classifier learns from your organisation's own data, and never shares it. It uses what it learns only to improve the decisions it makes for your organisation.
TeamFlow keeps that learning apart from every other organisation. An owner or admin can switch the learning off at any time. TeamFlow then uses a general autofix method and deletes what it learned from your data. Our licence covers this use only while the learning is switched on.
Here, “your data” means the derived state TeamFlow already holds: stages, statuses, check results, decisions and their outcomes. You have full control over your data. It is never shared outside your organisation, and it is encrypted at rest and in transit. Agent conversations are also encrypted with a key that belongs to your organisation alone. Streaming agent conversations with Agent view is strictly opt-in and managed by your organisation's owners and admins. It never means secrets.
You confirm that you have the right to send us what your reporters send, and that doing so does not breach anybody else's rights or your own obligations.
We may use aggregate, anonymous statistics about how the service is used, in a form that identifies neither you nor your organisation, to run and improve it.
8. Availability
We work to keep TeamFlow available and quick, but at this stage of the product we offer no service level agreement and no uptime commitment. We may take the service down for maintenance, and we may change or remove features. If we withdraw a material feature we will give reasonable notice.
Reporters queue and retry when the service is unavailable, so a short outage delays the board rather than losing the work behind it.
9. Suspension and termination
We may suspend or close an organisation's access if a payment is not made, if these terms are breached, if the service is being used in a way that endangers it or other customers, or if the law requires it. Where it is reasonable to do so we will warn you first and give you a chance to put it right. For a serious breach or a security risk we may act immediately.
A TeamFlow administrator can suspend, restore or close an organisation in the course of running the service, and can act on a lawful request. Administrative access is limited to the people who operate the service and is used for support, billing and abuse.
You can close your organisation at any time by asking us. On termination your access ends, and your data is deleted or archived on the timetable in the Privacy Policy. Sections 7, 10, 11 and 13 survive termination.
10. Disclaimers
TeamFlow is provided as is. To the extent the law allows, we exclude all implied warranties, including fitness for a particular purpose, merchantability and non-infringement. We do not warrant that the service will be uninterrupted or error free, or that the board it draws is complete: it reflects the reports it has received, and a reporter that is switched off or cannot reach us produces a board that is out of date.
Do not rely on TeamFlow alone as evidence of compliance, of a deployment, or of anything else that matters legally. Your tracker, your pipeline and your repository hold the record.
11. Limitation of liability
Nothing in these terms limits liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for anything else that cannot be limited by law.
Subject to that, we are not liable for loss of profit, loss of business, loss of goodwill, loss of anticipated savings, or any indirect or consequential loss; and our total liability arising out of or in connection with this agreement is limited to the fees you paid us in the twelve months before the event giving rise to the claim.
Each party is responsible for its own compliance with data protection law, and the licence in section 7 does not make us responsible for what your organisation chooses to report.
12. Changes to these terms
We may change these terms as the product changes. We will update the effective date at the top of this page, and for a material change we will email the owner of every organisation 30 days before it takes effect. Continuing to use the service after a change takes effect means you accept it. If you do not, you can cancel under section 5.
13. Governing law
This agreement is governed by the laws of the Emirate of Ras Al Khaimah and the applicable federal laws of the United Arab Emirates, and the courts of Ras Al Khaimah have exclusive jurisdiction over any dispute, except that either party may seek an injunction wherever it is needed. If you are a consumer, this does not take away the protection of the mandatory law of the country where you live.
If any part of these terms is found unenforceable, the rest continues to apply. A delay in enforcing a term is not a waiver of it. These terms, with the Privacy Policy, are the whole agreement between us about TeamFlow.
14. Contact us
Questions about these terms, notices under them, and anything else legal go to macleod@macleodlabs.ai, by phone on +971 58 633 0035, or by post to CWEP4972, Compass Building, Al Shohada Road, Al Hamra Industrial Zone-FZ, Ras Al Khaimah, United Arab Emirates.