← Siner

Privacy Policy

Last updated: November 11, 2026

Siner is owned and operated by Hatch House Limited, a company registered in Ras Al Khaimah, United Arab Emirates (hatchhouseltd.com). Siner is a client for the Nostr protocol, available as an iPhone app and as a web app at siner.me. Your identity is a cryptographic keypair you control — not an account on our servers — and any wallet you use is self-custodial, with keys we never hold. Siner is built to collect as little as possible: there are no ads, no third-party tracking, and no data sales. The limited telemetry we do collect — crash diagnostics and anonymous, aggregated product analytics — is never linked to your identity and can be turned off. This policy explains the data Siner processes, what's public by design, and the choices you have. The iPhone app and the web app are the same product on different foundations, and where they handle your data differently, both are described.

Your keys stay with you

Your private key (your "nsec") never reaches our servers in readable form. Every post, message, and signature is signed on your own device or in your own browser.

On iPhone, the key is generated on your device and stored in the iOS Keychain, marked so it does not sync to iCloud or other devices.

In a browser there are three ways to sign in, and they are not equally private. If you use a signer extension (NIP-07) or link the signer on your phone (NIP-46), the key never enters the web page at all — those are the strongest options and we recommend them. If instead you paste your key, it is encrypted and kept in this browser's storage so you stay signed in across reloads, under a key the browser will not hand back to any script. Be clear about the limit of that: it protects your key at rest — on a stolen disk, in a device backup, in a copied browser profile — but not against code running on siner.me itself, and a Nostr key cannot be rotated if it leaks. You can add a passphrase (Settings → Account & Security) so nothing on the device opens it without you. A browser is not a backup either: logging out, clearing site data, or losing the device erases the stored copy.

What Siner stores in your browser

The web app uses no cookies and no third-party storage. Everything it keeps is first-party and functional — it is what makes the app work at all, not a way of tracking you across the internet.

In this browser Siner stores: your encrypted key, if you signed in by pasting one (see above); the posts, profiles and decrypted messages it has already fetched, cached so the app is not empty every time it opens; your settings; your drafts; the built-in wallet's seed, if you created or restored that wallet here (see "Your wallet & funds"); the connection string for any Lightning wallet you chose to remember; the browser's device key that seals your posts (see "Device records held by siner.me"); and a random analytics id, if you have left analytics on. None of it is sent anywhere except as this policy describes.

All of it lives on your machine and none of it is readable by us. You can erase every bit of it at once by signing out, or by clearing site data for siner.me in your browser settings — which also erases your stored key, so make sure you have a backup first.

Email & account recovery

Email is optional and only used if you turn on encrypted backup. When you do, we use your email address to send a one-time verification code through our email provider (Resend). The code is single-use and expires after about 15 minutes; we don't keep your email address after that. Your backup itself is stored under a one-way hash of your email, so the stored backup is not linked to a readable address.

Encrypted key backup

If you enable backup, your key is encrypted on your device with your chosen password (PBKDF2 with 600,000 iterations, then AES-256-GCM) before anything is uploaded. Our server stores only the resulting ciphertext and the parameters needed to decrypt it on your device — it has no ability to decrypt your key. This also means that if you lose your backup password, no one (including us) can recover your key. Save it somewhere safe.

Your wallet & funds

The iPhone app includes a built-in, self-custodial Lightning wallet (powered by the Breez "Spark" SDK). The wallet is secured by a seed generated on your device and stored only in the iOS Keychain (it does not sync to iCloud); we never receive it, and it has its own 12-word recovery phrase, separate from your Nostr key. Using the wallet means your device communicates with Breez/Spark infrastructure and the Lightning Network to send and receive payments.

The web app can run the same built-in wallet: choose Create Siner wallet on the Wallet tab, or Restore from recovery phrase to open your phone's wallet. In a browser its seed is kept in this browser's storage, not a Keychain, and encrypted there when you have set a passphrase; we never receive it. Signing out leaves it in place so your funds are not lost; clearing site data removes the wallet from that browser, so back up its 12 words first.

