Privacy Policy
Last updated: October 2026. This policy outlines how ChainSiren and DAMEPI SASU handle data, authentication, and notification routing in our emergency coordination platform.
1. Privacy-First & Non-Custodial Architecture
ChainSiren is built upon cryptographic standards designed to eliminate reliance on centralized credentials, passwords, and identity tracking. We do not maintain user password databases, nor do we request access to your private cryptographic keys or seed phrases.
Authentication is performed exclusively through Sign-In with Ethereum (SIWE / EIP-4361), verifying your cryptographic possession of a public wallet address.
2. Information We Process
- Public Wallet Addresses: When you sign in with Ethereum, your public address (e.g.,
0x123...) is used to associate your network subscriptions, dispatcher roles, and subscription status. - Alert Destination Configuration: If you configure alerting channels, you provide webhook endpoints (e.g. Discord webhook URLs, Telegram chat identifiers, Slack webhooks, or PagerDuty integration routing keys).
- Cryptographic Incident Signatures (EIP-712): When dispatchers or validator operators sign incident acknowledgments or emergency directives, the resulting signature, nonce, timestamp, and public address are cryptographically verified and recorded in the audit trail.
- Billing Information: Paid subscriptions (Operator, Team, Maintainer) are processed securely through our payment provider, Stripe. ChainSiren never stores your raw credit card numbers or banking credentials.
3. What We Never Request or Store
To maintain strict security isolation:
- We never request, store, or have access to your private keys or seed recovery phrases.
- We never execute blockchain asset transfers on your behalf.
- We do not sell, rent, or monetize your contact or routing data to third-party advertisers.
4. Third-Party Infrastructure & Services
ChainSiren interfaces with specialized infrastructure providers to deliver high-availability emergency alerts:
- PagerDuty: For incident phone escalation and push notification delivery.
- Telegram & Discord APIs: To transmit automated war room alerts to your designated channels.
- Stripe: For subscription billing and checkout portal management.
- Public Blockchain RPCs: To verify cryptographic block state and signatures.
5. Your Rights & Data Controller Contact
In accordance with the EU General Data Protection Regulation (GDPR) and French data protection laws (CNIL), you retain the right to inspect, update, or delete your configured webhook routing endpoints and personal configuration.