Privacy Policy
Effective 12 October 2026
BlipScope ("we", "the Service") is an independent YouTube niche-research and analytics tool. This policy explains what we collect, why, and what we do with it. We do not sell personal data, and we do not use it for advertising.
Information you give us
- Account details. When you sign in with Google we receive your name, email address and profile picture from your Google account. Accounts created with an email and password store that password only in securely hashed form; we never store it in readable form.
- Content you create in the app. Watchlists, swipe-file folders and notes, creator briefs, research plans and text you paste into tools such as Script X-Ray, Title Scorer, Prompt Studio or Draft Review. Saved briefs and plans include the audience, production constraints, evidence links, hypotheses, outcomes and lessons you choose to enter.
- Draft Review inputs. Your original video stays on your device. When you choose Analyze, selected compressed frames, an optional thumbnail, your title, promise and pasted transcript are sent for review. Your saved creator brief is also used when available.
- Billing details. If you subscribe to a paid plan, payment is handled entirely by Stripe. We never see or store your card number. We retain only a subscription identifier and plan status.
Browser extension
Connecting the extension stores your BlipScope session credential and email in local extension storage, accessible to trusted extension contexts. It also stores appearance and discovery-tool preferences. Disconnecting removes the stored credential and email. The extension uses your existing account session; signing out invalidates that session.
On supported channel and video pages, the expanded research panel sends only the identifiers needed to look the research up: the video identifier, its uploader's channel identifier, or a public channel handle where the channel identifier is not on the page. Card research and keyword research run when you click their buttons; keyword research sends the selected YouTube search query. Saving research sends the identifiers, folders, notes and group choices you select to your BlipScope account. These requests are associated with your account. The extension does not read your general browsing history, cookies or YouTube Analytics data.
The three-video comparison shortlist remains in the current tab's memory and clears on reload. Titles and image files entered in the extension's local packaging preview remain on your device, are not uploaded by that tool and clear on reload. The same applies to the thumbnail compressor, which resizes and re-encodes an image you choose entirely on your device. Opening a research plan is a separate action; saving information in the app stores it under the app's normal account policies.
Some extension tools never contact BlipScope. Copy title reads the title of the video you clicked from the page and places it on your clipboard. Opening a full-size thumbnail loads the image directly from YouTube's image server in a new tab. The optional feed filters (hide Shorts, hide videos you have started or watched) are off until you turn them on, run on your device and send nothing.
YouTube data
BlipScope uses YouTube API Services: the YouTube Data API v3 and, for the features described under "Your own YouTube channel" below, the YouTube Analytics API. By using BlipScope you are also agreeing to the YouTube Terms of Service, and Google's Privacy Policy applies to data obtained through the API.
We retrieve and store publicly available information about YouTube channels and videos — titles, descriptions, thumbnails, view counts, subscriber counts, like and comment counts, durations and publication dates. This is public channel data. Research about other people's channels uses only this public data: we cannot see anyone else's private YouTube Analytics, watch history or account.
Your own YouTube channel (optional)
Optional channel features ask you to connect your Google account with extra YouTube permissions. We ask only when you choose one of them, and Google shows you exactly what is being granted before you agree. Nothing on this list is requested when you simply sign in.
- Detect my channel (permission: "View your YouTube account",
youtube.readonly). We read only the ID of the YouTube channel your Google account owns, so we can link it to your BlipScope account. We store that channel ID with your account. We do not read your subscriptions, playlists, watch history, comments or private videos through this identification feature. - Connected YouTube Analytics in Chat (permission: "View YouTube Analytics reports for your YouTube content",
yt-analytics.readonly). Only when you explicitly include connected Analytics in a Chat run may it read reports for your own channel. Selected results are processed and retained as described below. The former standalone analytics screen and its weekly report are retired. - Private uploads (when activated; permissions:
youtube.readonlyandyoutube.upload). With your explicit consent we verify the selected channel and send your chosen original video, title, description, tags and optional thumbnail to YouTube. We set the video to private. You review it and decide whether to publish in YouTube Studio. This feature does not make videos public or delete them.
To make these requests on your behalf, when you choose a connected channel feature, we store the access and refresh tokens Google issues with your account. They are used only for the channel features you authorize, including optional private uploads. Your YouTube data is never shown to other users, sold, used for advertising, or used to train AI models, and it is not shared with anyone except the infrastructure providers named under "Where data lives", who process it only to run the Service.
BlipScope's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Retention. Non-statistical data obtained from the YouTube Data API — such as video titles, descriptions, thumbnails and channel names — is refreshed or deleted within 30 days of retrieval, in line with the YouTube API Services Developer Policies. Statistical data (view, subscriber, like and comment counts) and the metrics we derive from it are retained so we can show how a channel changes over time, and are deleted once no longer needed for that purpose. You can ask us to remove any channel from our index at any time using the contact address below, and we action such requests within 30 days.
Estimates are ours, not YouTube's. Revenue, RPM and outlier figures shown by BlipScope are calculated independently by BlipScope from public data. They are estimates only — they are not reported earnings, are not obtained from the YouTube API, and are not endorsed or verified by YouTube or Google.
You may revoke BlipScope's access to your Google and YouTube data at any time via Google's security settings page. Once you do, the stored tokens stop working and we can no longer make authorized requests to your account. To have the stored tokens and your linked channel ID deleted as well, email us at the address below; we action such requests within 7 days.
How we use information
- To provide the Service — authenticating you and returning research results.
- To compute estimates and scores (see the Estimates section in our Terms).
- To send account and service emails. The former Goldmine and weekly analytics notifications are retired.
- To enforce plan limits and prevent abuse.
- To respond to you when you contact us.
Public web research (optional)
When you enable public web research in Chat or submit AI Keyword Research, the search query goes to the configured provider: Tavily, or Exa in the legacy configuration. Legacy Exa search also receives an optional research objective when you supply one. Tavily receives only the search query. When you choose to read a public page, its URL goes to Tavily Extract or Jina Reader, according to that configuration. Retrieved evidence identifies its sources and observation times; each retrieved excerpt names the service used. Chat uses public web providers only when you enable Public web for that run. AI Keyword Research uses public web evidence as part of the submitted research request. Public web tools are disabled for runs using private YouTube Analytics. Do not submit passwords, private account links or confidential information to public web research. We do not forward your browser cookies, Google tokens or account credentials.
Results include the source URL and the time BlipScope retrieved the result. The provider may return a cached or incomplete snapshot. Standalone search and page excerpts are cached separately for your account for up to 10 and 15 minutes respectively. If you use an excerpt in Chat, it becomes part of that run's existing retention period. These features do not grant access to private, paid or blocked content, and do not use your research to train BlipScope's model weights. Tavily, Exa and Jina process requests under their own service terms and privacy policies.
Where data lives
The Service runs on Cloudflare Workers, with data stored in Cloudflare D1, KV and private R2 storage. Payment processing uses Stripe. Text you submit to AI-assisted tools and selected Draft Review frames and thumbnails are processed by Cloudflare Workers AI to generate a response. Idea Check, and the ask box when you choose "Let BlipScope choose", may also send the idea or request you typed, with related public YouTube video details, to TypeSafe (typesafe.ai), which returns only a choice or rating among options we define. This processing happens outside your device; otherwise the ask box works out which tool to open on your device. We use no advertising or tracking networks and set no third-party analytics cookies; the only cookie we set is the one that keeps you signed in.
Chat research. Starting a run sends your request, retrieved public evidence and any report you select to Cloudflare Workers AI for planning and recommendations. Retired Creator Brief preferences are not applied. Only if you choose to include connected YouTube Analytics may the run use reports available under your existing Google grant. Research requests, bounded tool results and reports are stored with your account for up to 30 days, or 6 days for runs that allow private Analytics. Expired records are removed by hourly cleanup. Research Plans are retired; previously saved records are retained under the existing account data controls. Saving inspiration in Swipe Files is an explicit action. A run may continue after you close the browser; Stop run prevents further operations, although an already submitted request may finish. These inputs are not used to train our models.
Creator media (when activated). Reviewing a media estimate does not generate files. When you approve generation, the selected saved script and visual descriptions are processed by Cloudflare Workers AI to create artwork and English narration. Choosing cinematic video also sends visual descriptions and relevant script excerpts to Runway to generate clips. The media controls identify the selected production style before you start. Drafts containing connected private Analytics require a separate confirmation before this media processing. BlipScope does not send your social account credentials to either media provider and does not use these inputs or outputs to train its own models.
Generated images, narration and clips are held in private storage associated with your account for up to seven days, ending earlier when the source conversation expires. Downloads check your current access and expiry. Expiry and account deletion queue the associated files for cleanup; files awaiting cleanup cannot be downloaded through the app. Provider processing and retention are also governed by the applicable provider terms. Small generation reservation records without script or media content may remain temporarily to enforce usage limits. Generation can continue after you close the page. Cancelling stops further generation work; an already submitted provider request may still finish and incur cost.
Final thumbnail composition and MP4 assembly run in your browser using the generated assets. The resulting downloads remain on your device; BlipScope does not upload or publish them to your social accounts. Keep the browser and device available while exporting. Downloaded copies are under your control and are not removed when the cloud assets expire.
Imported local analysis. Soup / Video Watcher report imports send only the normalized text report, sampled coverage, timestamped observations and quality labels you preview. BlipScope does not upload the original video, local paths, raw prompts or frame files through this importer. Imports expire after 30 days. You must have permission to share the report; importing it is not consent to model training.
Private upload storage. Video chunks and an optional thumbnail pass through BlipScope to YouTube; they are not saved as media files in BlipScope storage. An encrypted upload-session reference expires after 24 hours. Upload progress and metadata are retained for up to 6 days and then removed by hourly cleanup. Forget removes the BlipScope record, and Cancel stops further upload work; neither action deletes a video already received by YouTube. Manage that video in YouTube Studio.
Draft Review storage. BlipScope does not save submitted draft frames or thumbnails in its application storage. Review results remain in the current page and are not automatically saved to your account. If you choose to transfer suggestions to a research plan and save it, those text notes are stored with your account; the draft media is not included. These application-storage choices are separate from the processing of your inputs by Cloudflare Workers AI described above.
Saved workspace content. Creator briefs and research plans are stored with your account until deleted. You can edit or clear your brief and manage your saved plans in the workspace. Deleting your account also deletes its saved brief and research plans.
Your choices
You can change your password from Account → Security at any time. You may request access to, correction of, or deletion of your account and its associated data by emailing businesskemkud2000@gmail.com. We action deletion requests within 30 days.
Children
BlipScope is a business tool and is not directed at children under 13, and we do not knowingly collect their personal information.
Changes
If we make material changes to this policy we will update the effective date above and, for significant changes, notify account holders by email.
Contact
Questions about this policy: businesskemkud2000@gmail.com