ProofPack closed on 26 October 2026. This page is kept as the record of how we handled data while it ran. Read the closure notice.
Terms of service
Version terms-2026-10-11, in effect from 11 October 2026.
Changes from version terms-2026-10-02b (11 October 2026). Clause 10.5 now says what we will do if we stop trading or stop supporting the version you hold: before we do, we issue every annual licensee a licence file with no expiry for that version. The earlier text promised that your right to run the version would not end, which the licence file and the engine do not provide by themselves: after the term and the 30-day grace period in clause 3.5, the engine writes the JSON document only. Clause 2 now says what the compare command computes in the build this site serves: it computes the comparison statistics, where the earlier text said it computed none. As clause 11 says, a change does not apply to a term you have already paid for.
These are the terms on which Global Phoenix Solutions Ltd licenses ProofPack. You accept them by ticking the box at card checkout or by accepting a quote; the version you accepted is recorded against your account. Please read them: they are short, and they say plainly what ProofPack does and does not do.
1. Who the parties are
We are Global Phoenix Solutions Ltd, a company registered in England and Wales, number 14855822, registered office Ground Floor Flat, 259 Chichester Road, Bognor Regis, West Sussex, PO21 5AH, United Kingdom. Contact: Joshua Sandhu, director, joshua.sandhu@globalphoenix.co.uk.
You are the company or other legal entity named on the checkout or the quote as the licensee. The person who accepts these terms confirms that they are authorised to bind that entity. ProofPack is sold to businesses only, not to consumers.
2. What ProofPack is
ProofPack is software that runs inside your own environment. You give it a table of model predictions, reference-standard labels and patient or site attributes, and a criteria file that you author. It computes overall and subgroup performance with confidence intervals and calibration, and reports whether each criterion you wrote is met, not met, or cannot be assessed. Its compare command takes the outputs of two versions of your model on the same rows, checks that they pair row by row and, in the build this site serves on the date of this version, computes the comparison statistics listed at /docs/compare: for each declared operating point the discordant counts and McNemar’s test (not computed on clustered rows); the paired differences of sensitivity, specificity and accuracy with the Newcombe paired interval; the paired DeLong AUROC difference; and, for a score you declare a probability, the paired bootstrap differences of the Brier score and the calibration slope. On clustered rows each difference is a cluster-bootstrap difference. It reports whether a difference meets a margin only where your criteria file declares one. That is the whole of what it does. Comparison statistics that we release after you order are part of the licence you hold at no extra charge.
The documents it renders. The engine writes every result to a JSON document and renders HTML report documents from those results. Report documents and output formats that we release after you order are added to the licence you hold at no extra charge.
3. The licence
3.1 Grant. For each regulated model named on your order, and for the term you paid for, we grant you a non-exclusive, non-transferable licence to install and run ProofPack on your own infrastructure and to use the documents it renders for any purpose of yours, including regulatory submissions.
3.2 Per model. A licence covers one named model. Each additional model needs an additional-model licence at the price shown on /pricing.
3.3 Term. Quarterly or annual, as chosen on the order. There is no monthly plan.
3.4 What “unlimited” means. Within the term you may render packs, re-render them and run the compare command described in section 2 for the licensed model as many times as you wish, and monitoring runs when monitoring is released. It does not mean unlimited acceptance testing: repeated testing against the same locked test set inflates optimism. ProofPack keeps a ledger, on your machine, of how many times each test set has been used in a run with acceptance criteria, and records the count in that run’s output; if your criteria file sets a limit, the run warns when the count passes it. The ledger never leaves your machine.
3.5 The licence file. A licence is a signed file that the engine verifies offline against the public key built into it, which is the key published on /trust. There is no licence server. After the paid term ends, the file enters a 30-day grace period in which the engine still renders, with the watermark “LICENCE EXPIRED - not for submission”; after that the engine writes the JSON document only, carrying the same watermark. The commands that do not need a licence keep working.
3.6 Restrictions. You may not sublicense, resell or provide ProofPack as a service to third parties, and you may not remove or alter a watermark, a version stamp or a methods statement from a rendered document. The engine’s source is published so that anyone can read the arithmetic and re-run it to check a number; it is not released under an open-source licence, and this clause is what permits you to run it on your data.
3.7 Trial and grace watermarks. If we issue you a trial licence, its term ends no later than 30 days after the day we issue it, and every document rendered under it carries the watermark “TRIAL”; a document rendered in the grace period carries the expired watermark in clause 3.5. The numbers in it are the engine’s numbers; the document is not one to file.
4. Price, payment and renewal
4.1 Price. The price is the one shown on /pricing when you order, exclusive of tax. The same price applies whether you pay by card or by invoice.
4.2 Tax. Prices exclude VAT and any other tax. Global Phoenix Solutions Ltd is not registered for UK VAT, so we charge no VAT. We do not ask Stripe to compute tax at card checkout or on the quote route. We are not registered for US sales tax and will not be until a US sale exists. We do not ask for a VAT number or other tax ID at card checkout or on the quote form.
4.3 Card. Payment is taken by Stripe at checkout. The licence is issued when Stripe reports the first invoice paid.
4.4 Invoice. If you take the quote route, you accept the quote online, an invoice is issued, and payment is due within 30 days of the invoice. The licence is issued when the invoice is paid.
4.5 Renewal. A quarterly licence renews for a further quarter at the end of each quarter unless you cancel before the renewal date. An annual licence does not renew by itself: it ends at the end of the year unless you accept a renewal quote, which we send you before the year ends.
4.6 Refund. Within 14 days of the first payment on a new licence, if ProofPack has not rendered a pack you can use, email us and we refund the term in full. After that a licence runs to the end of its paid term and fees are not refundable.
4.7 Failed payment. If a renewal payment fails, your current licence file enters its grace period when its term ends; whether Stripe retries the payment meanwhile is an account setting [unverified: Stripe retry configuration]. If the renewal is still unpaid at the end of the grace period the licence ends.
5. What you remain responsible for
ProofPack computes. You decide. Specifically, you are responsible for:
- the acceptance criteria, margins and non-inferiority bounds in your criteria file, and for the justification you record beside each;
- the reference standard and how the labels were produced;
- the study design, the test set, its independence from training data, and how many times it is used;
- every declaration you make in the criteria file or the pack, including the intended use and the population;
- the lawfulness of the data you process with ProofPack. It runs in your environment; we do not receive your data and we are not a processor of it. If your data includes personal data, you are its controller and you are responsible for your lawful basis and safeguards;
- the submission itself. ProofPack renders documents; your regulatory lead writes and owns the submission.
We do not set a criterion, choose a margin or declare a model good or bad, and no output of ProofPack does either.
6. What we warrant, and what we do not
6.1 We warrant computational correctness. For the licensed version, ProofPack computes what its published source and documentation say it computes, and reproduces the published fixture values and cross-checks listed on /trust/validation to the tolerances in the determinism and tolerance policy published in our documentation at /docs/iq-oq: identical results on the reference platform, and agreement within 1e-9 for closed-form statistics and 1e-6 for iterative ones on other platforms, with bootstrap intervals reproduced to their reported rounding under the same seed.
6.2 If a number is wrong. Tell us. A wrong number is a severity-one defect and we fix it. That fix, and the refund in clause 4.6, are your remedies for a breach of this warranty.
6.3 What we do not warrant. We do not warrant, promise or predict any regulatory outcome. No regulator, notified body or standards organisation has assessed ProofPack or given it any status, and nothing about using it changes what a regulator will do with your submission. We do not offer an interpretation of your results, a judgement on your criteria, or an opinion on whether your model is good enough. The software is otherwise provided as it is, and all other warranties, conditions and terms implied by law are excluded so far as the law allows.
6.4 Draft guidance. Where a document follows the structure of a regulator’s draft guidance, the document says so, and a draft is a draft: it may change or be withdrawn, and following its structure is not conformance with anything.
7. Support
A licence includes answers to computational-correctness questions - is this number right, why does this interval look like that, why did this gate fire - within one business day (Monday to Friday, England). We do not answer, on any channel, which criterion you should set, what margin to choose, or whether a submission will succeed; those questions are outside what ProofPack does, and the reply will say so.
8. Your data and ours
ProofPack runs in your environment. The complete list of what can leave it is published on /trust, generated from the engine’s own egress schema: at most one telemetry record with no row-level data, and nothing at all when run with --offline. The commercial data we hold about you, and the terms on which we hold it, are set out in the privacy notice and the data processing agreement.
9. Liability
9.1 What is not limited. Nothing in these terms limits or excludes either party’s liability for death or personal injury caused by negligence (which section 2(1) of the Unfair Contract Terms Act 1977 does not allow to be excluded or restricted), for fraud or fraudulent misrepresentation, or for anything else that the law does not allow to be limited or excluded.
9.2 The cap. Subject to 9.1, our total liability to you under or in connection with these terms, however arising, is limited to the fees you paid us in the twelve months before the event giving rise to the claim.
9.3 Excluded losses. Subject to 9.1, we are not liable for loss of profit, loss of business, loss of a regulatory decision or of the time to obtain one, or any indirect or consequential loss.
9.4 Why. ProofPack is priced as a tool, not as a share of your submission. If that allocation of risk is not acceptable to you, do not buy it; we would rather you said so now.
10. Term and termination
10.1 These terms apply from the date you accept them until the last licence under them ends.
10.2 Either party may end these terms at once by written notice if the other is in material breach and has not put it right within 30 days of being told, or becomes insolvent.
10.3 We may suspend a licence if a payment is more than 30 days overdue, having told you first.
10.4 On termination your licence ends, but you keep every document you have rendered and may continue to use it. Clauses 5, 6.3, 9 and 12 continue.
10.5 Continuity. The software runs on your infrastructure and keeps running if we stop trading; licence files verify offline; the engine source is published. If we stop trading, or stop supporting the version you hold, then before we do we will issue every annual licensee a licence file with no expiry for the version they hold. That promise is to annual licensees and covers the version held when we issue the file; it does not cover versions released later, and it is not a promise of support or updates.
11. Changes to these terms
We may change these terms for future orders and renewals. We will publish the new version here with a new version line and date, and tell the contact on your account by email at least 30 days before a change applies to a renewal. A change does not apply to a term you have already paid for. If you do not accept a change, you may let your licence end at the next renewal.
12. General
12.1 Governing law. These terms are governed by the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction.
12.2 Whole agreement. These terms, the order, the pricing page as it stood when you ordered, and the data processing agreement are the whole agreement between us about ProofPack, and replace anything said before.
12.3 Notices. By email: to us at joshua.sandhu@globalphoenix.co.uk, and to you at the address on your account.
12.4 Assignment. You may not transfer these terms without our written consent; we may transfer them to a successor to our business, and will tell you if we do.
12.5 Severance. If any part of these terms is found unenforceable, the rest stands.
Other legal pages: Privacy · DPA · Sub-processors · Outreach privacy notice · Legitimate interests assessment