On either platform you can instead connect a wallet you already have, over Nostr Wallet Connect (NWC). Its connection string is stored in the iOS Keychain on the phone, and in this browser's own storage on the web (only if you asked to remember it; otherwise it lasts for the tab). It is used to ask that wallet to pay or receive; Siner does not hold that wallet's keys.

Either way, Siner is not a custodian: we cannot access, freeze, or recover your funds, and if you lose your device without your recovery phrase, the funds in the built-in wallet cannot be recovered.

What's public by design

Nostr is a public network. When you post, update your profile, react, repost, zap, or file a report, that event is published to relays as signed, public data and is effectively permanent — relays and other people can keep copies indefinitely, including copies on relays we don't operate.

This includes: your profile (display name, bio, picture, lightning address), your posts and the media in them, your reactions and reposts, your zaps (which publicly link who tipped whom and how much), and abuse reports (which publicly link your key to the content you reported).

Sharing with the Nostr network (beta): not yet available to everyone; Siner turns it on in stages, and until then nothing is shared or read. Once it is available to you, it is off unless you turn on "Share my public posts with the Nostr network (beta)" (Relays, Nostr network; the setting is part of your account's public relay list). While it is on, each new public post you make (an autograph, a public postcard, a public memento or a collab) is also sent, only after it has passed automated screening, to six public Nostr relays run by others (relay.damus.io, nos.lol, relay.primal.net, nostr.bitcoiner.social, relay.snort.social and nostr.mom) as a standard note: its caption, the links to its pictures or video (a card with two pictures is shown as one picture made by siner.me and served from siner.me), "Siner Sealed" with a link to verify a sealed post on siner.me, a link back to siner.me, and its zap split. Your likes, comments, reposts and zaps on shared posts go there too, each as a standard copy aimed at the shared post; a zap paid over Lightning names the shared copy and those relays in its request (a zap between two Siner wallets stays on our relay). Your profile and relay list go there only if you have none there yet, so ones made in another Nostr app are never replaced, and an edit to your profile goes only while the copy there is the one Siner sent; your deletion requests for what was sent go too. Your follow list never goes. Nothing else is copied: private postcards and mementos, memento contributions, direct messages, reports, mute lists and bookmarks stay on our relay. After you turn sharing off, only your updated relay list and deletion requests for what was already copied still go there, and the app offers to ask those relays to remove the copies. Those relays may keep copies after you delete something or turn sharing off, and a post that Siner later removes may remain on them; we cannot remove content from them. In the other direction, while you share, siner.me copies the replies, likes, reposts, comments and zaps that people on other Nostr apps aim at what you shared into our relay, with the profile (name and picture) of each person who sent one. To find them, siner.me asks those six relays, and two more it only reads from and never sends to (nostr.wine and eden.nostr.land), for what is aimed at accounts that share.

Camera, microphone & media you upload

Siner uses your camera only while you're actively capturing a photo or video to publish, and your photo library or file picker only for items you choose to attach. Captured or selected media stays on your device until you publish it. Siner asks for the microphone when you switch the camera to Video, or when you sign, because a video has sound and so does the signing video. If you say no, or the device has none, the video records without sound. Taking a photo never uses the microphone. A video you publish carries its audio track, and it is public with the video. In a browser, the camera, the microphone and your location are additionally gated by your browser's own permission prompt: deny it and the app cannot reach them whatever its settings say.

When you sign, your front camera records the signing, with sound, and that recording is the signing video. It travels with what you sign (an autograph, a postcard, a memento, a contribution or a collab), and the Siner Seal shows it and checks that it is unchanged. Like the artwork, it is uploaded to our content delivery network and is public if the post is public; in a private postcard or memento only its link and fingerprint travel inside the encrypted message, and the file is served from our content delivery network to anyone who has that link. It is also checked by automated screening, only for sexual content, violence, graphic violence and self-harm, as "Content moderation" describes. Videos are capped at 30 seconds in the camera.

When you do publish, images and videos are uploaded to our content delivery network and served at public HTTPS URLs — anyone with the URL can view them, and other servers may cache them. Publishing is public by design — don't upload anything you wouldn't want to be public and persistent.

Location & device details

Siner can attach proof-of-authenticity context to autographs — capture time, and optionally your location and a description of the device you used. Both are controlled by toggles in Privacy settings, on either platform. When a toggle is off, that detail is left out of both the public event and the image you upload. When it is on, it can appear in the public post, its proof metadata, and the image's embedded EXIF data. Turn these off before capturing if you don't want that information shared.

What those two details ARE differs by platform: on the phone, GPS location and the device model. In a browser, the location your browser reports (and only after you grant the permission prompt) and your browser and operating system rather than a hardware model.

Place search and place names: on the phone, Apple's geocoder turns a place you search for, or a location, into a name like "Lisbon, Portugal". The web app has no geocoder of its own, so when you search a place for a postcard, or it names the place of your approximate location, a photo or a post, the search text or coordinates rounded to about 1 km go through Siner's server to a geocoding service (Photon, run by komoot). The geocoding service sees our server, not your IP address, and we don't log what you search for.

Direct messages & postcards

Direct messages are end-to-end encrypted (NIP-17 gift wrapping). The decrypted text is cached only on your own device — in the app's storage on the phone, in this browser's storage on the web — and only ciphertext, addressed to your recipient, is sent to relays. We cannot read your messages. Metadata minimization is applied (timing is jittered and delivery defaults to our relay), but as with all messaging, your recipient and the relays involved can observe that an encrypted message was sent.

A postcard you send privately, to one person or several, is delivered the same encrypted way: only you and your recipients can open it, and we cannot read the encrypted message. Its pictures and videos are the one exception, described under "Content moderation": they are checked by automated screening when they are uploaded, only for sexual content, violence, graphic violence and self-harm. A recipient you invite by email is the exception described under "Postcard and memento invites": the invite email carries your name and a preview of your message. To seal them, siner.me learns the id of each copy and when it was sent (see "The Siner Seal: what siner.me records about your posts").

Handles (NIP-05)

If you claim a username@siner.me handle, we store a mapping from that name to your public key so others can verify you. That mapping is served publicly so any Nostr client can resolve it.

Postcard and memento invites

If you send a postcard to, or invite to a memento (a card several people sign together), someone who isn't on Siner, you provide their email address so we can send them an invite (delivered through our email provider, Resend) with a one-time claim link. You're responsible for having that person's consent to email them. We send the invite email only once your account is established (it posts from a Siner iPhone, or it is at least 7 days old); until then you share the claim link yourself and nothing is emailed. Phone numbers in your name and message are removed from the invite. A postcard invite also carries your name and a preview of your message (up to its first 280 characters), which the email shows; the card itself is kept on our server encrypted to a key that only the link in the email carries, so we cannot open it. We store a claim record — the email or a claim token plus the card and pubkey references needed to deliver the postcard or activate the memento, and for a postcard your name and that preview — which expires automatically after about 60 days. We don't use these addresses for marketing, and you can ask us to remove an invite record at support@siner.me.

The Siner Seal: what siner.me records about your posts

The Siner Seal shows that a post was made in Siner by the account that posted it, on a Siner device registered to that account, at the time siner.me recorded, and that it is unchanged since. To make that possible, every time you post, send or comment from Siner, your iPhone or your browser approves the exact post, and siner.me records it.

For each post siner.me signs and stores an origin statement: your public key, the post's id, which kind of device approved it (the Siner app on iPhone, or a browser) with that device's key identifier, and the time siner.me received it. It also stores the filing itself: the ids of everything that one send created and the device's approval. Anyone who knows a post's public key and id can ask siner.me for its statement, which is how any app or the siner.me page checks a seal.

Private postcards and mementos: their content stays end-to-end encrypted and we still cannot read it. But siner.me now learns the id of each private copy you send and the time you sent it, because each copy gets its own statement. A statement names one copy only and reveals nothing about the other recipients.

What is not recorded: the content of your posts and messages, your private key, and your location. The checks of pictures and videos are done by the viewer's app against the post itself.

Older seals: posts made with Siner 1.2 also filed a seal bundle (content hashes, signing metadata, optional location and device context per your toggles above, and a signature), stored under its content hash and publicly retrievable. Those bundles are kept until you ask us to remove them (support@siner.me).

How long: origin statements and filings are kept until you delete your account, which removes them along with the queued Bitcoin records described below.

Device records held by siner.me

To know that a post came from a Siner device registered to your account, siner.me keeps a record for each device.

On iPhone that is an Apple App Attest key record: the key identifier, the attestation Apple produced, the public key, the validation result, a counter that stops an old approval being replayed, and the Nostr public keys of the accounts that key is bound to. Each account signed in on the iPhone binds itself to the key with its own signature, so one iPhone can serve several accounts and none can use it for another.

In a browser the web app creates a device key the first time you post from it, without a prompt. The private half stays in the browser and cannot be exported, even by Siner. siner.me stores its public key, its identifier, your Nostr public key and the time it was registered. Clearing site data or using a private window creates a new key, which registers silently; the number of new keys per account per day is capped.

Older web seals (1.2) used a WebAuthn credential record: the credential identifier, its public key, the grade the registry could verify, details of the authenticator (its type and model identifier), a counter, and your Nostr public key. Those records have no expiry and are kept until you ask us to remove them.

These are public keys and technical details, not your biometrics. Face ID, Touch ID or a device PIN stay on your device. App Attest records, the account bindings and browser keys are kept until you delete your account; deleting it removes your bindings and browser keys, and an App Attest key record is removed once no account is bound to it.

Upload receipts

When you upload media, the server writes a receipt: the SHA-256 hash of the file, the account key that uploaded it, its size, its type, the time, and where it is stored. The first uploader of a file keeps the receipt. We set no expiry on receipts. The media itself is served from our content delivery network as described above.

Bitcoin timestamps (OpenTimestamps and NIP-03)

Every origin statement is anchored on the Bitcoin blockchain, as evidence of its time that does not depend on Siner. A background worker on our server takes the fingerprint (hash) of each statement, combines them into one hash every few minutes, and sends only that hash to public OpenTimestamps calendar servers. Your content, your key, your location and your device details are never sent. The calendars see our server's IP address and the hash. Our server then asks two public block explorers (mempool.space and blockstream.info) for the Bitcoin block header; they receive no data about you.

When the record is confirmed in a Bitcoin block, the proof is served with the statement. For a public post we also publish a NIP-03 timestamp attestation on Nostr, signed by Siner, which names the post's id and is public like any other event. Private postcards and mementos get no NIP-03 event.

How long: a record that has not confirmed is stamped again, not dropped. Deleting your account removes your records that are not yet in a batch. A confirmed batch record is kept, because the proofs of other posts depend on it; it holds only fingerprints, which reveal nothing about you or your posts. Seal bundles from Siner 1.2 are still timestamped the older way while 1.2 apps remain in use: their queue and stamping records are removed once the proof is confirmed, a hash not confirmed within 7 days is set aside and deleted after 90 days, and the worker's log entries are deleted after 30 days.

No tracking, no advertising

Siner contains no advertising and no third-party tracking SDKs. The iPhone app does not use an advertising identifier and does not ask to track you across apps or websites; our privacy manifest declares no cross-app tracking. The web app sets no cookies, loads no analytics or advertising script from anyone else, and has no third-party embed that could watch you. We do not sell your data. The only data that leaves your device beyond what you publish is the first-party, anonymous telemetry described next (diagnostics and product analytics), which you can turn off.

Diagnostics (crash & performance)

To find and fix bugs, the iPhone app may send crash and performance reports using Apple's MetricKit. These are diagnostics — not linked to your identity and containing no message content. Apple delivers them roughly once a day. They're reflected in the app's privacy manifest (Crash Data and Performance Data, used for app functionality).

The web app has no MetricKit. When something breaks in it, it sends a short error report instead: what kind of error it was and its technical message, the code location (a stack trace), the shape of the screen's address with any key, id or token in it removed, the app version, and your browser family and operating system (for example "Chrome 130, macOS"). Nostr keys and ids, Lightning invoices, email addresses and link parameters are stripped from the text before it is sent. A report carries no identifier of you or your browser and no message or post content. The web app sends none at all while "Share anonymous analytics" is off in Settings → Privacy.

Product analytics (anonymous & optional)

To understand how Siner is used and where it frustrates people — for example, which step of sign-up people abandon, or which screen they leave from — both apps send anonymous, aggregated product analytics.

What is sent is a short list of flat labels and nothing else: an event type (a screen view, a step of a flow, a flow completed or abandoned), the name of that screen or step, and a timestamp. The seal adds a few counters of the same kind, with no post id, key or content. On our server, siner.me counts seal filings and lookups by device kind and result, with no link to who made them. There is no field in it that could carry your npub, your name, your email, a handle you typed, or any message or post content — and none is sent.

It is tied to a random identifier that is generated on your device and belongs to that install or that browser alone, never to your identity. Events are aggregated into totals on our server (counts of how features and screens are used); we do not build per-person activity profiles.

You can turn it off at any time in Settings → Privacy, on either platform, and doing so also discards that random identifier and replaces it — so nothing collected afterwards can be joined to anything collected before. We can also disable it remotely, for each app independently. On iPhone it is declared in the app's privacy manifest as Product Interaction data used for analytics, not linked to your identity and not used for tracking.

Content moderation

To keep Siner safe, content on our relay and media on our CDN may be reviewed when reported and, where enabled, automatically screened by our AI moderation providers. What is screened depends on whether something is public or private.

Public posts get full automated screening. The post text, its public image URLs, and still frames sampled from each public video (ten by default, never its sound), including the signing video shown in a public post's Siner Seal, are sent to OpenAI (its moderation service) and/or Anthropic (Claude), which check them against everything our Community Guidelines prohibit.

Private postcards, mementos and contributions are checked by automated screening for four things only: sexual content, violence, graphic violence and self-harm. What is checked is every photo and video uploaded for them: the card's pictures as they appear on the card (a postcard's back and a memento's inside page show your message), its videos and its signing videos. The message you write stays end-to-end encrypted and is not sent. For a picture, its link on our CDN is sent and the provider fetches it; for a video, still frames are sent (ten by default, never its sound). They go only to OpenAI (its moderation service), which returns its usual set of results; siner.me keeps only these four and discards every other result at once: it is not stored, not shown to anyone and not acted on. Because siner.me cannot tell when a file is uploaded whether it will be posted or sent privately, every photo and video uploaded to siner.me is checked in this narrow way when it is uploaded; if you then post it publicly, it is also screened in full as described above.

What happens to a flag on a private card: a violence, graphic violence or self-harm flag can be reviewed by our team, who may delete the file and act on the account; nothing happens automatically. A sexual content flag is only counted and kept as a machine record that our team does not see. Our team can see that record only while reviewing a report on that card. Child sexual abuse material, wherever we find it, is removed and reported to the National Center for Missing & Exploited Children (NCMEC), and the account is banned, as our Community Guidelines say.

What we keep: video frames are deleted as soon as they have been checked. For a private item that passes, siner.me keeps only a short record that the file was checked and passed (the file's identifier, the account that uploaded it and the time) among the most recent 300 checks, and for 7 days the result for an unchanged video, so the same file is not sent twice. If a check fails, the file's identifier and the account stay on a list until our team retries or dismisses it. A violence, graphic violence or self-harm flag is kept, with the file's identifier and the account, until our team has dealt with it, and longer where the law requires. The record of a sexual content flag holds the file's identifier and its link, the account that uploaded it, the category, its score and the time; it is kept for 90 days or, once a report has attached it, as long as that report is kept. Until a report attaches it, our team sees only how many such flags there were. Each provider handles what it receives under its own API terms.

Replies and other interactions brought in from other Nostr apps are screened like any public post once they reach our relay. Notes shown by "Show posts from the wider Nostr network (beta)" come straight from public relays to your device and are not screened by Siner.

Your direct messages are end-to-end encrypted and are never scanned or readable by us. See our Community Guidelines for what's enforced and how to appeal.

Network basics (IP addresses)

Like any internet app, connecting reveals your IP address to the servers you contact. That includes our relay and CDN, and also third parties you reach directly — the hosts of other users' images, lightning-address providers when you zap, and public timestamp servers. With "Show posts from the wider Nostr network (beta)" on, your device also connects to relay.damus.io, nos.lol, relay.primal.net, nostr.bitcoiner.social, relay.snort.social, nostr.mom, nostr.wine and eden.nostr.land, which see your IP address, to fetch notes from the people you follow and, when you open the profile of someone who isn't on Siner, that person's profile and recent notes; sharing your posts does not, because siner.me's server sends them. We don't use IP addresses to build profiles of you; our relay keeps standard short-lived web-server logs for security and reliability.

Service providers

We rely on a small set of providers, each handling only what its function needs: DigitalOcean (hosts our Nostr relay and the media CDN), Resend (sends recovery, postcard invite and memento invite emails), Cloudflare (DNS, and depending on configuration may route traffic to our domain), Breez (provides the self-custodial Lightning wallet SDK and Spark infrastructure the built-in wallet connects to), OpenAI and Anthropic (automated moderation screening, when enabled: either may classify public posts; only OpenAI receives the photos and video frames of private cards, and only to check them for sexual content, violence, graphic violence and self-harm; neither receives your direct messages), Apple (the App Attest device-integrity check for posts made on iPhone), the public OpenTimestamps calendars (receive only a hash to anchor a proof), and two public block explorers, mempool.space and blockstream.info (our server reads Bitcoin block headers from them; they receive no data about you), and the public Nostr relays relay.damus.io, nos.lol, relay.primal.net, nostr.bitcoiner.social, relay.snort.social and nostr.mom (run by others under their own terms; they receive your public events while you share with the Nostr network), plus nostr.wine and eden.nostr.land, which siner.me and the app only read from. When you zap, you also contact the recipient's Lightning-address provider directly.

Your choices & rights

You control what you share: location and device toggles, analytics, whether to enable account backup, whether to claim a handle, and whom to mute or block. You can export a copy of your data from Privacy settings and delete your account in Settings → Account & Security → Delete Account — both are available in the phone app and in the browser. The built-in wallet has its own 12-word recovery phrase, on the phone and in a browser, so you can move your funds independently of your account.

For access, correction, or deletion requests under laws like the GDPR or CCPA, email support@siner.me with the subject "Data Subject Request." Most of your data lives on your own device and on the public network rather than on our servers; we'll help with what we hold.

The limits of deletion

Deleting your account removes your local data and keys from wherever you are using Siner — the app's storage on the phone, this browser's storage on the web — broadcasts a deletion request to relays, and deletes the media we host for you. Deleting in one place does not clear the other: if you use both, delete in both. But because Nostr is decentralized, content you already published may persist on relays and caches we don't control, and a deletion request is a request other relays may not honor. If you shared with the Nostr network, the deletion request also goes to relay.damus.io, nos.lol, relay.primal.net, nostr.bitcoiner.social, relay.snort.social and nostr.mom, which may not honor it either. If you created an encrypted backup, note that the (unreadable) backup may persist on our servers after account deletion; email support@siner.me to have it removed. Deleting your account does not move or destroy the funds in your built-in wallet — that wallet is controlled by its own recovery phrase, so back it up and withdraw your sats before deleting if you want to keep them.

Children

Siner is not directed to children. You must meet the minimum age required in your jurisdiction, and on iPhone the minimum age of the App Store rating, to use it. We don't knowingly collect data from children; contact us if you believe a child has used the app and we'll help.

Changes

We'll update this policy as Siner evolves and revise the date above. If we add anything that changes what we collect — for example, optional diagnostics — we'll describe it here and surface material changes in the app before it takes effect.

Contact

Questions about this policy: support@siner.me. Siner is owned and operated by Hatch House Limited, and the data controller is Hatch House Limited (registration number 01011756), Office A, Innovation City Business Centre, RAK BANK ROC Office, Ground Floor, Al Rifaa, Sheikh Mohammed Bin Zayed Road, Ras Al Khaimah, United Arab Emirates. Company contact: info@hatchhouseltd.com.

Last updated: November 11, 2026

Questions? support@siner.me

A creator network on Nostr.

Siner is owned and operated by Hatch House Limited (hatchhouseltd.com).