Privacy Policy

1. What We Store Locally

UNIUN stores your notes, profile, saved items, channel messages, and settings directly on your device. This data is not sent to any server controlled by UNIUN.

2. What Gets Shared Publicly

When you publish a note or send a message in a public channel, that content is broadcast to Nostr relays. Nostr is an open public protocol — once published, your notes may be visible to anyone connected to those relays. UNIUN does not control third-party relays.

3. Your Identity & Keys

Your identity is a cryptographic key pair. Your public key is visible to others on the Nostr network. Your private key (nsec) is stored exclusively in your device's secure system keychain (iOS Keychain / Android Keystore). UNIUN never transmits your private key to any server.

4. Local AI (Shiv)

The Shiv AI assistant runs entirely on your device. It accesses only your locally saved notes. No note content is sent to any external AI service or API.

5. Media & Blossom Servers

If you attach images or media, they may be uploaded to a Blossom content server of your choice. UNIUN does not operate Blossom servers. Content uploaded there may be publicly accessible by design of the protocol.

6. Direct Messages

DMs are end-to-end encrypted using the Nostr NIP-17 standard. Only the intended recipient can read the message content. Message routing metadata may be visible to relays.

7. Your Control

You can delete your local data at any time from Settings. Because Nostr is a public protocol, content already published to relays is distributed across many independent nodes — see Section 8 for how to request its deletion across the network.

8. Deleting Your Data

UNIUN is a decentralized application built on Nostr, so your published data does not live on a single server we can wipe on your behalf. It is replicated across many independent relays (nodes) operated by different people around the world.

To delete that data everywhere it exists, Nostr provides a standard called NIP-62 "Request to Vanish." You sign a special event (kind 62) with your key that instructs relays to permanently delete all events associated with your public key. Compliant relays honor the request and remove your data, and may forward the request onward to other relays.

Because relays are independently operated, deletion depends on each relay honoring the protocol. UNIUN cannot force a third-party relay to comply, but the NIP-62 request is the network-wide mechanism for asking every node holding your data to remove it. You can read the full specification here:

Nostr NIP-62 — Request to Vanish

9. Contact

For privacy questions: pranavpandey1998developer@gmail.com