Trust Center

Start with what the evidence can establish.

HempDash works in a category where a polished claim can travel farther than its source. This page records the method behind our public claims, the current boundaries of the public product, and the questions that still belong to people.

Public trust record reviewed August 15, 2026

Read this first

What HempDash does not prove

When a HempDash record, finding, or verification result is available, it is evidence about a bounded question. It is not a substitute for the wider decision.

No whole-product conclusion
A COA finding addresses a named requirement and the document supplied. It does not decide every fact about a product or transaction.
No legal conclusion
HempDash does not provide legal advice or determine how a requirement applies to a particular business, product, or dispute.
No regulator outcome
A record cannot predict how an agency, court, inspector, provider, insurer, or other reviewer will decide a matter.
No source identity from extraction alone
Reading fields from an uploaded COA does not authenticate the issuing laboratory or establish that the report matches the item in hand.
No company-performance claim
The public product surfaces do not establish customer adoption, revenue, market share, or future company performance.

Claim methodology

How a public claim earns its place

Capability copy is checked against a versioned evidence record. Publishability is calculated from the underlying facts; a writer cannot mark a claim approved in page copy.

  1. 01

    Name one bounded claim

    A claim describes one independently checkable capability or availability fact, not a bundle of outcomes.

  2. 02

    Record the evidence

    The record captures implementation, tests, deployment, runtime configuration where relevant, a production probe where relevant, provenance, and review date.

  3. 03

    Fail closed

    A missing, failed, unknown, or stale fact withholds the capability claim from a gated surface until the evidence is refreshed.

  4. 04

    Keep the qualifier

    When the evidence supports only a narrower statement, the public wording stays inside that narrower boundary.

Evidence signing and public checks

Current public evidence surfaces

Anonymous COA check

A visitor can upload a COA without an account and receive findings attached to individual requirements. The checker does not return an overall verdict.

Open the COA check →

Public seal verification

A third party can check a HempDash seal credential without an account. The check validates the credential's signature and record binding; it does not establish product quality or a wider product conclusion.

See the network boundary →

Public record

Details and current gaps

Each statement is scoped to the surface it describes. For the site-wide legal terms, read the Privacy Policy and Disclaimer.

Review processHuman judgment stays visible
The public checker locates fields and reports requirement-scoped findings. NEEDS REVIEW and UNABLE TO DETERMINE are deliberate outcomes: they keep unresolved questions with the operator, counsel, laboratory, or other appropriate reviewer.
AI useAI locates fields in the public COA check
For that surface, the PDF is processed in memory and is not stored. Text extracted from the document is processed by an AI provider to locate fields. The finding remains bounded to the submitted document and named requirement.
Rule provenanceSources, dates, and posture travel together
The Texas authority pages render from a shared reviewed snapshot that keeps citation, source link, effective date, review date, and enforcement or litigation posture as separate fields. A review date is not a claim that the rule cannot change afterward.
RetentionRetention depends on the surface
First-party site usage events are kept for 12 months; contact details are kept while HempDash is in touch and as needed for the stated purposes. The Privacy Policy is the source for those site-wide terms. Document-handling terms for a gated product surface appear with that surface when its capability claim is publishable.
Service providersName the handoff that is public
The Privacy Policy identifies the service providers used for the public site and contact flows. A separate comprehensive public subprocessor register is not currently published. Product-surface provider disclosures appear with the relevant gated surface when its capability claim is publishable.
StatusPublic status is surface-specific
The current public surfaces are linked above. A standalone public service-status page is not currently published, so this page does not imply one exists.
Security claimsNo certification by implication
No third-party security certification is claimed on this page. The evidence-signing statement above is about verification of a specific credential, not a general security assessment of HempDash.
LimitationsUnknown is a real state
Missing source context, unreadable documents, pending enforcement posture, unavailable integrations, and stale evidence remain visible rather than being rewritten as positive outcomes.

Found a trust-record mismatch?

Send the page, claim, and source you believe conflict. We will review the evidence record and correct the public wording when the facts require it.

Email the founder →