Privacy Policy
Effective date: March 6, 2026
1. Data Model
ST0RM.SU is designed to keep keys and most message data on user devices. Public channel syncing depends on active peers.
2. Local Storage
Your browser may store local configuration, session artifacts, and optional cached content.
3. Encryption
DMs use end-to-end encryption with peer-derived keys. Public channels are encrypted payloads shared in the live peer mesh.
4. What We Do Not Intend To Collect
ST0RM.SU is not designed to collect plaintext DM content on central servers.
5. Infrastructure Logs
Hosting layers may generate standard technical logs (IP, timestamps, errors) needed for uptime and abuse prevention.
6. Payments
If payment features are enabled, payment processors may process transaction metadata under their own privacy terms.
7. Security
No system is perfect. Endpoint compromise can expose active sessions.
8. Your Choices
Use panic wipe and browser profile separation for stronger local operational privacy.
9. Policy Updates
This policy may change. A production deployment should include versioned policy history.