Readstr Privacy Policy

• We do not run analytics, trackers, or advertising.
• We do not sell or rent your data, and we do not share it with third parties for their own use.
• Your Nostr private key never leaves your device and is never sent to our servers.
• We store only what is needed to sync your subscriptions and read state across your devices.
• Readstr is open source and self-hostable, so you can run the entire stack yourself.

Readstr is designed to hold as little as possible. Depending on how you use it, the following data is involved:

• Nostr public key (npub / pubkey). Used as your account identifier so your subscriptions and read state can be synced. This is public information by design.
• Feed subscriptions. The RSS/Atom and Nostr feeds you add, stored so they are available across your devices.
• Read state. Which items you have marked as read, so unread counts stay consistent between the web app and the extension.
• Extension settings. Preferences such as your configured Readstr URL, poll interval, and notification options. These are stored locally in your browser.
• Nostr private key (nsec), if you choose to enter one. Stored locally in your browser and used only to sign requests on your device. It is never transmitted to our servers. Where a NIP-07 signer is available, the extension uses it and does not handle your key at all.

• To detect feeds on pages you visit and let you subscribe to them.
• To synchronize your subscriptions and read state across your devices.
• To fetch new feed items and, if enabled, notify you when they arrive.
• To authenticate your requests to the Readstr server using NIP-98 HTTP auth.

We use your data only for these operational purposes. We do not use it for advertising, profiling, or any purpose unrelated to running the feed reader.

• Feed sources you subscribe to.Fetching a feed contacts that source’s server, which will see the request as any feed reader would.
• Nostr relays you use. Nostr content is fetched from and published to the relays you configure.
• No one else. We do not sell, rent, or transfer your data to third parties, and we do not use third-party analytics or advertising networks.

• Sync data (public key, subscriptions, read state) is stored on the Readstr server you connect to.
• Local data (settings and any private key) is stored in your browser’s extension storage and never leaves your device except to sign your own requests.
• All communication with the Readstr server uses HTTPS.
• Requests are authenticated with NIP-98, so your private key is used only to sign and is not transmitted.

• You can use the extension without a Nostr account; feeds can be kept locally in your browser.
• You can remove any locally stored key from the extension’s settings at any time.
• You can delete your subscriptions and read state from your account.
• You can self-host Readstr so that all data stays on infrastructure you control.

If our data practices change, we will update this page and revise the “Last updated” date above. Material changes will be reflected here before they take effect.

Questions about this policy or your data can be sent to information@privkey.io. Readstr is open source at github.com/privkeyio/readstr.