United States · Discovery / limited fit

Legal boundaries for United States

Understand current legal boundaries for Verified.Tools in United States, including evidence records, review paths, and claims outside the beta boundary.

What United States teams should confirm

These pages describe the current product boundary. They do not replace legal advice or transaction-specific review.

What we can describe

  • Explain provenance, workflow records, and operational audit value.
  • Use US terminology without implying EU-style trust-service status.

What we do not claim

  • Do not import eIDAS/QES language as if it were the US offer.
  • Do not imply notarisation or regulated trust-service equivalence.

What to confirm

  • US market rollout remains selective and use-case dependent.
  • Current materials do not provide legal advice or guarantee jurisdictional sufficiency.

Legal boundaries for United States

This page explains the current boundaries in plain language. It does not replace customer legal advice, and it does not promote unavailable trust-service status.

  • Explain provenance, workflow records, and operational audit value.
  • Do not import eIDAS/QES language as if it were the US offer.
  • US market rollout remains selective and use-case dependent.

When to ask for review

Use the legal contact path when a customer needs jurisdiction-specific advice, regulated trust-service positioning, or transaction-specific sufficiency reviewed.

Common questions

Does this page provide legal advice?

No. The page explains product capability and claim boundaries. Customers should obtain legal advice for transaction-specific sufficiency.

What can Verified.Tools say in United States?

Explain provenance, workflow records, and operational audit value. Use US terminology without implying EU-style trust-service status.

What claims are deliberately avoided?

Do not import eIDAS/QES language as if it were the US offer. Do not imply notarisation or regulated trust-service equivalence.