Privacy Policy
Last Updated: September 2, 2026
RSSFlow Reader ("RSSFlow" or "the Extension") values your privacy and data security above all else. This Privacy Policy comprehensively discloses how we collect, process, store, and share your data (including account credentials, local reading data, and AI interactions), and details our strict compliance with Google Chrome Web Store Developer Program Policies.
1. Data Collection (What Data We Collect)
1.1 User Account & Authentication Data (Email, Password & Verification Code)
When you optionally register or sign in to an RSSFlow account to manage Pro licenses across devices, we collect:
- Email Address: Collected during account registration or sign-in to identify your account, send email verification codes, and manage multi-device license entitlements. Feed libraries are not cloud-synced.
- Password & Login Credentials: Submitted during account registration and login to authenticate your identity. Passwords are never stored in plain text; they are securely salted, hashed, and processed via our trusted authentication infrastructure (Clerk).
- Verification Codes & Activation Codes: Collected when verifying your email during registration/login, password resets, or when applying Pro license keys to unlock advanced features.
- Anonymous Device & Session Identifiers: Generated to securely associate license entitlements and manage active signed-in devices.
1.2 RSS Subscriptions & Content Cache
Stored locally in your browser to enable RSS feed reading, offline access, and feed management:
- RSS/Atom Feed URLs actively added or imported (OPML) by you
- Article titles, web links, author names, publication dates, summaries, and full-text HTML/plain text cache
- User reading records: read/unread states, starred/bookmarked articles, custom categories, tags, and reading notes
- Local content caches from Discovery, Summary, and Flow timeline views
1.3 User Configuration & Integration Credentials
Stored locally to provide personalized reading experiences and user-initiated integrations:
- UI & Display preferences: themes, layout densities, language, and font settings
- AI model configuration: selected model providers, model names, custom Prompts, and user-provided API Keys (e.g., OpenAI, Google Gemini, SiliconFlow, DeepSeek)
- Integration tokens: Telegram Bot Token / Chat ID, Feishu Webhook URL, and MCP Bridge configurations
- Task automation schedules, notification preferences, and speech (TTS) settings
1.4 AI Interaction & Chat Data
When you explicitly trigger AI summarization, chat assistant, or translation features:
- Selected article excerpts, user queries, and chat conversation context
- Custom instructions, prompt templates, and AI-generated responses (summaries, insights, mindmaps)
1.5 Explicit Non-Collection & Data Boundaries
Except for the account credentials (Email, Password, Verification Code) you voluntarily provide when creating an optional account, RSSFlow strictly adheres to data minimization:
- NO unnecessary Personally Identifiable Information (PII) such as home addresses, phone numbers, or government IDs
- NO general browser web surfing history outside of your explicitly subscribed RSS feeds
- NO full payment card numbers or bank credentials. Paid checkout is hosted by Creem.io (Merchant of Record); Creem processes card data under its own privacy policy. We may receive order id, checkout id, customer email, plan, and fulfillment status — not PAN/CVV.
2. Data Processing & Purpose (How We Use Your Data)
2.1 Account Authentication & Multi-Device Sync
Your email, password, and verification codes are processed exclusively to verify your identity, maintain secure login sessions, and synchronize Pro license status across your authorized devices. They are not used to sync your RSS library or article cache.
2.2 Core RSS Aggregation & Offline Reading
The extension fetches RSS/Atom feeds in the background, using an offscreen document to safely parse HTML/XML feeds into clean articles stored in your local SQLite WASM database.
2.3 AI-Powered Summaries & Conversations
When you actively request an AI summary or chat query, the relevant article snippet and prompt are transmitted solely to your chosen AI provider endpoint to generate the requested analysis.
2.4 Scheduled Automations & Push Notifications
When automated digest tasks execute, article updates and summaries are formatted and forwarded directly to your configured Telegram or Feishu webhook endpoints.
2.5 Text-to-Speech (TTS)
Selected article content is synthesized locally using the browser Speech API or sent to your chosen cloud TTS provider to generate audio playback.
3. Data Storage, Retention & Security (Where and How Long Data Is Stored)
3.1 Local-First Architecture for Content
Most RSSFlow reading data (reading lists, cached articles, local settings, and AI chat history) is stored on your local device using Chrome's storage API and local SQLite WebAssembly (unlimitedStorage).
3.2 Account & Credential Security
Account authentication data (Email, Password, Verification Codes) is transmitted exclusively over encrypted HTTPS/TLS connections. Passwords are cryptographic salted hashes managed by enterprise-grade identity provider Clerk; plain-text passwords are never accessible to or stored by us.
3.3 Data Retention Period
Local reading data persists until you manually clear it, reset the extension, or uninstall it. Account authentication data is retained for as long as your account remains active; you can delete your account and all associated data at any time.
4. Data Sharing & Third-Party Disclosure (Who We Share Data With)
4.1 Affirmative Declaration on Data Sharing
We do NOT sell, rent, monetize, or trade your personal data under any circumstances. Data is transmitted only when you actively initiate features:
- Authentication Provider (Clerk): Processes your email, password (hashed), and verification codes solely to authenticate your account and manage multi-device sign-in sessions.
- Payment processor (Creem.io): Hosted checkout for RSSFlow Pro. Creem is Merchant of Record for tax and invoices. We receive order metadata needed to issue a license; we do not receive full card numbers.
- Account and license API (Cloudflare Worker): Stores activation codes, license snapshots, and Creem order mappings so the extension can validate Pro access.
- Subscribed RSS Feed Servers: Direct HTTP(S) requests to retrieve article updates from feeds you add.
- User-Configured AI Providers: Direct API calls to user-configured AI providers (e.g., OpenAI, Google Gemini, SiliconFlow, DeepSeek).
- User-Configured Messaging Channels: Direct webhook payloads to user-configured messaging channels (Telegram Bot API, Feishu Open Platform).
- License Validation Service: License verification requests (activation key and device token) to validate license status.
4.2 Third-Party Terms
Third-party services process data under their respective privacy policies. We encourage you to review their terms before configuring their endpoints.
5. Chrome Web Store Limited Use Compliance Declaration
5.1 Google Developer Program Policies Adherence
RSSFlow complies rigorously with the Chrome Web Store Limited Use Policy for all collected data (including Email, Password, and Verification Codes):
- No Data Sale: We do NOT sell, lease, or monetize user data (including email addresses and credentials) under any circumstances.
- Single Purpose & Core Utility: We do NOT use or transfer user data for purposes unrelated to the core functionalities of RSS reading, AI assistance, user notifications, and user account management.
- No Targeted Advertising: We do NOT use or transfer user data for personalized advertising, retargeting, or behavioral profiling.
- No Credit Assessment: We do NOT use or transfer user data to evaluate creditworthiness or for lending determinations.
6. Browser Permissions & Justification
6.1 Declaration of Extension Permissions
- offscreen: Required under Manifest V3 to safely parse XML/HTML feeds via DOMParser and execute the local SQLite WebAssembly engine in an isolated worker thread.
- unlimitedStorage: Required to store full offline articles, vector caches, and SQLite database files without exceeding Chrome's default 5MB quota.
- sidePanel: Required to render the reader interface and AI conversation panel inside Chrome's native sidebar.
- storage & alarms: Required to persist local user preferences and trigger background feed update intervals.
- host_permissions (https://*/*): Required to retrieve RSS/Atom feeds from user-specified feed URLs and connect to user-configured AI/Webhook/Authentication endpoints.
7. User Rights & Data Deletion (Your Control)
7.1 Full Data Autonomy & Account Deletion
You maintain complete ownership and control over your data at all times:
- Export all feed subscriptions anytime via standard OPML format
- Individually manage, edit, or delete articles, feeds, custom prompts, and chat histories
- Manage authorized devices and log out of account sessions at any time in Account Settings
- Permanently delete your account and all associated credentials upon request
- Instantly purge all local data by clicking 'Reset Extension Data' in settings or uninstalling the extension
8. Children's Privacy
8.1 Protection of Minors
RSSFlow is designed for general audiences and does not knowingly collect information from children under 13. Minors should use this extension under parental or guardian supervision.
9. Policy Updates & Contact
9.1 Policy Revisions
We may update this Privacy Policy to reflect product improvements or regulatory requirements. Any updates will be published on this page with an updated 'Last Updated' date.
RSSFlow Team (pizone)
If you have any questions or requests regarding this Privacy Policy or your account data, please contact us: