← Back to Abyss

Privacy Policy

Last updated: June 6, 2026

The Short Version

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.

1. What We Don't Collect

Abyss does not collect or store:

  • Email addresses, phone numbers, or real names
  • Message content (messages are end-to-end encrypted)
  • Contact lists or address books
  • Device identifiers or fingerprints
  • Usage analytics or telemetry
  • Cookies or tracking pixels

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.

2. Data That Exists on Your Device

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:

DataPurposeStored where
Wallet addressYour identity in roomsDevice only (localStorage)
NicknameDisplay name you choseDevice only (localStorage)
Room keysAES-256 keys to decrypt channelsDevice only (localStorage)
Member listsWho is in each roomDevice only (localStorage)
Message cacheOffline access to recent messagesDevice (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.

3. The Waku P2P Network and Relay Node

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:

  • Encrypted payloads — the node cannot decrypt message content (it does not hold room keys)
  • Content topics — protocol-level routing labels derived from the room key hash (they do not reveal room names or content)
  • Timestamps — when a message was relayed

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.

4. Wallet Connection

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.

5. The Marketing Website (abyss.chat)

The marketing website at abyss.chat is a static page. It does not use cookies, analytics services, tracking pixels, or any form of user tracking. It does not collect IP addresses or any visitor data. Font files are loaded from Google Fonts, which is governed by Google's Privacy Policy.

6. Third-Party Services

The App integrates with external services that have their own privacy policies:

  • WalletConnect — wallet connection relay (privacy policy)
  • Waku — P2P message transport (waku.org)
  • Ethereum RPC providers — blockchain queries for wallet authentication

7. Children

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.

8. Changes to This Policy

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.

9. Contact

Questions about this policy can be directed to support@enterabyss.chat or @abysschat on X.