Privacy & Blockchain Transparency Policy

Scope and document basis

This policy covers the HIVE Wallet product website, its desktop-package delivery, consent and language preferences, local demo assistant and external links. Technical statements are informed by the HiveWallet.net Advanced Technical and Operational Report; this policy does not govern the Hive blockchain, an RPC operator, GitHub, Hive Engine or another linked service.

Product-specific privacy statements below are attributed to the report dated 1 September 2026. Website-specific statements are based on inspection of the current project code. This distinction avoids treating historical source observations as guarantees about the present hosting environment.

Identity of the responsible operator

The report found that the historical official privacy statement did not identify a legal entity, jurisdiction, processor list, retention schedule, rights procedure, breach contact or version history. The current project materials likewise do not provide a verified production operator name, postal address or privacy email.

A production operator remains responsible for adding accurate identity and contact details required by applicable law before collecting support messages, connecting analytics or deploying through a hosting provider. This policy does not invent missing identity information.

Historical no-collection statement

According to the report, the official HiveWallet.net privacy text stated that the developer did not collect or store information and that analytics were disabled in both the application and website. The report treated that as a favorable data-minimization claim.

The same report also identified its limits: the statement was extremely short and lacked operational details needed to evaluate hosting logs, support communication, retention, recipients and rights. It should therefore be understood as a historical developer statement, not an independent technical guarantee of anonymity.

• Historical claim: developer collection and storage were denied
• Historical claim: application and website analytics were disabled
• Not established: complete present-day data-flow or server-log verification

Data used by this product website

The client interface can operate without an account registration, wallet connection or blockchain login. It does not ask for a Hive account name to display the report and does not call a Hive RPC endpoint as part of normal page rendering.

The website remembers consent and language preferences in localStorage. These records remain in the browser and are described in the Cookie & Local Storage Policy. No analytics, advertising or remote support integration is present in the audited client code.

• Consent category selections and update timestamp
• Selected interface language
• Temporary interface state such as open dialogs and chat messages while the page remains loaded

Hosting and security logs

Even when a site is static and contains no analytics library, its web server, content-delivery network, firewall or hosting control panel may process an IP address, request time, requested path, referrer, user-agent string, response code and security event. The project source cannot determine the production provider's exact log configuration.

The production operator should document the hosting provider, purposes, access controls, retention and any international transfers. Operational logs should be limited to delivery, security, abuse prevention and troubleshooting rather than repurposed for undisclosed profiling.

Demo assistant and contact fields

The HIVE Guide is a local demonstration. Questions are matched against predefined responses in the browser. After the demo delay, the interface can display message and email fields, but the audited component does not submit, transmit or persist their contents.

Closing or reloading the page clears this temporary state. Because a future production contact service would materially change processing, it must not be connected without updating this policy with the recipient, purpose, lawful basis, retention, security and user-rights procedure.

• Current state: no network submission endpoint
• Current state: no localStorage record for chat text or email
• Safety rule: never enter a master password or private role key

Wallet credentials are outside scope

This product website does not need and must not collect a Hive master password, owner key, active key, posting key, memo private key, local wallet passphrase, wallet.json file, QR-encoded key or biometric template.

The report explains that the historical mobile wallet could store selected role keys in a locally encrypted wallet file and optionally retrieve its local passphrase through native keychain and biometric controls. Local storage on a device is not the same as sending credentials to this website, and neither mechanism replaces an independent recovery backup.

Hive is a public account network

Hive uses globally unique named accounts. Balances, transfers, votes, posts, delegations, authority structures, recovery account, witness or proposal activity and custom JSON operations may be publicly observable and linked over time.

A wallet interface cannot make confirmed on-chain data private or erase it. Reusing one account across financial, social, governance and dApp activity creates a rich public profile. Operational privacy may require purpose-specific accounts, careful memo practices and awareness of account relationships.

• Public does not mean harmless or context-free
• A local key does not make a public transaction anonymous
• Deleting the app or browser data does not delete blockchain history

Transfer memo privacy

The report states that transfer memos are public by default. Hive supports a recognized encrypted-memo format using memo keys, but sender, recipient, asset, amount, time and transaction relationships remain visible.

