Overview
Feedgest helps you collect sources, generate digests, and deliver them through the channels you configure. This policy explains what data the product handles and how it is used to run the service.
Data we collect
We collect the information needed to provide the application, protect accounts, process billing, and support digest generation.
- Account data such as email address, username, locale, theme, authentication provider, and admin status.
- Source and content data from feeds and integrations you add, including RSS, newsletters, YouTube, GitHub releases, Telegram, and other supported sources.
- Digest configuration, delivery settings, prompts, generated digests, chat threads, categories, webhook settings, and connected channel metadata.
- Usage, quota, billing, payment history, device session, IP address, user agent, and security-related logs.
- Support messages, feature requests, votes, comments, and contact form submissions.
How we use data
We use data to operate Feedgest, fetch and process sources, create AI-assisted summaries, deliver digests, manage billing, secure accounts, debug failures, and improve reliability.
Service providers and cookies
Feedgest depends on third-party providers for core product features. We send each provider only the data needed for that provider to perform its role.
- AI providers such as Gemini, OpenAI, and configured model providers may receive source content, prompts, and digest context for summaries, chat, embeddings, or related AI features.
- OAuth providers such as Google, GitHub, GitLab, and X may process login and connection metadata when you use those sign-in methods.
- Billing providers such as Stripe and CryptAPI process checkout, subscription, invoice, and crypto payment information.
- Delivery providers and integrations such as email, Telegram, Slack, Discord, webhook endpoints, Google Chat, Mattermost, and Zulip receive the messages or delivery data you configure.
- Operational providers may process logs, analytics, security, storage, email, and error monitoring data, including Clicky analytics, Sentry, Amazon SES, and object storage.
AI processing
When Feedgest generates summaries, embeddings, categories, chat responses, or other AI-assisted output, relevant source content and instructions may be sent to the selected AI provider. AI output can be inaccurate, incomplete, or reflect source material incorrectly, so you should review important results before relying on them.
Your controls
You can update account settings, change delivery configuration, delete sources, delete digest profiles, revoke sessions, disconnect connected apps, and remove content from the product where the interface provides those controls.
Security and retention
We use access controls, encrypted passwords, secured credentials, session tracking, rate limits, and operational monitoring to protect the service. We keep account, content, billing, log, and backup data for as long as needed to provide Feedgest, meet legal obligations, resolve disputes, prevent abuse, and maintain reliable operations.
Contact
For privacy questions, account requests, or data removal requests, use the support address listed below.