Cookie & Local Storage Policy

Purpose, scope and evidence boundary

This policy applies to the HIVE Wallet product website and its desktop-download interface. Its technical disclosures are informed by the HiveWallet.net Advanced Technical and Operational Report, while this policy covers only browser-side preferences implemented by the current website.

The report states that the historical official privacy notice claimed analytics were disabled in both the application and website. This site's implementation was inspected separately so that the policy describes what the current interface actually does rather than copying that historical statement as a present guarantee.

No HTTP cookies set by the interface

The current website code does not create document.cookie values and does not install a cookie-management or analytics vendor. The consent interface uses the browser's localStorage mechanism, which remains on the device for the relevant site origin until it is changed or cleared.

The familiar term ‘cookie banner’ is retained because visitors recognize it, but the exact technology currently used by the interface is local storage. Hosting infrastructure may still use operational mechanisms outside this static source; any production operator must disclose such changes before deployment.

• No advertising cookie is created by the current interface
• No analytics library is loaded by the current interface
• No wallet credential is stored by the consent component

Strictly necessary preference records

Two local records support requested interface functions. They are treated as necessary because the website otherwise cannot remember the consent choice or selected language between visits.

Blocking local storage does not prevent access to the report. The preference may then last only for the current page session and the banner may reappear on a later visit.

• hive-wallet-cookie-consent: stores the selected categories, choice mode and ISO-format update time
• hive-wallet-locale: stores the selected interface language code; the audited libraries provide every language listed in the selector
• Necessary storage contains no account name, balance, transaction, private key or wallet file

Consent record structure

The consent record is a JSON object containing necessary, functional, analytics and marketing boolean values, a choice value of all, necessary or custom, and an updatedAt timestamp. The necessary value is always true because it records the visitor's instruction.

Selecting Accept all records affirmative choices for every displayed category. Selecting Decline optional or Accept necessary records only necessary storage. Saving custom preferences records the switches exactly as selected.

Functional category

Functional storage would support optional interface conveniences beyond the minimum needed to remember consent and language. The audited website does not currently connect an additional functional vendor or create an additional functional record when this switch is enabled.

If a future feature needs such storage, the policy and preference center must identify its name, purpose, duration and recipient before activation. Previously recorded consent must not be used to conceal a materially different purpose.

Analytics category

No analytics script, analytics request or analytics identifier is implemented by the current client code. The switch records the visitor's preference only. It does not activate measurement by itself.

This implementation position is consistent with the report's observation that the historical official privacy statement claimed analytics were disabled. The report also notes that the old statement was too short to identify a legal entity, processors, retention, rights or version history; this policy does not treat that statement as proof about every server or historical binary.

• No visitor profile is created by the audited interface
• No wallet account is linked to an analytics identifier
• No optional analytics request is sent after Accept all

Marketing category

No advertising pixel, campaign tracker, behavioral advertising service or cross-site marketing identifier is connected in the audited build. Enabling the switch stores the preference but activates no marketing code.

Before any future marketing integration, the production operator must update this policy, identify the provider and purpose, explain retention and transfers, and obtain any consent required by applicable law.

Duration and deletion

The current localStorage records do not contain an automatic expiry value. They persist for the site origin until replaced by a later choice, removed by a website update, or cleared through browser controls. Private or temporary browsing modes may remove them earlier.

You can delete both records by clearing site data for this domain. Deletion resets the remembered choice and may cause the consent banner and default language to appear again. It does not alter public Hive blockchain records or data held by external websites.

• Browser settings can block or clear local storage
• Clearing storage withdraws the remembered optional preference on this device
• Choices do not automatically synchronize between browsers or devices

External links, RPC nodes and embedded dApps

Links from the HIVE Wallet website may open external sources such as GitHub, the Hive wallet directory and historical distribution records. Those destinations control their own cookies, logs and privacy practices; this site's consent record does not authorize or restrict them.

The report separately explains that the historical mobile wallet queried remote Hive RPC nodes and included an embedded dApp browser. RPC operators may observe network metadata and queried accounts, while embedded websites may connect browsing behavior to a public Hive account. Those application-layer risks are not managed by this website's cookie preferences.

Wallet credentials and blockchain information

Consent storage is not a wallet, backup or recovery mechanism. It must never contain a Hive master password, owner key, active key, posting key, memo private key, local wallet passphrase or biometric record.

Hive account names and on-chain operations are public by design. Removing browser preferences cannot delete, reverse or anonymize a transaction, vote, delegation, authority change, custom JSON operation or public memo already recorded by the network.

Changing preferences

Use Cookie settings in the footer to reopen the preference center before a consent record exists, or clear this site's local data through the browser to reset a saved instruction. The interface provides Accept all, Decline optional, Accept necessary and granular custom controls.

A production deployment should keep a permanently accessible preference link even after the banner closes. If optional services are introduced, withdrawal must be as easy as acceptance and should prevent future optional processing without claiming to erase data already lawfully retained elsewhere.

Policy changes and verification

This policy should be reviewed whenever storage names, connected vendors, purposes or retention behavior change. Material changes require an updated revision date and, where necessary, a renewed visitor choice.

The current statements are based on inspection of the website source and the report dated 1 September 2026. They do not certify every hosting configuration, browser extension, external destination or historical HiveWallet.net binary.