Legal

Terms of Service

The terms on which dVeracity Inc. provides dveracity.com, the dVeracity API and MCP server, Validation as a Service, and the verification platform.

Effective 7 September 2026.

1. The agreement

These terms are a contract between you and dVeracity Inc. (226 Skylark Pt, Jupiter, FL 33458, USA). You accept them by creating an account, by using an API key, by authorising an AI agent or assistant to connect to dVeracity on your behalf, or by using the website. If you act for an organisation, you confirm you may bind it, and “you” includes it. Our Privacy Policy explains what we do with personal data and forms part of these terms.

2. The service

dVeracity provides:

  • The Open Footprint reference layer — the canonical Open Footprint data model, sector profiles, policy guardrails and O-DEF semantic annotations, readable through the website, the API and the MCP server.
  • The Semantic API — natural-language queries over a verified emissions knowledge graph, metered per call.
  • Validation as a Service — checking submitted emissions and product-footprint data against published standards, metered per call.
  • The verification platform — tooling through which data is ingested, checked and presented to accredited verifiers.

Features, tiers, call ceilings and credit prices are those shown on Pricing and at checkout at the time you buy. We may improve or change the service; where a change removes something you paid for, section 10 applies.

3. Accounts, keys and connected agents

  • You are responsible for everything done with your account, your API keys, and any AI agent or assistant you authorise through our consent screen. Keep keys secret; revoke any you believe is exposed — you can do so at any time in the dashboard.
  • An agent you authorise acts as you. Its calls are attributed to your account and metered against it, and its results are returned to the client you connected — what that client does with them is governed by its operator's terms, not ours.
  • Every tool the MCP server exposes reads data; none creates, changes or deletes anything you own. Metered tools spend credits, which is a billing event, not a change to your data.
  • One person per account. Do not share credentials or circumvent tier limits by operating multiple accounts.

4. Plans, credits and payment

  • Tiers. Each tier carries a monthly API-call ceiling as shown on the pricing page. Calls above the ceiling are refused until the next billing period or an upgrade.
  • Subscriptions are billed in advance by Stripe at the start of each billing period and renew automatically. You may cancel at any time; cancellation takes effect at the end of the period already paid for, and access continues until then.
  • Credits pay for metered calls — one credit per natural-language query or validation check, five hundred per signed certification, or as stated at checkout at the time of purchase. Credit packs are one-off purchases. Credits do not expire.
  • When credits run out, metered calls answer HTTP 402 with a purchase link and are not performed; free tools keep working. We never spend credits you do not have.
  • Refunds. Subscription fees and credit packs are non-refundable, except where the law requires otherwise or where the service was unavailable through our fault for the period concerned — in which case we refund or credit the affected period.
  • Taxes are added where applicable. Prices are in US dollars.

5. What a result is — and is not

This section matters more than the rest. dVeracity issues trust in two layers that are kept cryptographically and legally separate, and you rely on each only for what it is.

  • Platform evidence. Validation results, quality scores, policy findings, readiness flags and data-integrity proofs are signed under dVeracity's own identity. They state that specified data existed in a specified state at a specified time, and what automated checks found. They are evidence, not opinion, and every attested result carries the assurance level and the reference to the evidence and validator version that produced it.
  • The verification opinion. dVeracity does not issue verification opinions and never appears as the issuer of one. A professional verification opinion — the decision and its assurance level — is issued only by an accredited verifier, signed under that verifier's own identity and keys. Where the platform presents a verifier's opinion, it presents it; it did not make it.
  • Standards and models are not ours. The Open Footprint standard and the O-DEF framework are published by The Open Group; PACT, the GHG Protocol, ISO standards and regulatory frameworks belong to their publishers. Our validators implement our reading of them at a given version, which is recorded with every result. A passing validation means the data met the checks we ran; it is not a statement that the data is true, complete, or compliant with any law.
  • No professional advice. Nothing the service produces is legal, accounting, audit, assurance or regulatory advice. Decisions about what to report, to whom, and under which regime remain yours and your advisers'.

6. Your data and our data

  • Yours stays yours. You keep all rights in data and documents you submit. You grant us a licence to process them to provide the service to you — including automated extraction, validation and storage in your tenant — and to keep what regulation requires us to keep, as set out in the Privacy Policy.
  • Residency and sovereignty are decided per tenant; see the Privacy Policy, section 4. Tell us before onboarding if you need a specific region.
  • Ours stays ours. The service, its software, the O-DEF registry and semantic annotations we maintain, our validators, indexes, documentation and marks are ours or our licensors'. You may use them only to use the service. Reading the reference layer through the API does not license you to republish it as your own.
  • Open source. The dVeracity MCP client and our Open Footprint implementation repository are published under the Apache License 2.0; that licence, not these terms, governs your use of that code.
  • Results you receive — validation findings, query answers, signed evidence — you may use for your own reporting and disclosure, including passing them to your verifier, provided you do not strip the assurance level, version or signature from an attested result.

7. Acceptable use

You agree not to:

  • submit data you have no right to submit, or personal data the verification does not need;
  • attempt to obtain credentials, tokens or data belonging to another account or tenant, or probe the isolation between tenants;
  • circumvent metering, call ceilings, consent or scope enforcement, or reverse-engineer the service except as the law allows;
  • present platform evidence as a verification opinion, or alter a signed result;
  • use the service to build a product that primarily republishes our reference layer;
  • use the service in breach of law, including sanctions and export-control law.

Security researchers acting in good faith are welcome to report findings to contact@dveracity.com; please do not test against other customers' data.

8. Suspension and termination

  • You may close your account at any time. Deletion of your data then follows the Privacy Policy, subject to what the regulation of your jurisdiction obliges us to retain.
  • We may suspend an account, key or connected agent immediately where we reasonably believe it is being used in breach of section 7, poses a security risk, or is in arrears, and will tell you why unless the law prevents it. We may terminate for a breach that is not cured within thirty days of notice.
  • Suspension does not delete your data; termination triggers the retention rules above. Sections 5, 6, 9 and 11 survive termination.

9. Warranties and liability

We will provide the service with reasonable skill and care. Beyond that, the service is provided “as is”: we do not warrant that it is uninterrupted or error-free, that a validation catches every defect, or that a passing result will be accepted by any verifier, regulator or counterparty. These terms carry no service-level commitment; where an Enterprise customer has a separate written service-level agreement with us, that agreement prevails over this paragraph for the matters it covers.

To the extent the law allows, neither party is liable to the other for indirect or consequential loss, and our total liability under these terms is limited to the amounts you paid us in the twelve months before the event giving rise to the claim. Nothing limits liability for fraud, for death or personal injury caused by negligence, or for anything that cannot be limited by law.

10. Changes

We update these terms by changing the effective date at the top. For changes that materially reduce what you get or increase what you pay, we give account holders at least thirty days' notice by email, and you may cancel before they take effect and receive a pro-rata refund of any prepaid, unused period. Price changes apply from your next billing period.

11. Governing law

These terms are governed by the laws of the State of Delaware, United States, without regard to conflict-of-law rules. Before either of us starts proceedings, we each agree to raise the dispute in writing and try in good faith to resolve it within thirty days. After that, the state and federal courts located in Delaware have exclusive jurisdiction, and each of us submits to them — except that either party may seek an injunction in any competent court to protect its intellectual property or confidential information. Where mandatory consumer law in your country gives you additional rights or a different forum, those rights are unaffected.

12. Contact

dVeracity Inc., 226 Skylark Pt, Jupiter, FL 33458, USA. contact@dveracity.com — Support.