Seven documents, each one written rather than assembled.

LabFlow is provided by Ahsan Mahmood, an independent developer. Using the site, creating an account, or operating a tenant means these terms apply to you. Where a laboratory has agreed separate terms with us in writing, those take precedence over these for that laboratory.

LabFlow is a laboratory information system: registration, ordering, specimen chain of custody, result entry and validation, quality control, and the audited release of reports. It also carries a public directory where a patient can find a laboratory.

Inside a tenant, the laboratory creates accounts, assigns roles and removes people who leave. We do not adjudicate a dispute between a laboratory and its own staff about access. You are responsible for keeping your credentials to yourself; sharing a login inside a laboratory destroys the value of the audit trail, which is the record that protects you when a result is questioned.

Platform staff accounts exist, they are few, and every action they take is written to the same append-only audit trail as everyone else's. Support access to a tenant is not silent.

Do not attempt to reach a tenant that is not yours, do not probe the service in a way that risks other tenants' data, and do not upload anything unlawful. Security research is welcome and there is a route for it in the data security document; testing against a live tenant that holds real patient records is not research, it is an incident.

LabFlow describes three plan shapes: a single laboratory, several under one organisation, and operating the platform for laboratories that are not yours. There is no payment path in the product and nothing on this site can be bought. The plan model exists so that limits are a configuration change later rather than a rebuild; today every limit is effectively unlimited.

A plan is granted by platform staff and carries an end date. When one is in force, these are the terms that apply to it:

• Cancelling ends the renewal, not the period. A granted plan runs to the end of the period it was granted for, and then stops renewing. You keep what was granted until that date.
• Payments already made are not refunded.
• A plan ending never deletes anything. Content over the smaller plan's limits becomes read-only and stays readable and exportable. Deleting a laboratory's records because a plan lapsed would be the worst thing this product could do.

Stated plainly so it is not a surprise later. Read together with the pricing page, which carries the same three shapes and the same absence of a price.

Everything a laboratory puts into its tenant remains that laboratory's. We claim no ownership of it and we take no licence over it. Nothing inside a tenant is used to build or improve anything, which includes every patient record, order, result, report and quality-control run, on every plan.

What sits outside a tenant is treated differently, and the difference is stated here rather than left to be inferred.

We may use non-clinical content from free accounts, meaning support messages, product feedback and bug reports, together with aggregate, de-identified usage statistics, to improve the features we build. Patient records, orders, results and any clinical content are never used this way, on any plan. Nor is anything a patient writes in a satisfaction answer — clause 09. Content in a paid plan is not used to improve features without your explicit consent. You can object at any time, and moving to a paid plan stops it.

Aggregate means a count with no tenant, laboratory or person identifiable in it, which is why this clause and the statement that a tenant's data never leaves its own boundary are both true at once.

The same clause appears in the privacy policy at clause 06, with the legal reasoning for why clinical content is carved out.

This is the most important clause on the page.

We are not responsible for a clinical decision made using a result, for a result that was entered incorrectly, or for a laboratory's choice of rules. We are responsible for the software recording and moving what it was told, accurately and with an audit trail.

There is no uptime commitment, no support response time, and no on-call rota, because the LabFlow team works in one time zone with nobody on call. The service runs on free tiers of the platforms named in the privacy policy, and their limits are ours. A laboratory that needs a contractual availability target does not have one here, and should treat that as a reason to wait rather than as a detail to negotiate later.

Maintenance that takes the service down is announced in advance where it is planned, and afterwards where it is not.

You can stop using LabFlow whenever you like, and you can ask for your data back in an open format before you go. We can end an account for a serious breach of clause 04, and we will say which one.

Ending an account does not shorten a retention window that clinical accreditation requires. What is deleted, what is archived, and what is kept until when is set out on the data deletion page, which is the only page that carries those numbers.

LabFlow is provided as it is. We do not warrant that it is free of defects, that it will always be available, or that it fits a particular laboratory's workflow. Where the law allows us to limit liability, our liability is limited to the amount paid for the service in the twelve months before the claim, which today is nothing, and that is the honest arithmetic rather than a clever cap.

Nothing here limits liability for death or personal injury caused by negligence, for fraud, or for anything else the law does not permit to be limited.

A governing-law and jurisdiction clause belongs here and is not settled. Rather than name a jurisdiction that has not been chosen, it is left open and marked.

Two consequences follow, and both are in your favour. Nothing on this site is an offer capable of acceptance, and no laboratory should treat these terms as a completed contract for production use. When the clause is written it will be dated, published in the feed, and account holders will be told before it takes effect.

Revisions are dated at the top and published in the feed. A change that reduces what you get, or increases what you owe, is sent to account holders by email before it applies.