BitProofTerms of Service
Back to site

Terms of Service

BitProof, a vbounds project · Last updated 3 August 2026 · Contact platform@vbounds.com

These terms govern use of the BitProof console, the relying-party workspace and the evidence packs produced by either. They are written to be read, not to be survived.

1. What BitProof is

BitProof produces evidence about an AI system: a versioned pack containing domain results, a signed computational-integrity attestation, and a list of documentary gaps. Packs can be shared with a named relying party through a read-only link.

2. What BitProof is not

3. Sample data — read this before relying on a pack

Today exactly one domain is measured: computational integrity, produced by the RefKernel engine and sealed with an Ed25519 signature anyone can verify. The other seven domains carry illustrative sample figures and are labelled sample wherever a score appears. Presenting a sample-labelled figure to a third party as a measurement of your system is a misuse of the pack and a breach of these terms.

4. Accounts

You need an account to use the console. You are responsible for the credentials you use and for the accuracy of what you register. You must not register a system you are not authorised to describe. We may suspend an account that is used to misrepresent evidence.

5. Your content

You keep ownership of everything you enter: system descriptions, endpoint URLs, uploaded documents. You grant us only the licence needed to operate the service — to store that content, render it in your console, and render the snapshot you choose to share into the links you issue. We do not use your content to train models.

Never enter a credential. Endpoint URLs are stored in the clear and shown to relying parties; the console rejects URLs that carry a key, a token or a password. Model weights and API keys are never sent to us and the platform has no field to store them in.

6. Share links and reliance

A share link is read-only, scoped to one pack version and one named relying party, expires on the date you choose (up to 365 days), and can be revoked by you at any time from the console. Revocation stops the link resolving; it does not retract a copy the relying party already downloaded or printed.

A reliance letter is a separate, optional instrument arranged by email. It names one relying party, is purpose-limited and point-in-time, and carries a stated liability cap. Its fee is $2,000–$5,000 one-time and is invoiced to the assessed party, never to the relying party. No reliance letter exists unless one has been signed; nothing on the workspace page creates one.

7. The free relying-party workspace

Underwriters, brokers, auditors and reinsurers use the workspace at no charge, now or later. Opening a pack creates no contract between you and BitProof and confers no right of reliance: reliance is created by the letter in section 6 and by nothing else.

8. Acceptable use

9. Availability and change

BitProof is early access. Features described as sample, planned or not yet built may change or may not ship. We will not silently relabel unmeasured data as measured; if a domain goes live, the pack will say so and the change will be dated.

10. Fees

The first report for one system is free. Paid plans start at $15,000 per year per AI system, confirmed in writing before any charge. Reliance-letter fees are as stated in section 6.

11. Liability

To the maximum extent the law allows, our aggregate liability arising out of the service is limited to the fees you paid us in the twelve months before the claim, or, where a reliance letter is in force, to the cap stated in that letter. We are not liable for indirect or consequential loss. Nothing here excludes liability for fraud, for fraudulent misrepresentation, or for anything that cannot lawfully be excluded.

We deliberately avoid a blanket disclaimer against a known relying party: courts routinely void them, which would leave that party with less protection rather than more.

12. Termination

You can stop using the service at any time and ask us to delete your account and its data — see the Privacy Policy. We may terminate for a material breach of section 8, having told you what the breach is.

13. Governing law

These terms are governed by the laws of England and Wales, and the courts of England and Wales have exclusive jurisdiction. If you are contracting from another jurisdiction and this does not work for you, tell us before signing — we would rather agree it up front.

14. Changes to these terms

We will post the updated date at the top of this page and, for a change that materially affects you, email account holders at least 14 days before it takes effect.