Private keys stay with you.

Data kept on your computer

Hive stores settings, task state, logs, encrypted wallet material, and optional Relay credentials in your operating system's application-data directory. Wallet private keys, keystore JSON, passphrases, and recovery phrases are not QSDM Account data.

Hive analytics are disabled and Hive contains no advertising tracker.

Optional account data

When you choose QSDM Account, the service processes an email address and/or Telegram OpenID identity, creates a browser session, and stores public wallet addresses you explicitly link. You may attach both sign-in methods to one profile; QSDM rejects identities already owned by another profile instead of silently merging accounts.

• Identity display values are encrypted at rest.
• Login tokens and session tokens are stored as keyed hashes.
• Email uses a short-lived one-time link. No reusable account password is stored.
• A wallet is linked only after Hive approves an ML-DSA ownership signature.

QSDM Account cannot sign, spend CELL, or recover a wallet.

Network and ledger data

Features you start may send public wallet addresses and keys, signed transactions, task actions, mining proofs, resource descriptions, workload receipts, chain requests, and integration-link proofs. Reference infrastructure may retain ordinary security logs such as source IP, request time, endpoint, status, and rate-limit events.

Accepted transactions and proofs are replicated ledger records and generally cannot be deleted without invalidating the ledger.

Your choices

QSDM Account is optional. You can use the self-custody wallet and Hive without an account profile. From the account dashboard you can unlink public wallets, sign out other browsers, or delete the account identity and its public wallet links. Account deletion does not delete Hive, wallet keys, CELL, or accepted ledger records.

For account-data access questions, contact ops@qsdm.tech from a verified identity associated with the account. Never email a wallet secret or backup.

Security reports

Do not put exploit details, credentials, personal data, or wallet secrets in a public issue. Use the repository's private GitHub Security reporting channel.