Skip to content
zHezarFoundation / Public release

Legal & Trust / Foundation index

Trust is explanation. Policy is authority.

Public principles can make zHezar understandable today. Binding terms, permissions, duties, and acceptance require approved documents and operating systems that do not yet exist.

Browse current trustPolicy status
Plain-language trustExplain what can be shown now.
Governing documentCreate rights only after approval.

No acceptance occurs here.

Current notice

No binding policy active

This index is not Terms of Service or legal advice.

It does not identify a legal entity, governing law, venue, policy version, effective date, legal contact, acceptance state, or authorization for account, competition, commerce, product, ownership, or dispute behavior.

Available now

Five public explanations. One visible boundary.

These routes explain current evidence and intended principles. None replaces the governing document for a future action.

  1. 01

    Transparency

    Current evidence, public claims, and inactive product boundaries.

    Read Transparency
  2. 02

    Accessibility

    Current route evidence, equal-access principles, and open review work.

    Read Accessibility
  3. 03

    Privacy

    Static-site behavior, purpose limitation, and future data gates.

    Read Privacy
  4. 04

    How It Works

    The complete concept without turning future steps into active authority.

    Read How It Works
  5. 05

    Help

    Current self-service and the boundary around protected support.

    Read Help

Governing documents

Unavailable means unavailable.

Draft, internal-review, or professional-review work does not appear as an active policy and cannot collect agreement.

Document familyStateRequired before publication
General platform termsNot published

Entity, jurisdiction, eligibility, disputes, liability, changes, and termination require legal approval.

Privacy PolicyNot published

Production data inventory, purposes, providers, regions, rights, retention, and request operations require review.

Accessibility StatementNot published

Conformance target, supported technologies, independent review, known barriers, and accommodation operations remain open.

Competition and artist documentsNot active

Official Rules, submissions, licensing, compensation, evidence, appeals, tax, and payout are separately gated.

Commerce and customer policiesNot active

Payment, allocation, shipping, cancellation, returns, exchanges, refunds, and consumer disclosures await activation.

Product identity and ownership termsNot active

NFC, Claim, Ownership, transfer, corrections, provenance, and future marketplace authority remain separate.

Versioned authority

A real policy carries its own evidence.

Publication is more than adding a page. Every binding document must identify what it governs and preserve the history needed to understand change.

  1. 01

    Document owner and approving reviewer

  2. 02

    Stable identifier and exact version

  3. 03

    Publication and effective dates

  4. 04

    Material-change and archive history

  5. 05

    Required acceptance and withdrawal rules

  6. 06

    Feature and jurisdiction applicability

Before an action opens

Page, policy, enforcement, support, and review must agree.

A feature does not become safe or authorized because its interface exists. The governing document, backend enforcement, operations, professional review, recovery, and public explanation must be ready together.

Review current evidence