Privacy & Data
ZipHype is designed so that your private social preferences stay under your control rather than becoming a ZipHype user database. Public blockchain activity remains public, while private settings live in your encrypted ZipHype vault.
No ZipHype user database
ZipHype does not maintain a server-side database of your follows, muted accounts, hidden or reported posts, feed preferences, or customization settings. Those preferences are stored in your encrypted .ziphype vault and in its encrypted local browser copy.
ZipHype's server-side feed layer may temporarily proxy or cache public ZipCoin feed data for performance. That public cache is not a private user profile or behavioral database.
Your vault, your responsibility
Your vault is encrypted and belongs to you. ZipHype cannot recover a lost vault password, a deleted backup, or a lost wallet on your behalf.
On a trusted device, ZipHype may keep the encrypted vault together with a non-extractable browser key in local browser storage so the vault can reopen automatically. Using Lock Vaultremoves that trusted-device key from the browser.
- Keep a safe backup of your .ziphype vault file.
- Protect the password used to unlock your vault.
- Protect your wallet, seed phrase, and device access.
- Lock the vault on a device you no longer want to trust before giving that device to someone else.
Public blockchain activity
ZipCoin posts, burns, transaction hashes, public wallet addresses, and Hype actions can be recorded on Ethereum and are not private ZipHype data. Blockchain transactions are public and generally permanent once confirmed.
When you make a public post, your wallet address can be part of that public record. ENS names and avatars may also be resolved from public Ethereum data where available.
Anonymous ZipCoin posts
When the ZipCoin feed identifies a post as anonymous, ZipHype does not intentionally associate that post with a wallet identity or use it to build a hidden identity profile.
Anonymous posting does not mean that every external network, blockchain, wallet, or infrastructure provider is unable to observe metadata outside ZipHype. ZipHype does not control those independent services.
Other services
Using ZipHype can involve services that exist outside ZipHype, including your wallet software, Ethereum RPC infrastructure, the ZipCoin feed/indexer, ENS, and sites you choose to open such as Etherscan. Those services can have their own data practices.
ENS avatars may be hosted by third parties. When ZipHype displays one, your browser may contact that external host directly to load the image, which can expose ordinary request metadata such as your IP address to that provider.
Tracking
ZipHype is designed to avoid behavioral tracking, fingerprinting, and unnecessary collection of user-specific activity. The goal is to provide the interface and public feed infrastructure without turning private social behavior into server-owned user data.
Ordinary hosting and network infrastructure may still process basic request or security metadata as part of operating a web service.
Transactions cannot be undone
ZipHype can hide content from your own interface, but it cannot delete confirmed blockchain posts, burns, or Hype transactions. Always review wallet prompts before signing.