Skip to content
zHezarFoundation / Public release

Help / public guidance

Find the right path before sharing the details.

Start with current public guidance. Account-specific, order, security, legal, safety, and private-evidence matters need controlled routes that are not open during Foundation.

Browse current guidanceContact routing
Current public paths
  1. 01How It Works
  2. 02About
  3. 03Transparency
  4. 04Account access
  5. 05Contact

Protected mattersControlled route required

Service state

No live status source

No service incident is represented here.

This page does not claim that systems are healthy, monitored, incident-free, or operating to a response target. It contains static public guidance only.

Current self-service

Five useful paths. No empty article library.

Help search and topic categories will become useful when approved content volume grows. Today, direct links are clearer.

  1. 01

    Understand the complete concept

    Follow discovery, participation, physical form, scan, claim, and history without confusing their authority.

    Open How It Works
  2. 02

    Learn why zHezar exists

    Read the mission, physical-product priority, artist relationship, and evidence-before-expansion direction.

    Open About
  3. 03

    Review current evidence

    See what the Foundation site can demonstrate and which product, participation, and ownership systems remain closed.

    Open Transparency
  4. 04

    Understand account access

    Review why sign-in is closed and what security, privacy, and recovery must exist before it opens.

    Open Account access
  5. 05

    Route a public inquiry

    Choose a public business or general-support channel without placing protected details in ordinary correspondence.

    Open Contact

Choose by matter

Public guidance and protected support are different systems.

Public now

General guidance and inquiry routing

Use the five public paths above or review Contact for the purpose of each public mailbox.

Not open

Authenticated and specialized cases

Account, orders, payments, security, copyright, legal, safety, Claims, Ownership, appeals, and private evidence need controlled intake.

Authority boundary

A message is not a protected record

An email address, thread, display name, logo, or case-like reference cannot grant staff authority or confirm an outcome.

Security reminder

Keep secrets out of support messages.

  • Never send a password, recovery code, or reusable authentication code.
  • Never send complete payment credentials through email or a public form.
  • Do not send identity documents, private Artwork evidence, or cryptographic material through ordinary correspondence.
  • Verify a protected route independently before following a link or sharing evidence.