What this policy covers
This policy explains how NeuroFilter.AI handles information when you use the Chrome extension, the NeuroFilter website, and related account, billing, and support features.
This version is effective April 23, 2026. If we make material changes, we will update the date on this page and publish the revised policy at this same URL.
What the extension processes on your device
NeuroFilter.AI reads YouTube data inside your browser so it can score visible recommendations and apply focus controls without sending your watch context to NeuroFilter servers.
Video titles, descriptions, channel names, transcript or caption snippets when available, and the visible YouTube page context are processed locally to calculate relevance, hide or mute low-fit recommendations, and apply focus-mode settings.
That on-device analysis is the core of the product. NeuroFilter servers do not receive the YouTube titles, descriptions, channel names, transcript snippets, or browsing context that the extension analyzes for filtering.
- Visible recommendation cards and watch-page metadata on youtube.com
- Transcript or caption text fetched from YouTube when available for local scoring
- Your chosen filter threshold, reveal mode, and focus-mode layout settings
Data stored locally in your browser
The extension stores settings and working data locally so the experience stays fast across sessions. This local storage can include interests, disinterests, filter settings, theme and device preferences, cached text payloads, cached scores, usage counters, and local auth session state.
IndexedDB caches text payloads and inference scores for up to 7 days to avoid repeated work. Those local caches are purged on a rolling basis.
- chrome.storage data for extension settings and session state
- IndexedDB caches for text payloads and scores with a 7-day TTL
- Local usage counters used to enforce plan limits on the device
Cloud account and profile data we store
If you create or use a NeuroFilter account, we store the account data needed to authenticate you, sync account status across devices, localize pricing, and support billing and entitlement checks.
This may include your email address, Supabase user ID, display-name snapshot if available, country code, plan type, billing cadence, renewal or expiration dates, Pro status, student status, and similar account-state fields.
We also store operational records tied to account features such as pricing-route selection, transaction references, referral state, license redemption state, and founder-support or audit records when authorized admins troubleshoot account issues.
- Authentication and account identifiers managed through Supabase
- Plan and billing state such as country, cadence, expiry, and entitlement flags
- Referral, license-redemption, and support or audit records tied to your account
Interests, disinterests, and optional AI expansion
Your manually entered interests and disinterests are stored locally in the extension. If you are signed in and use synced account features, your base interests, visible interests, generated interests, and effective interest profile may also be stored in Supabase so your setup can follow you across devices.
For signed-in users who use interest-profile sync, NeuroFilter may send your entered interests through the Supabase edge function `sync-interest-profile`. That function can call Google Gemini to generate additional related interest terms.
This cloud expansion step is optional and additive. It helps expand your interest vocabulary, but it does not replace the extension's on-device scoring. The actual scoring of YouTube content still happens locally in your browser.
- Base interests you enter directly
- Visible interests shown in the UI after sync or refinement
- Generated and effective interest terms plus LLM metadata such as provider, model, and prompt version
Billing, student verification, referrals, and licenses
Paid plans, renewals, and customer-portal actions are handled through Dodo Payments and server-side Supabase functions. NeuroFilter does not process or store full payment-card numbers inside the extension.
If you verify student status, we use your confirmed account email and academic-domain matching rules to determine eligibility and store student-verification dates, free-window timing, reverification timing, and eligibility-expiration timing.
If you use referral or promotional license features, we store referral codes, referred-by state, signup counts, bonus months, license key metadata, redemptions, pending discounts, and related transaction records needed to apply those benefits correctly.
- Checkout session creation and billing state synchronization
- Student-verification status and eligibility windows
- Referral-code, reward, license-key, redemption, and discount state
Third parties and service providers
We share data only with service providers that are necessary to run the product or comply with law, security, or fraud-prevention obligations.
- Supabase for authentication, database storage, and edge functions
- Dodo Payments for hosted checkout, subscriptions, customer portal access, and transaction webhooks
- Google Gemini, only through the optional synced-interest expansion workflow described above
- Hugging Face and its delivery CDNs so the browser can download model files used for on-device inference
- Microsoft Azure for hosting the public website and legal pages
How we use data and our limited-use commitment
We use data to provide and improve NeuroFilter.AI's single purpose: helping users make YouTube more intentional through on-device scoring, account sync, billing, and directly related support tools.
NeuroFilter.AI uses accessed data only to provide or improve the extension's user-facing focus filtering, account, billing, and support features in accordance with the Chrome Web Store User Data Policy, including the Limited Use requirements.
We do not sell personal data. We do not use accessed data for advertising, profiling unrelated to the extension's user-facing purpose, creditworthiness decisions, or data-broker activity.
Humans do not review user data except when one of the following limited situations applies: you ask for support on a specific issue, we need to investigate fraud or security abuse, or we must comply with a legal obligation. When authorized founder-support tools are used, those actions are logged in admin audit records.
Retention, deletion, and your choices
Local cached YouTube payloads and scores are retained in the browser for up to 7 days unless you clear extension storage or uninstall the extension sooner.
Cloud account, billing, referral, license, and support records are retained for as long as needed to operate the service, enforce promotions, prevent abuse, resolve disputes, meet tax or legal obligations, and maintain accurate account history.
If you want us to delete your cloud account data, contact piyushpal2828@gmail.com. We may retain limited records where required for billing, fraud prevention, legal compliance, or legitimate recordkeeping.
Security and contact
We use HTTPS for network requests, restrict admin tooling, and rely on managed infrastructure for authentication, database security, and payment processing. No system can promise absolute security, but we design the product to minimize the most sensitive data transfers by keeping the main recommendation analysis on-device.
For privacy questions, support requests, or deletion requests, contact piyushpal2828@gmail.com.