Privacy Policy

Overview

Nori is a client application for the Nostr protocol, an open, decentralized communication network. This privacy policy explains how Nori handles your data and what information is shared when you use the app.

How Nostr Works

Nostr is a decentralized protocol. When you publish content, it is sent to one or more relays (independent servers) that you choose. Nori does not operate these relays and has no control over data stored on them. Content published to Nostr relays is public by default and may be visible to anyone.

Data We Handle

Nori is designed to minimize data collection. Depending on the features you choose, the app and optional services handle:

Public key: Your Nostr public key is used to identify your account. It is not considered private information on the Nostr network.

Relay connections: The app connects to Nostr relays on your behalf to fetch and publish events. Relay operators may log connection metadata such as your IP address.

Local storage: Preferences, account information, and cached data are stored locally on your device. This data does not leave your device unless you explicitly publish it.

Published events: Any content you publish (messages, reactions, profile updates, etc.) is sent to your configured relays and becomes part of the public Nostr network.

Usage analytics (hosted web app only): Anonymous, cookieless page-view statistics collected by a self-hosted analytics service — see the Analytics section below.

Optional Passport account data: If you use Passport, the service stores your email address, username, password hash, encrypted Nostr private key, sessions, and security audit records. Optional email and push-notification preferences are stored only when you configure those features.

Optional Leviathan custody data: If a community uses Leviathan, the service stores its encrypted owner key, signing policy and operational records. Owner requests and action envelopes are Nostr events and may be publicly observable.

Private Keys and Optional Custody

Nori supports signing via browser extensions (NIP-07) and other external signers. When using these methods, your private key is managed by the signer and is never accessed or stored by Nori.

Passport and Leviathan are optional custody services. Passport encrypts and stores the identity key for an email/password account and signs through NIP-46. Its operator controls the service-side keystore and therefore has the technical ability to sign as that account and use its cryptographic capabilities, including decryption where the identity key is sufficient. Passport keys can be exported after re-authentication.

Leviathan encrypts and stores a participating community's owner key and uses it for policy-approved, owner-level actions. It does not hold member identity keys, the community root key, channel keys, or private-content keys, so owner-key custody alone does not provide access to community content.

Direct Messages

Direct messages on Nostr are encrypted between sender and recipient using the NIP-04 or NIP-44 encryption standards. While message content is encrypted, metadata such as the sender and recipient public keys and timestamps are visible on relays. Concord communities use end-to-end encryption (CORD-02) so that even the relay hosting a community cannot read message content.

File Uploads

When you upload files (images, videos, etc.), they are sent to Blossom-compatible file servers. These servers are operated by third parties and may have their own privacy policies. Uploaded files are generally publicly accessible via their URLs.

Voice Calls

Voice calls use LiveKit servers. For Concord communities, the voice broker issues a short-lived token bound to your pubkey; call media is encrypted in transit. For NIP-29 servers, the relay operator manages the LiveKit instance and its data handling.

Analytics

The hosted web app collects privacy-preserving usage analytics using a self-hosted instance of <umami>Umami</umami>, running on the same infrastructure as the service itself. No data is shared with third parties.

No cookies and no cross-site tracking. Nothing is stored on your device.

Page views are recorded with coarse technical context (browser and device type, country, referrer). Raw IP addresses are not stored; returning visits are counted via a salted hash that rotates daily, so visits cannot be linked across days.

Analytics are never linked to your Nostr identity. Your public key is not sent to or stored in the analytics system.

The service also computes aggregate statistics from its own relay (for example, the number of communities, posts, and daily active accounts). Only totals are kept — no per-account activity records — and end-to-end encrypted content remains unreadable in the process.

Native app builds and self-hosted deployments include no analytics unless the deployment operator configures their own.

Third-Party Services

The app may interact with the following third-party services:

Nostr relays: For reading and publishing events

Blossom servers: For file uploads and media hosting

LiveKit voice servers: For real-time voice calls

NIP-05 providers: For verifying Nostr addresses

Passport services (optional): For custodial identity, account recovery, and remote signing

Leviathan services (optional): For policy-gated custody of a community owner key

Each of these services is operated independently and may have its own data handling practices.

Data Removal

Because Nostr is a decentralized protocol, Nori cannot guarantee the deletion of content once it has been published to relays. You can request deletion by publishing a Request to Vanish (NIP-62), but individual relays are not obligated to honor these requests. To clear local data, you can delete your account from Settings, which wipes all client-side persistence on this device.

Deleting local app data does not delete records held by an optional Passport or Leviathan operator. Use that service's account, export, migration, or deletion controls where available, or contact its operator. Public Nostr audit events may remain on relays after service data is removed.

Changes to This Policy

We may update this privacy policy from time to time. Changes will be reflected on this page with an updated date. Continued use of Nori after changes constitutes acceptance of the revised policy.

Contact

If you have questions about this privacy policy, you can reach the team behind Nori at info@nori.club.