Terms & conditions

Last updated: October 16, 2026

1. The service

"Verdifax" is the deterministic execution and attestation platform described at verdifax.com, including the API, the dashboard, the documentation site, the SDKs, and the Verdifax Final Artifact (.VFA) format. "We", "us", and "our" refer to Verdifax, LLC, a Delaware limited liability company. "You" refers to the individual or organization accessing the service.

2. Eligibility

You may use Verdifax only if you have the legal capacity to enter into contracts in your jurisdiction, and only for purposes that are lawful in the jurisdictions in which you operate. Verdifax is not directed at children under 16.

3. Access and accounts

Access to the API requires an API key. API keys are scoped to the account that requested them and may not be transferred. You are responsible for keeping API keys confidential and for all activity that occurs under your keys. The dashboard stores your API key in your browser's local storage, so anyone who can use that browser profile can read it. You must notify us immediately if you suspect a key has been compromised.

4. Acceptable use

You may not use Verdifax to: violate applicable law; infringe the intellectual-property or privacy rights of others; transmit malware; generate manifest hashes for content you have no right to attest; attempt to subvert the cryptographic verification chain; or interfere with the operation of the service. We reserve the right to suspend or terminate access for violations.

5. Your data

You retain all rights in the inputs you submit to the service. You grant us a limited license to process those inputs solely to provide the service, including sending AI output text to Anthropic for the governance review described below.

The API receives your payload, any AI output text, and any metadata you include in readable form. We store a SHA-256 hash of the payload and of the AI output text, not the raw content, except that an error message from a failed governance review can contain text from that review. We store the metadata you include exactly as you send it, as part of a sealed record. For runs anchored in the public Sigstore Rekor log, the service currently has no way to edit or remove that metadata, and we keep stored data indefinitely. Your API key cannot make a record public: only a Verdifax admin key can publish a record, and only for a run created with that same admin key. A route_id that begins with buyer-demo- does not make a record public; records published under that earlier rule remain public, as our privacy policy describes. We do not use your inputs to train any model.

Our hosted service has the AI governance review turned on. When a request includes AI output text, we send that text to Anthropic's Claude API for review. By including AI output text, you confirm that you have the rights and permissions needed for us to send it to Anthropic. The review is produced by a third-party AI model and can be wrong, so do not rely on factual statements in it without checking them yourself.

See the Privacy policy and the sub-processor list for full detail.

6. Verification scope

The Verdifax manifest hash is a SHA-256 digest computed from the sealed record of a run. Recomputing it from the sealed fields yields the recorded value, and any change to a field the manifest covers produces a different hash. For records sealed from run 239 on, a second public-log entry binds a digest of every section of the record, so a change to any section made after anchoring no longer matches that entry, and removing that entry from the bundle makes verification fail, because the first entry states that it is required. Run 238 also carries the second entry, but removing it lowers the verifier's verdict to partial coverage instead of a failure. Since verifier 0.12.0, a public-log entry counts only if it is signed with a published Verdifax log-signing key and the timestamp the log signs for it verifies, so a rewritten record that anyone else logs as a new entry fails. Verdifax holds that key. From run 240 on, each record seals a 600-second anchoring window, so a later re-log, even by Verdifax, fails or must carry a new sealed date; earlier records show their authenticated anchoring time but cannot fail on it. For records sealed before run 238, the public-log entry binds the run's identity and, on leaf v5 records, its 33 pre-anchor values, so a change to those values made after sealing no longer matches that entry; the descriptive sections of those records (outcome summary, request substance, authorization and approval chain, real-world effects, system provenance) are sealed by hashes inside the bundle but are not bound to the public log, so they show the bundle is internally consistent, not that a party able to rewrite the whole bundle has not changed them. Each /execute call seals its own clock value and nonce, so two submissions of the same inputs produce different manifest hashes by design. A production record is verified by recomputing its seals from its recorded fields, not by re-running it.

The open-source verifier, verdifax-verify, checks a run's audit bundle offline without relying on Verdifax's servers, including the Sigstore Rekor inclusion proof for runs anchored in that public log. Recomputing the manifest hash itself requires the full stored manifest, which Verdifax holds; GET /runs/{id}/verify performs that check for authenticated callers.

Our hosted service runs without a hardware attestation agent today, and each audit bundle states whether hardware attestation evidence is present for that run. The actor signature in a record is made by our server with a signing key that we generated and hold for your API key, so it shows that our server signed the record with that key, not that you signed it yourself.

The manifest hash does not prove that the model's output is correct, fair, unbiased, or aligned; that the values in your inputs are true; that a user is who they claim to be; that a model actually produced the output you submitted; or that caller-declared context is true. Verdifax attests to what it received and sealed. The full scope is stated at What the Manifest Hash proves, which forms part of these terms. If that page and these terms conflict, these terms control.

7. Fees and billing

Use of the service may be subject to fees described in your order form. Fees are exclusive of taxes. Payments are processed by Stripe, and payment card data never reaches Verdifax's systems. Failure to pay invoiced fees within thirty (30) days may result in suspension of service.

8. Intellectual property

The Verdifax software, documentation, designs, trademarks, and the Verdifax Final Artifact format are owned by us and are protected by intellectual-property law, except for the open-source components described in section 9. We grant you a non-exclusive, non-transferable, revocable license to access and use the service for its intended purpose during the term. No other rights are granted by implication.

9. Open source components

Verdifax incorporates open-source software, and those components remain subject to their respective licenses. The Verdifax verifier is published under the Clear BSD License at github.com/Verdifax/verdifax-verify.

10. Warranties and disclaimers

The service is provided "as is" to the maximum extent permitted by law. We do not warrant that the service will be uninterrupted, error-free, or fit for any particular purpose other than producing verifiable attestations of the runs you submit. Cryptographic guarantees are limited to those stated in section 6 and in the documentation it incorporates.

11. Limitation of liability

To the maximum extent permitted by law, our aggregate liability arising out of or related to the service is limited to the amount paid by you to us in the twelve (12) months preceding the event giving rise to the claim. We are not liable for indirect, incidental, special, consequential, or punitive damages.

12. Indemnification

You agree to indemnify and hold us harmless from claims arising out of your use of the service in violation of these terms or applicable law, including claims that the inputs you submitted infringed the rights of a third party.

13. Termination

You may stop using the service at any time. We may suspend or terminate your access if you breach these terms, if continued service would expose us to legal risk, or if you fail to pay fees when due. On termination, your right to access the service ends. Records sealed before termination stay in our database, as described in the Privacy policy, and their entries in the public Sigstore Rekor log cannot be removed.

14. Changes

We may update these terms from time to time. We will post each update on this page with a new "Last updated" date. For material changes, we will also email account holders; we send these emails by hand, because the service has no automated notice system. Continued use after the effective date constitutes acceptance. [Pending review by counsel: whether changes made this way bind existing users under Delaware law.]

15. Governing law

These terms are governed by the laws of the State of Delaware, USA, without regard to conflict-of-laws principles. Disputes will be resolved in the state or federal courts located in Delaware, except where you are a consumer protected by mandatory law in your country of residence.

16. Contact

Questions about these terms can be sent to legal@verdifax.com.