Transparent by design.
Private by default.
Herald uses TEEs and on-chain encryption to bridge the gap between web3 identities and web2 communication channels. Here's how it works.
Localized Encryption
A user connects their Solana wallet and provides their email. This email is instantly encrypted in the browser via X25519 before ever leaving the device.
Technical Specifications • v1.3.1
What we handle. What we don't.
Herald is designed to handle minimal data. Here's a technical breakdown of our storage and visibility model.
| Data Point | Transmitted | Persistent DB | On-Chain |
|---|---|---|---|
| Wallet Public Key (Ed25519) | |||
| Encrypted Contact Blob (X25519) | |||
| Plaintext Email Address | |||
| Telegram Username / ID | |||
| Notification Subject & Body | |||
| Delivery Status (ZK Proof) |
Wallet Public Key (Ed25519)
Encrypted Contact Blob (X25519)
Plaintext Email Address
Telegram Username / ID
Notification Subject & Body
Delivery Status (ZK Proof)
Architecturally Compliant
By ensuring plaintext identifiers never hit our persistent storage, Herald is GDPR and CCPA compliant by design. Our "Zero Trace" delivery means you never have to worry about data breaches exposing your users.
Ready to join the privacy-first layer?
Start sending notifications to your users safely in 5 minutes, or register your wallet to take control of your alerts.