1. Identity and authentication

Byhnex is designed around wallet authentication. The current product stack shows signature-based login and wallet authorization flows rather than email-password accounts. Your wallet address may therefore function as your account identifier across parts of the ecosystem.

2. Public blockchain data

Transactions, wallet addresses, escrow state accounts, vault accounts, token transfers, and related on-chain events may be public by design on the underlying blockchain. Byhnex cannot make blockchain records private after publication.

3. Off-chain records

The backend currently stores operational records related to contracts, profiles, messages, payment traces, signed actions, and activity logs. Additional records may evolve over time as new governance modules are introduced.

4. Reputation and work history

Byhnex is built to expose verifiable work history, contract outcomes, and reputation signals. Users should assume that some activity related to completed work and transaction history may be visible to counterparties or the public, depending on where the data is stored.

5. What users should avoid publishing

Do not place passwords, recovery phrases, private keys, confidential client files, regulated personal data, or any secret information in wallet memos, public messages, contract metadata, or blockchain transactions. On-chain publication is generally irreversible.

6. Security responsibilities

You are responsible for wallet security, device security, and transaction review before signature. Byhnex cannot recover assets lost through compromised wallets, malicious approvals, or user-signing mistakes outside the protocol rules actually enforced by the deployed system.

7. Policy status

This page is an operational privacy notice for the current Byhnex vitrine. It should be completed with your legal entity details, contact address, hosting information, cookie tooling, and jurisdiction-specific notices before production launch.