How SendBloc protects your data and respects your privacy.
Wallet-native encrypted messaging protocol. No phone number. No email. No compromise.
SendBloc ("we," "us," "our") operates a decentralized, end-to-end encrypted messaging protocol accessible via web, desktop, and mobile applications (collectively, the "Service"). This Privacy Policy explains what information we collect, how we use it, and the choices you have.
SendBloc is designed around a foundational principle: we cannot access the content of your messages. Our zero-knowledge architecture means that your communications are encrypted on your device before being transmitted, and only the intended recipient can decrypt them.
Effective Date: February 24, 2026. This policy applies to all users of the SendBloc protocol and associated applications.
Understanding what we do not collect is as important as understanding what we do. SendBloc has no access to:
SendBloc collects the minimum information necessary to operate the protocol:
When you generate a wallet, your public key is broadcast to the decentralized network to enable others to initiate encrypted communication with you. This is inherent to the protocol and cannot be attributed to a real-world identity without additional information that we do not collect.
Messages are relayed through the Waku protocol in encrypted form. Relay nodes temporarily hold encrypted message payloads to facilitate delivery. These payloads are indecipherable without the recipient's private key and are purged from relay nodes after delivery or a maximum retention period of 30 days.
If you explicitly opt in, anonymized crash reports may be sent to help us improve application stability. These reports contain no personally identifiable information, no message content, and no wallet addresses. You can disable this at any time in Settings.
Certain protocol actions (such as key registration and Pro Pass NFT minting) are recorded on the Ethereum blockchain. Blockchain transactions are public by design and are not controlled by SendBloc. We do not add any additional identifying information to on-chain transactions beyond what the protocol requires.
All private keys, message history, and contact data are stored locally on your device, encrypted at rest using your device's native encryption capabilities. SendBloc does not maintain server-side copies of your data.
Encrypted message payloads are temporarily stored on Waku relay nodes during the delivery process. These nodes are operated by a decentralized network of participants and do not have access to message content.
SendBloc does not operate a central user database. There is no server containing a list of users, their contacts, or their message history. This architecture makes large-scale data breaches structurally impossible.
SendBloc does not share user data with third-party advertisers, data brokers, analytics companies, or any commercial entity. We do not serve ads and do not monetize user data in any form.
The following third-party infrastructure is used:
SendBloc is not directed at individuals under the age of 18. We do not knowingly collect information from minors. If you believe a minor is using the Service, please contact us and we will take appropriate action.
Because SendBloc operates on a decentralized protocol, encrypted message payloads may be relayed through nodes located in various jurisdictions worldwide. However, since all content is end-to-end encrypted and we do not collect personally identifiable information, traditional data transfer concerns are mitigated by the architecture itself.
We may update this Privacy Policy from time to time. Material changes will be communicated through the application and published on our website at least 30 days before taking effect. Your continued use of the Service after changes take effect constitutes acceptance.
For privacy-related inquiries: