Providers used by the RSS-to-Telegram service launching first. Each receives only the information needed for its role.
Swipe the table sideways to see all details.
| Provider | Purpose | Data involved | Provider information |
|---|---|---|---|
| Cloudflare | Worker runtime, DNS, security, and key-value storage. | Subscription state, feed configuration, operational identifiers, and content processed in memory. | Trust Hub |
| Stripe | Hosted checkout, subscription billing, receipts, and Customer Portal. | Name, email, billing details, payment instrument, and subscription history. Card data is handled directly by Stripe. | Privacy |
| Anthropic | Generate a concise summary of a new feed item. | Feed item title and text submitted for summarization. | Privacy |
| Telegram | Customer-selected message destination and bot delivery. | Telegram chat or channel identifier and the summary message delivered there. | Privacy |
We will update this page before a new provider begins processing customer data. Where required and an account email is available, we will also provide advance notice. Products still marked “in development” may use different providers, but those providers are not part of the first production service until that product launches.