Privacy Policy
1. Zero Plaintext On-Chain Storage Guarantee
Traditional dead man's switches store beneficiary Ethereum addresses and percentage allocations in plaintext contract storage slots, exposing family net worth to anyone reading public blockchain state.
Cadence Cryptographic Invariant: Beneficiary identities and split ratios are never written to blockchain storage in plaintext. The Cadence frontend encrypts all heir allocation manifests client-side using asymmetric ECIES-secp256k1. Only the double-hashed cryptographic Merkle root (allocationRoot) is committed on-chain. Third parties inspect zero details regarding your heirs or asset distribution.
2. No IP Logging, Analytics, or Tracking
Cadence respects Web3 privacy fundamentals:
- Zero IP Tracking
- Our web servers and sentinel APIs do not record, store, or profile incoming user IP addresses or browser fingerprints.
- No Ad Trackers
- We do not embed Google Analytics, Meta Pixel, advertising scripts, or data broker beacons.
- No Doxxing
- Wallet addresses are used strictly to query on-chain balance commitments and never associated with real-world identities.
3. Sentinel Webhooks & Notification Privacy
If you bind guardian email addresses for automated proof-of-life alerts:
- EIP-712 Cryptographic Binding: Registrations via
POST /api/bindrequire an off-chain EIP-712 structured signature proving wallet ownership. - Public Masking: The public sentinel monitoring feed (
GET /api/monitored-vaults) cryptographically redacts and masks all guardian email handles (e.g.g***n@example.com). - Zero Spam Policy: Email channels are exclusively triggered when a vault heartbeat enters the final countdown or the 14-day grace period is initiated.
4. Public Blockchain Immutability
You acknowledge that transactions submitted to Arbitrum Sepolia, Robinhood Chain, or Ethereum Sepolia (such as calling checkIn(), depositing assets, or claiming streams) are publicly and permanently recorded on decentralized blockchains. Cadence contributors have no technical ability to delete, edit, or reverse public on-chain transaction records.
5. Client-Side Storage & Cookies
We store minimal local state strictly in your browser's localStorage (e.g. cadence_cookie_consent_v1) to remember your privacy choices, network preferences, and cached RPC responses. You can clear this data at any time via your browser settings or adjust preferences via .