A leading marker or lock icon is not sufficient proof that an installed build encrypted the memo correctly. Never put passwords, private keys, identity documents, recovery secrets or other irreversible sensitive information in a transfer memo.

RPC node metadata

The report identifies HiveWallet.net as a light client and https://api.hive.blog as the default endpoint in reviewed source. An RPC operator can observe network metadata, timing, queried accounts and request patterns and can return stale or incomplete data.

Selecting a custom node may reduce exposure to one public operator but transfers TLS, availability, synchronization, firewall and maintenance responsibilities to the user. Private keys should never be sent to an RPC node; signing should remain on the user's trusted device.

• Verify material-value results with a second trusted source
• Display and inspect the selected endpoint
• Treat node choice as both an availability and privacy decision

Embedded dApps and persistent approvals

The historical wallet included an embedded browser and a Keychain-compatible request bridge. A visited site can provide transaction intent and parameters while the wallet maps the request to a Hive operation, selects a role key and asks for approval.

That bridge is compatibility code, not a security or privacy endorsement. A website can observe browsing behavior, associate it with an account, request custom JSON operations or be compromised after earlier use. Persistent approvals should be minimized, reviewed and cleared when no longer required.

QR codes and deep links

The report documents QR generation and scanning plus hive://, hivewallet:// and hivewallet.net link handling. These channels reduce typing but can prefill accounts, keys, transfers or signing routes and therefore accept attacker-controlled input.

A QR code is a data container, not an authenticity seal. The confirmation screen must remain authoritative, and every prefilled account, symbol, amount, memo, operation and requested authority must be rechecked before approval.

• Do not scan a private-key QR into an unverified application
• Do not assume a familiar logo authenticates a deep link
• Cancel when the effective operation differs from your intent

Downloads, external websites and source links

The download section serves three deployment-provided desktop packages directly from the same website origin. A normal file request can be recorded by the hosting provider with technical delivery data such as IP address, time, requested filename, response status and user agent. The website does not request a Hive account or private key to deliver a file.

The section also links to evidence named in the report, including the historical product domain, public repository, secondary store record and Hive wallet directory. Opening one of those destinations creates a direct relationship with its operator under that operator's own privacy terms. Verify the destination, TLS connection, publisher identity and policy before submitting information or downloading software.

Retention, deletion and data minimization

Browser preference records remain until changed or cleared and have no automatic expiry in the current implementation. Demo chat text and email remain in page memory only and disappear on reload. Server-log retention is not established because the production hosting configuration is not part of the report or repository audit.

The production principle should be minimization: collect only what is needed for a declared purpose, restrict access, define a deletion schedule and avoid combining website identifiers with public Hive accounts unless the visitor knowingly requests such a function.

• Clear site data to remove local preferences
• Do not expect deletion to affect public Hive records
• Contact each external operator for data it independently controls

Security safeguards and residual risk

The static build applies a restrictive content security policy, blocks framing, limits browser permissions and does not connect optional tracking services. These controls reduce common website risks but cannot guarantee absolute security or protect against a compromised host, DNS record, browser, extension or device.

The report's highest-impact wallet risks remain owner or master credential compromise, a malicious binary and deceptive dApp authorization. The most likely risks for aging software include failed installation, outdated dependencies, RPC incompatibility and inability to reproduce a trusted signing environment.

Choices, rights and unresolved contact details

You can browse the report without enabling optional categories, clear browser preferences, avoid external links and refrain from entering any voluntary information. Rights such as access, correction, deletion, restriction, objection or portability depend on applicable law and on whether a production operator actually processes identifiable data.

The project does not contain a verified privacy contact or operator identity, so this policy cannot provide an invented rights channel. Those details must be completed before enabling a real contact form or optional data service. Blockchain records and data controlled independently by RPC nodes or external sites require separate handling.

Changes and version control

Material changes to hosting, analytics, support submission, wallet connectivity, RPC calls, embedded content or third-party services require a new policy review. The revision date should change, and any consent affected by a new purpose should be requested again.

This version reflects the report analysis date of 1 September 2026 and the inspected website implementation as revised on 4 September 2026. Future maintenance or distribution evidence may change the product assessment but must be independently verified before publication.