Privacy Policy

1. Information HORNFI may process

• Public blockchain information: wallet addresses, contract addresses, transaction hashes, token balances, Arena backing, claims and other activity available on BNB Smart Chain.
• Account and profile information: authentication identifiers, email address when provided through sign-in, display name, profile image, username, bio and other profile fields you choose to publish. HORNFI may also store the public wallet addresses linked to your signed-in account so an existing social session can be restored without repeated wallet-signature prompts.
• Community content: posts, comments, reactions, follows, reposts, project calls and similar social activity you submit through HORNFI.
• Project information: token names, symbols, descriptions, websites, social links, categories, images, banners and other creator-supplied launch or Arena metadata.
• Technical information: browser/device information, network requests, error logs, analytics events, theme/settings data and similar information needed to operate, secure and improve the service.

2. Wallet information and private keys

For an external wallet connected through the wallet interface, HORNFI receives the public address and transaction/signature results needed to operate the application. HORNFI does not receive the external wallet's private key or seed phrase.

The optional embedded HORN wallet works differently. Email or Google sign-up automatically creates a first wallet account in the browser, and a signed-in user can create or import additional wallet accounts. Each wallet's private key and, when available, recovery phrase is encrypted locally using AES-GCM and stored in the browser's IndexedDB together with a non-exportable device key. If you enable Secure Cloud Backup, the browser encrypts the complete wallet vault again with a random vault key before upload. Firebase receives ciphertext, initialization values, wrapped vault keys, passkey credential metadata and backup timestamps; HORNFI does not upload readable private keys, seed phrases or the readable HORN recovery code. A supported WebAuthn passkey or the user's recovery code is used on the device to unwrap the vault key.

HORNFI staff or support should never ask you to send a private key, seed phrase or HORN recovery code. Recovery material entered into the wallet manager is processed by the browser. Anyone who obtains wallet recovery material may be able to control or restore the wallet.

3. How information is used

• Provide wallet, launchpad, trading, Arena, claims, profile and community features.
• Display public project and market information and associate creator/backer activity with public wallet addresses.
• Authenticate users, maintain sessions, keep account settings synchronized and, when enabled, store zero-knowledge encrypted wallet-vault backups.
• Store and deliver creator media and community content.
• Detect abuse, spam, fraud, malicious uploads, unauthorized activity and technical failures.
• Measure product performance and improve reliability, usability and security.
• Comply with applicable legal obligations and enforce HORNFI's Terms of Service.

4. Public blockchain data

Blockchain transactions are public by design. Once a transaction is confirmed, HORNFI generally cannot edit, hide or delete the on-chain record. Wallet addresses can also become associated with other public information through third-party explorers, analytics tools or your own disclosures.

5. Service providers and third parties

HORNFI relies on third-party infrastructure to provide parts of the service. Depending on the feature used, information or requests may be processed by services such as:

Third-party services operate under their own terms and privacy practices. HORNFI does not control how independent blockchain protocols or external wallet providers process information.

6. Local storage, IndexedDB and similar technologies

HORNFI may use browser storage to remember theme preferences, session state, wallet-related preferences and other application settings. The embedded HORN wallet uses IndexedDB for encrypted local wallet material and device-specific smart-session keys. Clearing browser data removes those local copies. If Secure Cloud Backup is enabled, a passkey or HORN recovery code may restore the encrypted vault on another device; otherwise you must retain each wallet's own recovery phrase or private key.

7. Retention and deletion

Off-chain account and application information may be retained while needed to provide the service, protect users, resolve disputes, meet legal obligations and maintain platform integrity. Locally stored wallet material remains on the device/browser profile until it is replaced or cleared. Public blockchain data cannot generally be deleted by HORNFI.

Where applicable law gives you rights to access, correct or request deletion of off-chain personal information, you may contact HORNFI through the official channels published on hornfi.fun or the official X account @hornfi. Requests cannot erase public blockchain records controlled by the network.

8. Security

HORNFI uses technical safeguards appropriate to the current testnet product, including local AES-GCM encryption, optional passkey-protected encrypted backups and revocable selector-scoped smart-session keys. No website, browser storage system, passkey provider, wallet software or blockchain application can guarantee absolute security. You remain responsible for securing your devices and recovery material.

9. Children and legal eligibility

HORNFI is not designed for children. You should use HORNFI only if you are legally permitted to use blockchain and digital-asset software in your jurisdiction and have the legal capacity to accept the Terms of Service.

10. Changes to this policy

HORNFI may update this Privacy Policy as the product, infrastructure, network deployment or legal requirements change. Material updates will be reflected by changing the date shown above. Production or mainnet services may require additional disclosures before launch.