Privacy policy
Last updated: 12 October 2026
This policy covers the Obelisk website and web app at obelisk.ar and the Obelisk app for iOS (Obelisk Chat on the App Store). Obelisk is a client for Nostr, an open protocol. It has no accounts and no server of ours that stores your messages. This page says what leaves your device, who receives it, and what stays on it.
The short version
- There are no Obelisk accounts. You are identified by a Nostr public key, not by an email address, a phone number or a password.
- We do not sell data, show ads or track you across apps and websites.
- The iOS app has no analytics, no advertising and no crash reporting. The website loads Google Analytics only if you allow it.
- What you write goes to the Nostr relays that you and your groups choose. Each relay is run by its own operator and stores what it receives under its own rules.
- Direct messages are end-to-end encrypted. Relays and other servers still see some metadata, including your IP address.
Who we are
Obelisk is open source software under the AGPL-3.0 license. The source code of the web app is public at github.com/obelisk-app/obelisk.
The iOS app is published on the App Store by Dandelion Labs JSC.
In this policy, "we" means the Obelisk project: the people who maintain the software, the obelisk.ar website and the relays listed below. You can reach us at abuse@obelisk.ar.
Your identity and your keys
Your identity is a Nostr key pair. The public key is public by design: it is attached to everything you publish and anyone can see it.
The iOS app never asks for, receives or stores your private key. You sign in through a signer: the Nostr WoT app on the same phone, or a Nostr Connect (NIP-46) bunker. Every signature and every decryption is done by that signer.
The web app can sign in with a browser extension (NIP-07), with a bunker (NIP-46), or with a private key you paste. A pasted key stays in your browser, encrypted with a key the browser keeps and will not hand out. It is never sent to us.
What you publish, and where it goes
Obelisk reads and writes Nostr events on relays. A relay is a server run by whoever runs it. When you post in a channel, react, edit your profile, join a group or send a report, the app sends a signed event to a relay. The relay stores it and gives it to others under its own rules.
Channel messages, reactions, profiles, group membership and reports are not private. Anyone the relay lets in can read them, and other relays and apps may copy them.
A group lives on one relay. What you do in a group goes to that group's relay and not to others.
Both apps look up profiles on a small set of relays, some of them run by third parties. The web app also reads public notes and profiles from general Nostr relays run by third parties, which you can change in Settings.
The relays we run
We run two relays: wss://public.obelisk.ar and wss://lacrypta-relay.obelisk.ar. Both are defaults in the apps.
These relays store the events published to them, which are signed and mostly public by design. Their access logs currently include client IP addresses. They hold no names, email addresses, phone numbers or payment records, because the software has no concept of them.
Every other relay is run by someone else, with its own rules and its own privacy practices. A relay usually publishes its operator's contact in its information document (NIP-11), which the apps show.
Direct messages
Direct messages are end-to-end encrypted: only you and the person you write to can read them. We cannot read them or recover them.
By default they use NIP-17 gift wraps. A relay that stores one sees an encrypted envelope addressed to the recipient's public key, when it arrived, how large it is, and the IP address that delivered it. It does not see the text or who sent it.
A conversation can also use NIP-04, an older scheme kept for compatibility. NIP-04 still encrypts the text, but relays see the public keys of both people.
Direct messages travel through your inbox relays and the other person's, which may be relays we do not run.
Servers that see your IP address
Obelisk has no backend of its own, so your device connects directly to each service it uses. Each of them sees your IP address, as any internet server does:
- Relays you connect to, ours or anyone else's.
- Media hosts. Images, files and voice notes are uploaded to Blossom servers run by third parties, and anything another person posts is loaded from wherever it is hosted. A file posted in a channel can be opened by anyone who has its address. A file sent in a direct message is encrypted before it is uploaded.
- Voice servers. Group calls go through a media server (SFU): ours at sfu.obelisk.ar, or one the channel's operator chose. Some calls in the web app are peer to peer, and then the other people in the call see your IP address. Setting up a call also contacts public STUN servers run by Google and Cloudflare, and a TURN relay when one is configured.
- Linked sites. Opening a link, or playing an embedded video or track, connects you to that site.
- GIPHY. Searching for a GIF or a sticker in the web app sends your search words to GIPHY.
- Lightning providers. Sending a zap contacts the recipient's Lightning provider for an invoice and your own wallet provider to pay it.
Unless this page says we run a service, someone else does, under their own privacy policy. We do not control what they log.
The obelisk.ar website
The server that delivers obelisk.ar receives your IP address and browser details with each request, as any web server does.
Link previews. When the web app shows a preview card for a link in a message, it asks obelisk.ar to fetch that page's title, description and image address, so the linked site sees our server and not you. The request carries the address of the link. The server counts requests per IP address in memory for one minute to limit abuse, and keeps the result in memory for up to an hour. This code writes nothing to a log or a database. The image in a preview is then loaded by your browser from its own host.
Google Analytics. The website asks whether you allow Google Analytics. Nothing from Google loads unless you say yes. If you allow it, Analytics sets its own cookies and tells Google which pages you open and, from your IP address, roughly where you are, under Google's privacy policy. You can change your answer at any time from the footer of this site or in Settings > Data on this device.
Cookies. The site sets one cookie of its own, which remembers your language. Google Analytics cookies exist only if you allowed Analytics.
What stays on your device
To open quickly and keep you signed in, the apps store data on your device: your public key and how you sign in, cached channels, messages and profiles, read positions, settings, the people you blocked, and a wallet connection if you added one.
Direct messages you have opened are stored only in encrypted form. A wallet connection (a Nostr Wallet Connect link) can spend from your wallet, so the iOS app keeps it in the system keychain and the web app keeps it encrypted in the browser. It is erased when you disconnect the wallet or log out.
This data is not sent to us. Two things do leave the device in another form: in the web app, read positions are synced through your relays, encrypted to your own key, and in the iOS app, blocking someone also adds them to your Nostr mute list, which is public.
Permissions on iOS
- Microphone. Used only while you are in a voice call, so the others can hear you. iOS asks the first time you join one.
- Camera. The app does not use the camera: calls are audio only. It declares a camera purpose only because its calling library requires one.
- Background audio. A call keeps running when the app is in the background or the phone is locked.
The app does not ask for your contacts, location or photos, and it sends no push notifications.
Payments (zaps)
Zaps are Bitcoin Lightning payments made by your own wallet. Obelisk never holds funds, sells nothing and has no in-app purchases. There is no Obelisk payment server.
You can connect a wallet with Nostr Wallet Connect, hand a payment to a wallet app on your phone or, in the web app, use a WebLN browser extension. The payment itself is handled by your wallet provider and the recipient's Lightning provider.
Zaps follow NIP-57. The zap request you sign and the receipt the recipient's provider publishes are Nostr events, and they can show your public key, the amount and your comment.
Deleting your data
On your device. In the web app, open Settings > Data on this device to remove any category, or everything. In the iOS app, open the You tab, then Data on this device. Logging out also erases your login, your wallet connection and your stored direct messages from the device.
What you published. Nostr has a deletion request (NIP-09) that asks relays to remove an event you published. A relay that honours it removes its copy. Nobody can make every relay and every app delete theirs, so copies may remain.
On the relays we run. Write to abuse@obelisk.ar with the relay address and the event ID or your public key, and we will remove those events from our relays. Copies on other relays are outside our control.
There is no account to close.
Children
Obelisk is not directed at children under 13, and we do not knowingly collect personal information from them. Obelisk shows content written by other people that nobody reviews before it appears.
Changes to this policy
When this policy changes, we update this page and the date at the top. Its history is public in the project's source repository.
Contact
Privacy questions, support requests and abuse reports all go to abuse@obelisk.ar. Security problems go to security@obelisk.ar.