Privacy, in plain language.
This policy explains what the SuperFilter Chrome extension, website and APIs handle, why they handle it, and the choices available to you.
Effective and last updated: September 22, 2026.
Data handled on your device
SuperFilter reads the visible public content and metadata needed to filter supported YouTube, X and Reddit pages, including titles, descriptions, creator names, links and page context. Rules, preferences, counters and filtering decisions are normally processed and stored in the extension on your device. The website demo also runs locally. SuperFilter does not read private messages or request your complete Chrome browsing history.
Accounts, authentication and cloud sync
If you create an account, we handle your name, email address, account ID and authentication tokens through Supabase Auth. Password sign-in also sends your password to Supabase Auth; SuperFilter does not store a readable copy. If you choose Google sign-in, Google verifies your identity and shares your name and email with Supabase Auth. We do not request access to your Google Drive, Gmail or other Google data. The extension stores session tokens locally so you can stay signed in. If you use cloud sync, Supabase stores your profiles, rules, preferences and rule-feedback history for your account.
Personalization and activity
If you explicitly enable YouTube personalization, the extension records likes, unlikes and whether you watched at least 75% of a video. Topic and keyword counts, salted hashes for up to 100 recent videos, and a pool of up to 240 visible recommendation candidates may stay locally for up to 30 days. That candidate pool can include video IDs, URLs, titles, descriptions, creator information and thumbnails. You can pause personalization or clear this data in the extension.
AI interpretation and optional online context
When you request AI rule interpretation or smart topic enrichment, the rule text or topic and the necessary language and region context are sent through our server to Groq. AI request metadata, such as a pseudonymous installation or account ID, model, token counts, status and rate-limit data, is stored in Supabase; rule text is not stored in usage metrics. If you separately consent to improving the parser, an unrecognized rule, language and occurrence count may be retained. If you enable online context, public titles and snippets of up to 700 characters per item may also be sent for analysis.
Feedback, support and approximate location
Product feedback stores your message, category, pseudonymous installation ID, interface language, extension version, plan and keywords derived from the message. Vercel may provide a two-letter country code derived from your network address, and the service processes a one-way network hash for abuse prevention and rate limits. We do not collect GPS or precise location. Website support-chat messages are sent to Groq to generate the reply and are not stored by SuperFilter. Do not include sensitive information in rules, feedback or chat messages.
Billing and payments
Stripe collects and processes payment-card details on its hosted pages; SuperFilter does not receive full card numbers. To activate and manage Pro, we store or process the Stripe customer and subscription IDs, selected plan or price, subscription status and period, renewal state and payment-confirmation status. The extension receives only the plan and entitlement information it needs to unlock features.
Other website and operational data
The site stores your selected language in a first-party cookie and browser storage. A beta signup, when available, stores your email and signup time. Our systems also process security logs, request timing, success or error status and limited technical metadata needed to operate, secure and improve the service.
Service providers and limited use
We use Vercel for hosting and network delivery, Supabase for authentication and database storage, Google for optional Google sign-in, Groq for requested AI features and Stripe for billing. They process data only to provide those services under their applicable terms. We do not sell user data, use it for advertising or credit decisions, or transfer it for purposes unrelated to SuperFilter's single purpose. Our use and transfer of user data complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
Retention, security and your choices
Local data remains until you clear it, remove it through the extension or uninstall the extension. Account and synced data remains while your account is active or as needed for the service, legal obligations, fraud prevention and billing records. Feedback remains until it is deleted or no longer needed. We use HTTPS for data in transit and restrict administrative access. You can use the extension without an account for local features, disable optional sharing and personalization, clear learned data, sign out, delete synced profiles or contact us to request access or deletion of account data.
Privacy questions, access or deletion requests: discord.gg/UM5AzQahMQ