Product and creative context
Artwork title, artist attribution, garment details, release context, and selected product history can be public when the owning system approves them for public display.
Privacy notice / version 1
Looking at a garment should not require handing over your identity.
This Privacy Notice explains how zHezar, operating from Georgia, United States, handles information for public browsing and protected accounts. It is effective August 22, 2026.
One important distinction
Static Firebase HostingPublic reading still uses the network.
Your browser requests the site from Firebase Hosting, and infrastructure may process ordinary delivery and security information. The statements on this page are deliberately limited to the zHezar application behavior we can currently verify.
Today
Four practical facts for visitors.
These statements describe what the current public Website V2 experience does—not what every future zHezar feature may eventually require.
- 01
Reading stays public
The public Home, Shop, About, product information, and trust pages can be read without creating an account.
- 02
No advertising profiles
The public application does not initialize advertising or cross-site personalization tools.
- 03
Account access is gated
Public account creation remains unavailable until the separate security and operating gates pass. This notice does not open registration by itself.
- 04
Protected systems stay separate
Authentication, sessions, account setup, and private profile information are handled separately from ordinary public product pages.
Public product / protected person
A product can have a public story without exposing the person behind a private relationship.
Artist credit, release details, and privacy-safe product history are different from account identity, payment records, addresses, private ownership details, support evidence, or security information.
Personal and operational records
Account identity, contact information, payment, address, private owner data, support evidence, security signals, and private submissions should stay behind appropriate access controls.
Protected accounts
Collect only what account access needs.
These categories describe the reviewed technical design. Google or Apple sign-in begins only after you choose a provider, and public account creation remains closed until the operating process is proven.
- 01
Identity
Google or Apple provider identifiers and verified contact details are used to establish and protect one canonical account.
- 02
Account setup
A username, age-eligibility record, accepted policy versions, notification education, and optional interests support account completion.
- 03
Security
Session references, sign-in events, abuse limits, and security signals are used to protect the account and the service.
- 04
Public profile
A username or profile detail is public only when the product and the account’s privacy settings permit that exact field.
- 05
Requests and support
Verified access, correction, closure, deletion, and security requests require a controlled support process.
How information is handled
Purpose, restraint, and a verified request path.
zHezar limits personal information to the service, safety, support, and legal purposes described here. A feature-specific notice may add details before a future feature collects additional categories.
- 01
Service providers
zHezar uses providers such as Google, Apple, Firebase, and hosting or security vendors only for the service functions they support. Their own policies also apply to their services.
- 02
Sharing boundary
zHezar does not sell personal information or use account data to build third-party advertising profiles. Information may be disclosed to service providers, to protect people or the service, or when legally required.
- 03
Retention
Information is kept only as long as needed for the stated purpose, security, transactions, disputes, legal duties, or product provenance. Retention periods vary by record type.
- 04
Your choices
You may request access, correction, account closure, or eligible deletion. A request may require recent sign-in or another proportionate verification step before protected information is changed or released.
- 05
Age boundary
zHezar public accounts are for people age 18 or older. Do not create an account if you are under 18.