Last updated: June 6, 2026
Abyss does not collect, store, or process personal data. There is no backend server. There is no database. There are no analytics. Your messages are encrypted on your device and relayed peer-to-peer. We cannot read them even if we wanted to.
Abyss does not collect or store:
Note on IP addresses: The Abyss relay node sees IP addresses at the network transport level (WebSocket connections), as is inherent to any internet service. These are not logged, stored, or associated with wallet addresses or message content.
The following data is stored locally on your device (browser localStorage and IndexedDB) in unencrypted form. Encryption keys and identity data never leave your device:
| Data | Purpose | Stored where |
|---|---|---|
| Wallet address | Your identity in rooms | Device only (localStorage) |
| Nickname | Display name you chose | Device only (localStorage) |
| Room keys | AES-256 keys to decrypt channels | Device only (localStorage) |
| Member lists | Who is in each room | Device only (localStorage) |
| Message cache | Offline access to recent messages | Device (IndexedDB) + relay node (encrypted) |
Clearing your browser data permanently deletes the local copy of this information. There is no backup or recovery for encryption keys.
Messages are relayed through the Waku peer-to-peer network. The Abyss project operates a relay node to ensure message delivery and availability. This node stores encrypted message payloads for offline delivery (Waku Store protocol). Specifically, the relay node can see:
The relay node also sees IP addresses at the transport level (WebSocket connections), as with any internet service. These are not logged, stored, or correlated with message content.
The relay node cannot see: message text, sender identity, nicknames, wallet addresses, or any other content inside the encrypted payload. Sender and recipient information is sealed inside the AES-256-GCM encrypted message before it leaves your device.
When you connect a wallet, the App communicates directly with your wallet software (MetaMask, WalletConnect, etc.) to request a signature. The wallet provider's own privacy policy applies to that interaction. Abyss does not receive or store your private key or seed phrase.
The marketing website at enterabyss.chat is a static page. It does not use cookies, analytics services, tracking pixels, or any form of user tracking, and it collects no visitor data of its own.
Two files are loaded from third parties, and those parties see your IP address simply because your browser requests the file from them: font files from Google Fonts, and the animation library from unpkg. Neither is used for tracking, and neither is given any information about you beyond the request itself.
The App integrates with external services that have their own privacy policies:
Abyss is not directed at anyone under the age of 18. We do not knowingly interact with minors. Because we collect no data, we have no way to verify age.
We may update this policy when the App changes. The "Last updated" date at the top reflects the most recent revision. Continued use of the App constitutes acceptance.
Questions about this policy can be directed to support@enterabyss.chat or @abysschat on X.