Privacy policy
Effective November 21, 2026 · Chrome and Firefox extensions
Your archive and key
Your browser keeps a sync report for each relay. When a relay rejects events because of their age, the report includes the number rejected and the oldest rejected date.
Social Backup stores your account settings, configured usernames, captured posts, local drafts, signed Nostr events, attachments, delivery records and website signing approvals in your browser profile. Creating a profile publishes the name, description, picture, banner and website you choose, with your public key and (when payment data is permitted) its npub.cash receiving address, to your selected Nostr relays; its pictures are copied to the media backup server selected in Media so they stay available. Signing in with a public key lets you import that account’s events read-only. The secret key, if supplied or generated, stays in the extension’s local database, unencrypted at rest while unlocked. Someone with access to your browser profile files could recover it.
Signing up and choosing sources
Profile shows the signed profiles and follow lists this device has seen for your own account. Refreshing history checks your selected relays for signed versions and your public my-events index. If you configured a media backup server, the extension can request index blocks from that server by hash. Publishing a change checks your selected relays for the current version. Changes to profile fields, custom JSON and restored follows become public when you choose Publish. Local history retains up to ten earlier profiles and three earlier follow lists within a shared 2 MiB event-data limit. Current versions and items awaiting delivery are kept separately.
During setup and when you open or return to Sources, the extension checks existing X, Facebook and Instagram tabs for the signed-in account’s username or Facebook profile ID. These checks run on the device. In Sources, you can select a suggested account and save it. During setup the extension also reads the signed-in Instagram account’s public name, description, link and picture to help fill in a new profile. If you enter an X username, it loads that public X profile without your cookies to suggest your name, picture, banner, description and website. When you sign in with an existing key, it reads your published identity list from your relays and checks its X proof on X.
Backing up and publishing
When you configure a social account, the extension reads matching posts as you browse supported profiles. It checks public originals with X, Facebook or Instagram without account cookies. It can send confirmed public posts, their authors, original URLs, timestamps and media references to the Nostr relays selected in Backup, and public attachments or index blocks to the media backup servers selected in Media. Capture may publish automatically. When X identifies a reply and its parent on the public original, the extension publishes a reply to your own post as a Nostr reply to that post’s copy. If that post is not in your backup yet, the extension first checks its public original. It publishes a reply to another account’s post as a Nostr comment with the parent post’s X URL. Private and unconfirmed captures stay on the device and can be included in your ZIP export. A flower with a check marks your own posts on X, Facebook and Instagram once they are in your backup. For this the extension compares the IDs of posts on the page with your backup on the device and sends nothing; you can turn the marks off in Sources. A click on the mark of a post that has a public copy opens that copy on iris.to in a new tab. The extension opens the tab, so the page you were on does not get the address of the copy. On these sites the toolbar icon also shows a dot: green while your backup is on, yellow when it needs you and red when posts on the page are not saved. The extension works this out on the device, from your settings and the same comparison of post IDs, and sends nothing. Relay sync requests signed events for your public key, which can include encrypted messages.
Media downloads contact the original file host or a configured server. On other HTTPS pages the extension can resolve supported media links using the local archive, configured media backup servers and, for named trees, Nostr relays. Those services receive the requested media hash or tree identifier. Remote services can see your IP address and the time of a request. Public posts and shared archive links can be read, copied and retained by others.
Account links, tips and signing
Posting an X verification can publish an association between your X handle and Nostr key once the post shows on any X page, or when you paste its link; the extension confirms it on X’s public page first. As you view your configured X following list, the extension stores the handles shown there in your browser, separately for each configured X account. It also reads the total following count when your profile shows an exact number. The list and count stay on this device and are excluded from your ZIP export. The extension does not collect Facebook or Instagram following lists. Finding matches compares X handles with a local directory, requests your current Nostr follow list and the candidates’ current Nostr profiles and identity lists from your relays, and checks proof posts on X without your cookies. Searching, filtering and paging through those results stay on the device. The X following list is not sent to relays or a directory service. Choosing to follow matches publishes your updated Nostr contact list to your relays.
The extension refreshes a directory of public Nostr identity claims from your selected relays in the background. It includes public legacy proof references from a nostr.directory snapshot. These references are lookup hints and still require a live X proof; a newer Nostr identity list overrides them. Matching X handles happens on the device. Flowers beside accounts in an X following list use this local directory, even with tips off. Clicking a Nostr link checks the X proof and current Nostr identity list before showing the destination. When the toolbar popup opens on an X profile that has a claim in this directory, it checks the X proof on X and shows that Nostr profile from the directory, with its known followers from a snapshot included in the extension. Relays are not asked about profiles simply because you view them.
Bitcoin tips are optional. Opening a tip checks the public X proof and queries the Nostr author, profile and, where applicable, the matching note and tip receipts. Currency estimates use public rate events or Coinbase. Selecting an amount requests an invoice from the recipient’s Lightning provider. The provider receives the amount and may receive a signed zap request naming your public key, the recipient, relays and the Nostr note. A provider can publish a receipt. Opening a tip can also check the status of your previously requested invoices directly with that provider. For a one-click post tip, the extension also reads the public post from X to check its author before requesting the invoice. Your wallet authorizes payment. The extension remembers confirmed tips locally for the active profile, including the recipient, amount and associated post. Its flower can show your past tips without contacting a relay. The menu can also show verified public receipts from others. Turning off tips removes the buttons.
Optional Cashu wallet
The Cashu wallet starts off. Enabling it lets you keep ecash on this device for the active profile. The extension stores the wallet seed, proofs, invoices, quotes and payment records in its private browser storage. Opening the toolbar popup or a tip menu can show your available balance from local storage while the wallet is unlocked. The mint you select holds the underlying bitcoin. It receives the information needed to issue ecash, quote and pay invoices, or recover pending operations. By default you confirm each outgoing payment on the extension’s wallet page. If you save a default amount while confirming a Cashu tip or in Wallet settings, clicking a post flower authorizes that amount. The extension shows the recipient, amount and fee in its own window and gives you time to cancel. Fees above the limit shown in settings require confirmation. Websites cannot read your wallet through the extension’s signing interface.
A new public profile’s Lightning address is derived from its Nostr public key. You can add or remove your npub.cash address in Keys & access. Publishing the address does not contact npub.cash. If you choose to find your mint or check incoming payments, the extension authenticates to npub.cash with your public key and a signed request. Automatic inbox checks are off by default. When enabled, checks run every 15 minutes while the wallet is on and the profile is unlocked, independently of the sites you visit. The extension claims eligible incoming payments from the selected mint. Both services can see your IP address. Changing the wallet setting does not change your public profile.
Disabling the wallet keeps its balance and records on this device. Encrypted wallet backups use a password you choose and are separate from social archive exports. Clearing browser storage or uninstalling can erase funds without a usable wallet backup. Anyone with the backup and its password may be able to spend the funds.
When a website requests Nostr sign-in or a signature, approval lets it receive your public key or the signed event. You can remember your login choice for that site. For signatures, you can allow or decline once, remember the choice for that event kind, or apply it to all signing requests from the site, including profile changes and deletions. These choices are stored on your device for that site and Nostr profile. You can revoke them in Keys & access. Your secret key stays on your device.
Retention and choices
You can disable capture per platform, change relay and media destinations, or download a ZIP. In Keys & access you can lock the key, revoke website permissions or delete the local archive. Exported files remain wherever you saved them. Deleting local data cannot withdraw records already delivered to other services.
Social Backup has no advertising or analytics service and does not sell user data. It uses data for the features described here. Its use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
For questions about the extension, use the project support page. Keep keys, private posts and archive files out of public issues. See also the terms of use.