Privacy Policy
Effective date: 18 July 2026
This Privacy Policy explains how NextWatch AI and its related website collect, use, store, and share information when you visit nextwatchaitool.com, install the NextWatch AI browser extension, use its YouTube and AI features, manage a subscription, or purchase additional AI credits.
Data and privacy disclosures at a glance
The following disclosures describe the current NextWatch AI Chrome extension, production backend, subscription system, analytics, and website. These disclosures are intended to match the Chrome Web Store privacy form.
Chrome Web Store data categories disclosed
Personally identifiable information; financial and payment information; authentication information; personal communications; location and technical request data; web history; user activity; and website content. Health information is not intentionally collected.
Primary service providers
1. Who we are
NextWatch AI is operated by Sidebrain. In this policy, “NextWatch AI,” “we,” “us,” and “our” refer to the operator of the NextWatch AI extension, website, and production backend. For privacy questions or requests, contact litesbook@hotmail.com.
2. What NextWatch AI does
NextWatch AI is a Chrome extension and related online service that enhances YouTube with AI chat, summaries, research, video search, scene and timestamp assistance, personalised recommendations, cross-session memory, playback controls, volume boosting, automatic quality controls, and visual effects. Some features operate entirely inside your browser. AI, subscription, analytics, security, and credit-balance features communicate with our service providers and production backend.
3. Information we handle
The categories below align with the disclosures presented in the Chrome Web Store. The specific information processed depends on which features you use.
| Category | Examples | Why it is used |
|---|---|---|
| Personally identifiable information | Email address supplied through ExtensionPay or Stripe; founder email used for private owner activation; internal account and installation identifiers. | To verify subscriptions, restore purchases, associate credit balances, provide account support, and secure access. |
| Financial and payment information | Subscription plan, paid status, billing interval, payment or checkout status, credit-pack type, purchase amount, and transaction/session references. | To activate paid features, process subscriptions and one-time credit packs, prevent duplicate fulfilment, manage cancellations, and maintain billing records. NextWatch AI does not receive or store full card or bank details. |
| Authentication information | ExtensionPay access credentials or API tokens, opaque founder-session tokens, extension installation ID, Chrome extension ID, and security session records. | To verify paid or founder access and prevent unauthorised use. Secrets are stored locally or server-side as appropriate; founder tokens are stored as hashes in the backend database. |
| Personal communications | Questions, prompts, instructions, follow-up messages, feedback, notes, and AI conversation content entered into NextWatch AI. | To provide AI answers, research, summaries, video search, scene finding, playback commands, and conversational continuity. |
| Location and technical request data | IP address, approximate region inferred by infrastructure providers, browser/device details, request timestamps, extension version, and service logs. | To deliver the service, apply rate limits, detect abuse, troubleshoot failures, secure accounts, and measure reliability. We do not request GPS or precise device location. |
| Web history | YouTube page URLs, video IDs, video titles, creators/channels, recently watched or selected videos, and continuation history. | To power video memory, “For You Now,” “Next Up,” learned shortcuts, continue-watching features, and relevant recommendations. |
| User activity | Clicks, skips, repeats, watch duration, completion signals, playback position, selected recommendations, feature usage, volume/speed/quality settings, and recommendation feedback. | To operate controls, personalise results, improve ranking, remember preferences, calculate AI usage, and understand aggregate feature performance. |
| Website content | Visible YouTube titles, channel names, descriptions, recommendation cards, captions/transcripts, timestamps, links, thumbnails, and other visible YouTube context needed for the requested feature. | To answer questions about the current video, create summaries and chapters, locate scenes, fact-check or research claims, search for related videos, and perform requested visual analysis. |
4. Information stored locally in the extension
NextWatch AI uses Chrome extension storage to keep product state and make features work across sessions. Local data may include:
- Theme, volume, speed, quality, AI Auto HD, 3D Glow, and other settings.
- Recent videos, watch progress, completion and skip signals, favourite or hidden creators, learned topics, recommendation feedback, and search results.
- Recent AI conversation history and session memory used for conversational follow-ups.
- An installation-specific client identifier, analytics identifier, cached subscription status, usage balance, and an opaque founder token when owner access is activated.
Local extension data normally remains on the device until it is cleared, reset, overwritten through normal use, or removed when the extension is uninstalled. Chrome may retain or synchronise browser information according to the user’s Chrome settings and Google’s own policies.
5. AI processing and OpenAI
When you use an AI feature, NextWatch AI sends your prompt and only the context reasonably needed for that request to our backend and OpenAI. Depending on the feature, this may include the current video title, channel, URL, description, timestamps, relevant caption/transcript segments, recent conversation, preference signals, viewing memory, or search query.
This information is used to generate the requested response, search assistance, summary, research result, scene location, recommendation, or playback action. NextWatch AI does not intentionally store full AI prompts, transcripts, video descriptions, or AI responses in its subscription and credit database. They may be processed transiently by our servers and may be retained by OpenAI under OpenAI’s API data controls, safety, and retention practices. OpenAI states that API data is not used to train its models unless the API customer explicitly opts in.
6. Subscriptions, account access, and payments
NextWatch AI Pro subscriptions are managed through ExtensionPay and Stripe. ExtensionPay may collect an email address and provide NextWatch AI with subscription status, plan information, and an access credential used to verify entitlement. Stripe processes subscription and credit-pack payments and may collect name, email, billing details, payment-method information, IP address, device information, and transaction data for payment, authentication, fraud prevention, compliance, and support.
Full payment-card and bank-account details are entered directly into payment-provider pages. They do not pass through or get stored in the public extension or NextWatch AI’s application database. Our backend stores billing records needed to maintain entitlements and credit balances, such as a hashed email identifier, account ID, plan interval, included and bonus credit balances, checkout-session reference, credit-pack type, purchase amount, and payment-fulfilment status.
7. AI usage credits and cost controls
For paid AI features, our backend records account-level usage information such as requests, feature type, included and bonus credits used, remaining credits, input and output token counts, research-call counts, estimated service cost, allowance dates, and error/refund status. This data is used to enforce plan allowances, provide usage summaries, protect the service from abuse, prevent duplicate charges, and keep purchased credits accurate.
8. Analytics
NextWatch AI uses a privacy-filtered Google Analytics 4 Measurement Protocol integration to understand aggregate feature usage and reliability. The extension sends allowlisted event names and limited parameters through our backend. Examples include panel opens, feature selections, completion or failure status, model tier, token and credit totals, volume/speed/quality changes, search usage, subscription actions, and credit-pack checkout events.
The analytics pipeline is designed not to accept or forward typed prompts, transcript text, video titles, video IDs, full URLs, watch history, email addresses, payment-card information, or founder activation secrets. A random installation identifier is one-way hashed before it is used as the Google Analytics client identifier. Google may independently process device, browser, session, and approximate-location information under its policies when Google Analytics or other Google services are used on the public website.
9. Website cookies and advertising
The public NextWatch AI website may use cookies, Google Analytics, Google AdSense, or similar technologies for website measurement, security, consent management, and clearly labelled advertising. Google and other website providers may process cookies, device identifiers, IP address, approximate location, page interactions, and advertising information under their own policies and user-consent settings.
The NextWatch AI browser extension does not use YouTube viewing data, AI prompts, transcripts, or extension activity to serve personalised, retargeted, or interest-based advertisements. Website advertising is separate from extension recommendation and AI data.
10. How we use information
- To provide, personalise, and improve the extension’s disclosed YouTube and AI features.
- To answer prompts, summarise or research videos, locate scenes, search YouTube, and execute requested playback controls.
- To remember settings, viewing progress, preferences, and conversation context across sessions.
- To verify paid and founder access, maintain AI credit balances, process purchases, and provide account support.
- To measure aggregate usage, troubleshoot errors, secure the service, enforce limits, prevent fraud and abuse, and comply with law.
11. Service providers and data sharing
We do not sell personal information. We share or transmit information only where reasonably necessary to provide the product, process payments, operate infrastructure, measure performance, secure the service, comply with law, or complete a business transfer. Providers may process data in countries other than the user’s own under their terms, privacy policies, and applicable safeguards.
- OpenAI — AI responses, research tools, and model processing. Privacy Policy and API data controls.
- ExtensionPay — subscription checkout, email-based purchase restoration, and paid-status verification. ExtensionPay.
- Stripe — payment processing, checkout, payment authentication, fraud prevention, and credit-pack transactions. Stripe Privacy Center.
- Google — Chrome Web Store distribution, YouTube platform services, Google Analytics, and website advertising where enabled. Google Privacy Policy.
- Render — production API hosting, server logs, security infrastructure, and PostgreSQL account/credit storage. Render Privacy Policy.
- Netlify — public website hosting, content delivery, request handling, and related infrastructure. Netlify Privacy Statement.
12. Data retention
- Local extension data: retained until cleared, reset, overwritten through normal use, or removed by uninstalling the extension.
- Account, subscription, and AI-credit records: retained while needed to provide the service, maintain purchased balances, resolve disputes, prevent fraud, satisfy accounting obligations, and comply with law.
- Founder and security sessions: retained until expiry, revocation, or deletion according to operational and security needs.
- Analytics: retained according to our Google Analytics property settings and Google’s policies.
- Infrastructure logs and provider data: retained according to the relevant provider’s settings, policies, legal obligations, and security requirements.
- AI content: not intentionally written to the NextWatch account and credit database; provider-side processing and retention are governed by OpenAI’s API data controls.
13. Security
We use HTTPS for network transmission, keep OpenAI, Stripe, analytics, founder, and database secrets on the production server, restrict backend requests to approved extension IDs, use opaque installation identifiers, hash certain account and session identifiers, verify Stripe webhook signatures, and apply rate limits and duplicate-request protections. No system is completely secure, and users should not submit information they do not want processed by the selected feature.
14. Chrome Web Store Limited Use disclosure
15. Legal grounds
Where applicable, we process information to perform the service requested by the user, with consent, to pursue legitimate interests such as security, reliability, fraud prevention, product improvement and billing administration, and to comply with legal obligations. The available legal basis may differ by country and by the feature used.
16. User choices and rights
- You may avoid transmitting AI content by not using AI features; local playback controls can operate without sending an AI prompt.
- You may clear extension storage, reset product state, or uninstall the extension at any time.
- You may use the Manage or Cancel Subscription controls to manage recurring billing through the payment provider.
- You may manage browser cookies, Google advertising preferences, and website consent settings through your browser and Google controls.
- Depending on applicable law, you may request access, correction, deletion, restriction, objection, portability, or withdrawal of consent by contacting us.
We may need to verify a request and may retain information where required for legal, accounting, fraud-prevention, security, or dispute-resolution purposes. Data held independently by a provider may also need to be requested directly from that provider.
17. Children’s privacy
NextWatch AI is not directed to children under 13, or the higher minimum age required in a user’s jurisdiction. We do not knowingly collect personal information from children below the applicable minimum age. A parent or guardian who believes a child has provided information may contact us to request review and deletion.
18. Changes to this policy
We may update this Privacy Policy when product features, providers, legal requirements, or data practices change. We will revise the effective date above and provide additional notice when required.
19. Contact
For privacy questions, requests, or complaints, contact litesbook@hotmail.com. Please do not include passwords, payment-card numbers, founder activation codes, or other highly sensitive credentials in an email request.