Privacy Policy
Last updated: 2026-10-11
About this policy
DRSS, at drss.io, is a service of buildtall.systems. It bridges RSS and Nostr. This policy says what information DRSS collects, where DRSS keeps it, who receives it, and how you remove it. It covers drss.io and the DRSS YouTube integration.
Signing in
You sign in with a Nostr browser extension (NIP-07) or a remote signer (NIP-46). DRSS never sees your private key. DRSS learns your public key (npub), and it reads your public Nostr profile to show your name and picture. DRSS does not ask for an email address, a name, or a password. You can read the directory, articles, and feeds without signing in.
Cookies and browser storage
DRSS sets only the cookies that keep you signed in. It sets no tracking or advertising cookies.
drss_session: your npub and an expiry time, signed by DRSS. It lasts 30 days, or until you sign out.btk_nip46: set only when you sign in with a remote signer. It holds that signer session, encrypted.
Your browser also keeps some DRSS settings in its local storage: reader mode, listening positions, and playback speed and volume. After you edit a list picture, a note about it waits in the browser session storage until the next page loads. These values stay on your device. Signing out does not remove them. Your browser's site data controls remove them.
Where your information lives
DRSS keeps no user database. Your information lives in Nostr events:
- Your lists, follows, saved articles, and listening progress are events that you sign with your own key. DRSS publishes them to relay.nostr.io, a public relay that buildtall.systems operates. Anyone can read them, as with all public Nostr events.
- When you first publish a list, DRSS adds a link to your lists, which names your npub, to its public directory of lists.
- The feed sources that you add are recorded, with you as their creator, on a private relay that only buildtall.systems services reach.
- DRSS publishes bridged feed articles to relay.drss.io, a public relay that buildtall.systems operates.
Logs
- The web server logs each request: your IP address, the time, the address you asked for, the response status, the referring page, and your browser's user agent. These logs are rotated weekly and kept for 26 weeks.
- The DRSS application logs the method, path, status, and duration of each request, without your IP address. Some entries name an npub. These logs have a fixed size limit, and the oldest entries go first.
- DRSS reads your IP address in memory to limit request rates. It does not store it.
buildtall.systems uses these logs only to operate and protect the service, and gives them to no one.
Third parties
DRSS shows no advertising and runs no analytics. It loads no scripts or fonts from other sites. DRSS and your browser contact other parties only as follows:
- Feeds: the DRSS server reads the RSS feeds it bridges from their hosts. It also looks up podcasts in Apple Podcasts, and it reads YouTube oEmbed data for YouTube feeds.
- Audio: your browser plays episode audio directly from its publisher. When you raise the volume above 100%, DRSS gets the audio from the publisher and passes it to you.
- Videos: a YouTube video in an article shows a preview image from i.ytimg.com. The video loads only when you click it, from youtube-nocookie.com. YouTube's own privacy policy applies to that request.
- Images: thumbnails load from cdn.serve.buildtall.systems, delivered through Amazon CloudFront.
- Relays: DRSS reads public Nostr profiles and relay lists from public relays, among them purplepag.es, relay.damus.io, and nos.lol.
- Save suggestions: when you save an article, DRSS can suggest a list for it. For this, it sends the article's title and summary, and the titles and descriptions of your lists, to a language model through OpenRouter. It does not send your npub.
Removing your information
- You can delete your lists, unfollow, and remove saved articles in DRSS. Each removal is an event that you sign, and DRSS publishes it to the relays.
- You can delete a feed source that you created.
- Signing out removes the DRSS cookies.
A Nostr deletion is a request to each relay. Copies that other relays or clients made are outside the control of DRSS. For any other removal, write to the contact address below.
YouTube API Services
DRSS uses YouTube API Services. A DRSS admin can connect a YouTube channel as a destination, so that the episodes of a show also go to that channel as videos. Only DRSS admins can use this feature. When you connect a channel, you agree to the YouTube Terms of Service. Google's use of your information is subject to the Google Privacy Policy.
- Access: DRSS asks Google for three permissions: to upload videos (
youtube.upload), to read your channel (youtube.readonly), and to manage your YouTube account (youtube.force-ssl). It reads only your channel's ID and title, to confirm which channel you connected. It uses the third permission only to add each uploaded video to the playlist that its show names. - Storage: DRSS keeps the refresh token that Google returns. It encrypts the token to the key of the DRSS podcast producer (NIP-44), and it stores the result on the private relay of buildtall.systems. Only the podcast producer decrypts the token, and it holds the decrypted token in memory only. DRSS does not keep the access token. The channel ID and title are in your destination, a Nostr event that you sign and that is public.
- Use: the podcast producer uses the token only to upload the episodes of the shows that name your destination, and to add each video to the playlist that the show names. Each upload sends the video file and its title, description, tags, category, language, privacy setting, and synthetic-media label. Each playlist addition sends the playlist ID and the video ID.
- Sharing: DRSS gives your YouTube data to no one. The Destinations page shows a destination only to the admin who created it.
- Revoking: retire a destination on the Destinations page to stop all uploads to its channel. Retiring does not revoke the access of DRSS at Google, and it does not delete the stored token. To revoke the access, remove it on Google's security settings page. After that, the stored token no longer works. To have the stored token and the destination deleted, write to the contact address below.
Changes
When DRSS changes how it uses information, this page changes first. The date at the top shows the most recent change.
Contact
Send questions, complaints, and removal requests to contact@buildtall.systems.