Terms
Terms of service
The terms for every Agentic Evals package, in plain English. Version 6, 31 October 2026. Applies to orders placed from the date this version is published, and not retroactively to orders placed before it. Version 5, 29 October 2026, remains in force for every order placed while it applied and is kept word for word in the version 5 terms. The earlier version, 18 October 2026, is kept word for word in the version 4 terms, and it still applies to any order placed while it was in force.
1. Who we are
Agentic Evals is a service of Agentic Thinking Ltd, a company registered in England and Wales, company number 17152930. Our address is Office 9, Sycamore Trading Estate, Squires Gate, Blackpool FY4 3RL, United Kingdom. We are registered with the Information Commissioner's Office. Contact us at sales@agenticthinking.uk.
2. Who these terms are for
Our services are supplied to business customers only.
Our packages are sold to businesses. By buying, you confirm you are buying for a business, including as a founder of a product you are building, and not as a consumer.
3. What you buy
You buy one fixed-price product from the buy page. There are four:
- Honest Second Opinion. A signed written opinion on the evidence you already hold. It carries no certificate.
- Deny Means Deny certificate. One refusal-boundary check at one version and one date, with a signed Deny Means Deny certificate when the check holds.
- Advanced pack. Open source or private code, with or without one re-test. It includes the five-check baseline and the deeper tests agreed in your approach specification, and it issues a Certificate of Independent Evaluation when every applicable check passes.
- Deep evaluation. Scoped and priced in writing with you before any work starts. It issues the same certificate as the advanced pack, on the same condition.
The price on the buy page is the whole price. No VAT is added. The price shown is the total you pay. You pay in full, in advance, through Stripe. The fee does not depend on the result. Where a product issues a certificate, that certificate records the scoped evaluation outcome at one commit; it is not accredited product certification, a penetration test or an endorsement.
Plans, proposals and test specifications
A tailored approach specification or proposal describes our proposed approach, boundary, candidate cases, evidence aims, prerequisites and limits. It may identify feasibility questions to resolve. A plan or proposal is a planning deliverable; it is not the agreed test specification, an executable test kit or a completed evaluation. Candidate coverage in a proposal is not confirmed coverage.
The test specification is a separate written record of the agreed target and commit, evaluation boundary, selected cases and expected behaviours, relevant configuration and state, evidence and reproduction deliverables, exclusions and delivery date. We agree it with you before testing begins. A proposal does not itself authorise testing or establish a finding about your product.
The detailed test plan we prepare after stage 1 is agreed is our confidential working document. We do not share the plan. If the engagement is cancelled after stage 1 is agreed and before testing starts, stage 2 of "Founders Pragmatic Refund Policy" applies. Work carried out before your order does not retrospectively become paid work.
Founders Pragmatic Refund Policy
Every evaluation runs in three stages.
Approach and feasibility. We agree in writing the cases, expected behaviour, boundary and prerequisites, and confirm with a short feasibility check that our environment can host your software at the agreed commit and interact with it as the cases require. If we cannot agree the approach or complete the feasibility check within 10 working days of payment, we refund the fee in full. The 10 working days pause while any item on the intake list we issue with your order is outstanding. Once both parties have agreed the approach and the feasibility check in writing, this stage is closed and its refund no longer applies.
Detailed plan. Planning begins on the day stage 1 closes. We turn the approach agreed in stage 1 into the detailed technical plan: exactly what executes for each agreed case, including inputs, fixtures, steps and checks. The plan is our confidential working document and is not shared. At delivery you receive the report and the reproduction materials for the agreed cases, as set out in your package. If you cancel after stage 1 is agreed and before testing starts, we refund two thirds of the fee and retain one third for the planning work. If we cancel in that period, we refund the fee in full.
Testing. Testing starts on the date we notify you in writing that testing has begun. Once testing starts, the refunds above are closed and the fee is not refundable. If an agreed case proves impossible to run for a reason not foreseen at the approach stage, we will propose a replacement case that tests the same claim or risk to at least the same depth, which you will not unreasonably refuse. If no reasonable replacement can be agreed, we refund the fee divided by the number of agreed cases for each case not delivered. You receive a full refund if we cannot deliver the agreed package at all, or if we miss the agreed delivery date by more than five working days. The delivery date is extended by any period in which your environment or access is unavailable.
The delivery clock starts when stage 1 is agreed.
4. What an evaluation is, and what it is not
An evaluation tests your product at one fixed commit, in our isolated environment, against the checks and cases in your package. The report describes what we observed under those conditions, with its limits stated. Severity is our judgement.
An evaluation is not a certification, a penetration test, an audit opinion, a guarantee that your product is secure, or an endorsement. A result holds only for the commit and configuration we tested. You must not present a report, or any part of it, as a certification or endorsement by us.
5. What you agree to do
- Only submit software you own or are authorised to have tested, and tell us anything we must not do during testing. You will cover any third-party claim that says you were not authorised.
- You authorise us to run, probe, attack and attempt to subvert the submitted software in our environment. You confirm testing will not reach any live system or any third party's system unless that party has given written consent you have shown us, and you will set up the intake (stubs, mocks, test endpoints) accordingly. You will cover any loss or claim we suffer because this confirmation is wrong.
- Give us a complete, runnable intake: the repository link, the exact commit, how to run it, and one action your guardrails must block. That is what "complete runnable intake" means in these terms.
- Never send us production secrets, live service credentials or customer personal data. Read-only repository tokens scoped to the evaluation are fine; revoke them when we confirm deletion. We plant our own fake secrets for testing.
- Implement any fixes yourself. We do not change your code.
6. Delivery
The delivery clock starts when stage 1 is agreed, as "Founders Pragmatic Refund Policy" says. We aim to start testing within 2 hours of that point and receipt of a complete runnable intake, during UK business hours (9am to 6pm, Monday to Friday, excluding bank holidays); if both arrive outside those hours, within 2 hours of the next business-hours opening. The baseline report arrives within 5 working days of the delivery clock starting. For advanced packs we confirm the test scope and delivery date in writing from your complete intake before testing starts. Testing itself starts only after scope is confirmed.
If your product cannot run in the agreed environment, we contact you to agree the next step. The applicable stage in "Founders Pragmatic Refund Policy" above decides what is refunded, including the full refund if we cannot deliver the agreed package at all.
7. Re-tests
A package with a re-test includes one re-test of the original agreed cases and controls at one updated commit, submitted within 60 days of your first report. New workflows, material rewrites and further rounds are outside the package. A re-test not used within 60 days expires. Because we delete your source code when we deliver the report, a re-test needs fresh read access to the updated commit.
8. Cancellation and refunds
You can cancel by emailing sales@agenticthinking.uk. For business purchases, the stages and refund rules are set out in Founders Pragmatic Refund Policy above.
If you are nonetheless a consumer, the business refund rules above do not replace your statutory cancellation rights. If you expressly request work to start during the 14-day cancellation period and then cancel before the service is fully performed, any charge must be proportionate to the service actually supplied, as permitted by law. Loss of a statutory cancellation right on full performance requires the consent and acknowledgement required by law. Nothing in these terms limits your statutory rights.
9. Your code and data
- We never use your code to train models. Where AI is used, we use frontier models configured not to use your input for training. We list the providers on request.
- We delete our working copies of your source code when we deliver your report, and confirm it in writing.
- We keep the report and its evidence files for 12 months for comparison and re-tests, then delete them unless you ask us to keep them longer. Evidence can contain source excerpts and command output. You can ask us to delete it sooner.
- For private code you accept our confidentiality agreement (NDA), already signed by us, before you share access.
- Where your code or logs contain personal data, we process it as your processor, only to perform the evaluation and on your instructions in these terms. We keep it confidential and secure, use only the sub-processors we list on request (AI model and hosting providers) and tell you before changing them, make sure everyone who handles it is bound by confidentiality, impose the same data protection obligations on our sub-processors, tell you without undue delay if we become aware of a personal data breach affecting it, help you with data subject requests where relevant, delete it as set out in these terms, and give you the information reasonably needed to show compliance. Transfers outside the UK use the UK International Data Transfer Addendum or an adequacy decision. Subject matter and duration: the evaluation, for the evaluation period and the retention periods above. Data: whatever personal data is contained in the material you submit (typically names, email addresses and usernames of your staff or users).
10. Confidentiality and publication
Your report is private, whether your code is private or open source. We publish it, or name you as a customer, only with your written agreement. We may use anonymised, aggregate statistics across evaluations, such as how many products failed a check, in our publishing, marketing and research. We keep them in groups large enough that they never identify you or your product.
If we find a vulnerability in someone else's software while testing yours, we tell you first and consider your views. After at least 14 days, or longer if you show us a contract with that vendor that requires it, we may report it to that vendor under Agentic Thinking's published disclosure policy, without naming you or including your confidential information unless you agree in writing.
11. Ownership
You keep all rights in your code. The report is yours to use, including the fix prompts and regression tests in it. We keep the rights in our methods, tools, probes and templates, and may use what we learn from evaluations to improve them. You may not republish our methods, probes or tooling as a product or service.
12. Liability
Nothing in these terms limits liability for death or personal injury caused by negligence, for fraud, or for anything else the law does not allow us to limit.
Subject to that, our total liability for a package is limited to the fee you paid for that package. We are not liable for loss of profit, revenue, data or goodwill, for indirect or consequential loss, or for decisions you or anyone else make based on a report. For private code, liability for breach of confidentiality is set by the confidentiality agreement instead.
13. Changes and law
We may update these terms. The version in force when you paid applies to your package. These terms are governed by the law of England and Wales, and its courts have exclusive jurisdiction. Nobody other than you and us may enforce these terms (Contracts (Rights of Third Parties) Act 1999).
We may decline or stop an evaluation if the software appears unlawful, is designed to attack, defraud or harass third parties, or breaches our AI providers' acceptable use policies; any refund follows "Founders Pragmatic Refund Policy" above. We do not sell to persons or countries under UK sanctions.