Terms of Service

These Terms govern the agreement between Anchorly LTD, registered in England & Wales (“Provider”, “we”) and you, the client (“Client”, “you”), for QA Lead engagements.

A QA automation enablement engagement, in up to three phases: a free pilot, a fixed-fee build, and hourly support after handover. The work is building a Playwright test suite and a web console against your application, integrating both with your existing tools, deploying them into your cloud account, and handing them over to your team with documentation.

This is professional services, not a software licence. There is no product to subscribe to, no per-seat fee, and nothing that stops working if you stop paying us.

The pilot is free and carries no obligation on either side to proceed further. There is no contract for it beyond these Terms, no invoice, and no notice period. Whatever we produce during the pilot is yours to keep and use, on the ownership terms in section 5, whether or not you engage us for the build.

We may stop a pilot early if the test environment turns out to be unusable or the necessary access cannot be arranged. If we do, you keep what exists at that point and owe nothing.

• The build fee is fixed and agreed in writing before the build starts. It is invoiced monthly across the engagement.
• Invoices are payable within 30 days unless we agree otherwise in writing.
• Support after handover is billed by the hour against a rate agreed in advance, in arrears, with a short written summary of what the hours went on. There is no retainer and no minimum commitment.
• A material change to agreed scope is quoted and agreed separately before the work happens, not billed as a surprise.
• Fees exclude VAT and any cloud or AI provider costs, which you pay directly.

You own the deliverables. On payment of the fees due for a phase, all intellectual property in the work produced in that phase — the test suite, the console, the infrastructure-as-code, the documentation — is assigned to you outright, together with the right to use, modify, sublicense and distribute it without restriction or further payment. Deliverables from the free pilot are assigned to you on completion of the pilot, with no payment condition.

Where a deliverable incorporates general-purpose tooling, libraries or boilerplate we developed before the engagement and reuse across clients, that pre-existing material remains ours, and you receive a perpetual, worldwide, royalty-free licence to use it as part of the deliverable. We will not use this carve-out to retain anything you would need in order to run, modify or extend what we hand over.

Third-party open-source components remain under their own licences. We will tell you what they are.

You provide a test environment, test-account credentials, and read access to wherever your test cases and requirements live. We ask for the narrowest access that makes the work possible and handle credentials as described in the Privacy Policy. You should revoke all access at the end of the engagement.

We do not want access to production systems or to real customer data. If a test environment contains real personal data, tell us before work starts so it can be anonymised or a data-processing agreement put in place.

These engagements use AI agents as part of the delivered system and as part of how we work: agents draft test cases from your requirements, investigate failures, and sometimes draft test code. You should know three things about that.

• Machine-drafted output is always opened for human review — as a draft pull request or as an editable draft in the console. It is never merged or pushed to your test-management tool automatically.
• Agents are not permitted to modify your application code. Their write access is limited to test paths by an allowlist, and changes outside it are discarded.
• Once the deployment is in your account, AI usage is authenticated with a provider API key issued from your own provider account, so those costs and that processing are yours and visible to you. You are responsible for obtaining that key and for complying with your AI provider’s terms; we do not resell AI capacity and take no margin on it. The platform does not use credentials tied to an individual’s personal AI subscription.

Delivery depends on things only you can provide: a test environment that is not reset or rebuilt from under us without warning, test data that can be created programmatically, and a named person on your side who can answer “is this behaviour correct?” within a reasonable time. Where these are not available, timelines move, and we will tell you as soon as we can see it happening rather than at the end.

We deliver the service with reasonable skill and care, to the standard of a competent test-automation professional. But to be explicit, because it matters: an automated test suite reduces the risk of regressions reaching production; it does not eliminate it, and it is not a guarantee that your software is free of defects. Tests verify the behaviours they cover, against the environment they run in, at the time they run. We do not warrant that the suite will find any particular defect, that it will remain green as your application changes, or that it is a substitute for your own release judgement.

AI-generated test cases and AI failure analyses are drafts and opinions for a human to review. We do not warrant that a root-cause classification is correct.

To the maximum extent permitted by law, our total aggregate liability under or in connection with these Terms is capped at the fees you paid us in the twelve months preceding the event giving rise to the claim — and, for the free pilot, at £1,000, since no fees are paid for it. We are not liable for indirect, incidental or consequential losses, including lost revenue, lost profits, lost data, or losses arising from a defect that reached production. Nothing in these Terms limits liability for death or personal injury caused by negligence, for fraud, or for anything else that cannot lawfully be limited.

We treat your code, test cases, requirements, credentials and commercial information as confidential, and a mutual NDA is available on request before any work begins.

We describe past engagements publicly by sector only — for example “a fintech reporting platform” — with no client name, logo or domain, unless you give written permission otherwise. Aggregate figures such as the number of test cases catalogued may be cited without identifying you. If you would prefer an engagement not be referenced at all, say so and it will not be.

Either party may terminate a paid engagement on 30 days’ written notice, or immediately for material breach that is not cured within 14 days of written notice. A pilot may be ended at any time by either side with no notice. On termination you pay for work delivered up to that date, we hand over everything produced so far in a usable state with ownership assigned under section 5, and you revoke our access.

These Terms are governed by the laws of England and Wales, and disputes are subject to the exclusive jurisdiction of its courts.

Questions about these Terms? Email support@anchorly.co.