Privacy

Last updated 28 August 2026.

We do not sell data

SendRSS does not sell, rent, or barter personal data. We do not sell subscriber lists. We do not sell publisher accounts. We do not sell hashed identifiers. We do not put ads in the letter, plant open-tracking pixels, wrap links to score clicks, or build reader profiles for advertising.

This policy explains what SendRSS stores to run the product, how roles work, and what an export is. The GDPR page covers rights and processing in more detail. The terms are the contract.

Who we are

SendRSS is the operator of sendrss.com: RSS-to-email, a capture widget, and constrained broadcasts. Contact: support@sendrss.com or the contact form.

Paid plans are billed by our merchant of record. Invoices, tax documents, and payment cards live in that portal, not in SendRSS’s card vault.

Who is responsible

The publisher is the controller of their subscriber list: addresses collected on the widget or subscribe link, the mail they send, and any export they download. SendRSS processes that list only to run the service they asked for.

SendRSS is the controller of the SendRSS account and this website: sign-in, plan mapping, support tickets, site cookies, and a closure record if the account is closed.

SendRSS is the processor of subscriber data on the product (email, status, hashed IP, delivery events, feed items used to compose a letter). See GDPR.

What we store

Publishers

• Account email, display name, and sign-in sessions
• Feed URLs, list names, widgets, templates, broadcasts, and related settings
• Support tickets and attachments you upload
• Billing mappings from the merchant of record (plan and license identifiers, not your full card number)
• Optional logo files you upload for branded mail

Readers (your subscribers)

• Email address and list status (pending, confirmed, unsubscribed)
• Confirm tokens until they are used; unsubscribe tokens while the row exists
• IP addresses truncated, then hashed. Raw IPs are never stored
• Delivery events needed to send mail: sent, bounce, complaint — not opens, not click maps, not a reader profile

Site visitors

• Essential cookies for sign-in and light or dark appearance
• Optional extras only if a site operator pastes analytics or pixel code in admin, and the visitor chooses Allow extras
• Messages sent through the public contact form

We store only what the product needs. We do not keep a marketing dossier on your readers.

How we use it

• Run the account, widget, RSS email, and broadcasts
• Confirm new addresses (double opt-in). Status stays pending until the confirm link is used
• Deliver mail your readers asked for, with unsubscribe and data-deletion links
• Protect the platform: bounce and complaint handling, abuse review, high-volume broadcast approval
• Answer support and legal requests we are required to handle
• Keep a closure record after an account is deleted: email, date, a hashed IP, and a short account summary. Subscriber addresses are not kept in that record

We do not use subscriber lists to advertise SendRSS to those readers. We do not sell data.

Cookies

Essential cookies keep you signed in and remember light or dark appearance. They do not track you across other sites.

Optional extras are only the head or body code a site operator pastes in admin. Those stay off until Allow extras. Search-engine verification meta tags may still load. The widget embed and email never include that admin code.

Change this anytime with Cookies in the footer or workspace.

When you export

From Account you can download JSON of the account. From Subscribers or Account you can download a CSV of addresses and statuses. The list stays yours. An export is a copy of data you already control; we do not sell it.

Once a file has left SendRSS, it is in the publisher’s keeping, like any other copy they make of their own list. Treat it with the same care you would give the list in the workspace. See terms and GDPR.

There is no bulk import. People join through your widget or subscribe link, then confirm.

Sharing

We share personal data only as needed to run the product:

• Email delivery provider — to send confirmations, RSS letters, broadcasts, and system mail
• Merchant of record — to bill paid plans
• Hosting and file storage — to keep the application, logos, and support attachments available
• The publisher — when they export CSV or JSON, or when a reader uses unsubscribe or erase
• Authorities — if the law requires it

We do not sell data to brokers, advertisers, or other publishers.

Retention

• Pending, confirmed, and unsubscribed rows stay until you or the reader erase them, or you close the account
• Delivery events stay with the list so bounces and complaints can be handled, and are removed when the related subscriber or account is purged
• Closed accounts: operational data is deleted; a hashed closure record remains for audit
• Billing records may be retained by the merchant of record as their law requires

Security

• Double opt-in before mail
• No raw IPs
• Unsafe markup stripped before a post is stored or mailed
• Sign-in cookies are essential, not a tracker farm
• High-volume broadcasts can wait for review

No internet service is perfectly secure. Keep the account sign-in to people you trust, and keep exported files somewhere only they should see.

Your choices

Publishers: export JSON or CSV, purge a subscriber, close the account (one-click purge of feeds, lists, subscribers, widgets, and sessions).

Readers: confirm, unsubscribe, or erase from the email footer. Erase removes the address and related events for that list.

Rights under GDPR and similar laws: GDPR.

Changes

We may update this policy when the product changes. The date at the top is the current version. Material changes will be reflected on this page.

Questions: support@sendrss.com or Contact.