Privacy Policy for Nostr News Comments
Developer TeamPrivacy Policy
Last updated: June 2026
This Privacy Policy describes how our browser extension ("Nostr News Comments") handles user data. We are committed to protecting your privacy and ensuring a transparent, secure, and decentralized user experience.
1. No Collection of Personal Data
We do not collect, store, track, transmit, or sell any personal information or user data. There is no central server backend operated by the developer, and we do not use any analytics, cookies, or tracking tools.
2. Local Storage and Cryptographic Keys
All cryptographic keys (Private Key and Public Key) and user-configured display names are generated and stored strictly locally on your device using the browser's secure extension storage ("chrome.storage.local"). This data never leaves your device unless explicitly transmitted by you as part of a Nostr network event.
3. Decentralized Data Transmission (Nostr Protocol)
When you post a comment or interaction (such as an upvote or downvote), the action is cryptographically signed on your local machine using BIP-340 Schnorr cryptography and transmitted directly from your browser to public, decentralized Nostr relays via WebSockets. These relays are independent third-party entities infrastructure-wise, and data published to them is public by design according to the Nostr protocol.
4. Host Permissions
The extension requests host permissions for specific news websites (e.g., derstandard.at, diepresse.com, kurier.at) for the sole purpose of injecting the discussion user interface (via an isolated Shadow DOM) and anchoring comments to the respective article URLs. No browsing history, page contents outside the injected widget, or personal activities on these websites are read, stored, or monitored.
5. Changes to This Policy
Since this extension operates fully serverless and on-chain/relays-direct, any future updates will be bundled within the extension package itself. This privacy policy will remain strictly valid as long as the architecture remains entirely local.
Contact: If you have any technical questions regarding the local cryptographic implementation, please refer to the official public extension package documentation.