Effective date: October 1, 2026
ViralBle Privacy Policy
ViralBle provides YouTube creator-research tools. This Privacy Policy explains what information we collect, how we use and share it, and how long we keep it.
ViralBle uses YouTube API Services. Before you use ViralBle, you must agree to this Privacy Policy. It is prominently displayed before access and remains available while you use the Service.
1. YouTube API Services
When you use ViralBle’s YouTube features, we use YouTube Data API Services to retrieve the public video titles, descriptions, thumbnails, statistics, and public comments needed to provide the feature. For Viral Shorts Radar specifically, this includes a broader, ongoing scan of public YouTube Shorts that ViralBle selects, not only channels you specify — see Section 3.
By using ViralBle, you agree to be bound by the YouTube Terms of Service. See the Google Privacy Policy for information about Google’s handling of data related to YouTube API Services.
We do not currently access YouTube data that requires authorization from your YouTube account.
2. AI analysis features and AI providers
ViralBle uses third-party AI providers to analyze public YouTube data (such as comments, titles and descriptions), video transcripts obtained through third-party transcript services, and the content you provide to its tools. We only send the minimum data each analysis needs. We do not send your account information, such as your email address, sign-in credentials or payment information, to any AI provider. The providers we currently use are Jev (via OpenRouter), DeepSeek and Google Gemini, each described below. We may add, replace or remove AI providers as ViralBle develops. Before we send data to a new provider, we will update this section to name it, describe what it receives and where it processes data, and change the effective date above; where required, we will ask for your consent again.
Comment Insights, Audience Requests, Outlier Intelligence, and My Channel’s competitor and niche channel discovery send the minimum public YouTube data described above needed for the requested analysis to DeepSeek. Before that, Comment Insights and Audience Requests first send public comment text to Jev to screen out comments that don’t suggest a video topic, so that only the remaining comments go on to DeepSeek. If DeepSeek has a defined technical failure, we may send the same minimized data to Google’s Gemini API to complete the request. We do not send your YouTube login credentials or OAuth tokens to any of these providers.
Jev (comment screening), via OpenRouter. For each public comment being analyzed, we send only the comment’s text and the title of the video it was posted on to Jev, a classification model made by TypeSafe AI, Inc. Jev returns only a score for how likely the comment is to suggest a video topic. We access Jev through OpenRouter, Inc., which routes the request to TypeSafe. We do not send the comment author’s name or channel, or any information about your ViralBle account. TypeSafe states that it will not train or fine-tune any model on customer inputs, that its services are hosted in the United States, and that it retains personal data for as long as reasonably necessary to provide its services. OpenRouter states that it does not use inputs or outputs for model training; it is based in the United States and may process data in the United States and other countries. See TypeSafe’s Privacy Policy and OpenRouter’s Privacy Policy.
DeepSeek. DeepSeek processes the minimized inputs ViralBle sends through its Open Platform API and returns AI-generated outputs. DeepSeek’s published Terms of Use state that it may, to a limited extent and subject to the encryption, de-identification, and irreversibility measures it describes, use inputs and outputs to provide, maintain, operate, develop, or improve its services and underlying technology. DeepSeek states that it directly collects, processes, and stores personal data in the People’s Republic of China. Its published retention period is not fixed to a specific number of days and may continue as needed for service delivery, legal or contractual obligations, and other stated purposes. See DeepSeek’s Open Platform Terms of Service, Terms of Use, and Privacy Policy.
Gemini (technical fallback and similarity matching). Gemini is used only through a Cloud project with active billing. We send data to Gemini’s text-generation models only when DeepSeek has a defined technical failure. Separately, we use Gemini’s embedding model (which converts text into numbers used to measure similarity, and generates no text) on every run of My Channel’s competitor and niche channel discovery, sending public channel titles, channel descriptions, video titles and excerpts of video descriptions; and to group the AI-generated topic titles and niche labels described in this section. Under Google’s Gemini API Paid Services terms, Google does not use prompts or responses to improve its products. Google retains them for a limited period only to detect and prevent policy violations and to meet required legal or regulatory disclosures. See the Gemini API Additional Terms.
Analysis shown by ViralBle is generated from AI output, whichever provider produced it. It is not YouTube data and is not published, approved, or verified by YouTube. Where it is shown alongside YouTube API Data, ViralBle displays a clear and prominent notice to that effect.
These AI-powered features are optional. You may decline, and the feature simply will not run; nothing else about your account or the rest of the Service is affected. These features are for professional and business use and are not directed to or available to individuals under 18.
3. Viral Shorts Radar
Viral Shorts Radar ranks short public YouTube videos (30 to 60 seconds long) whose public view counts are growing unusually fast, grouped by the kind of content idea they represent. It works differently from ViralBle’s other tools in three ways you should know about:
First, the videos it scans are not limited to your channel or the competitors you name. ViralBle runs its own scheduled scan of public YouTube Shorts, using search queries and channels it selects, independent of any single member, and records how each video’s public view count changes over time.
Second, ViralBle sends each scanned video’s public title and description to DeepSeek (see Section 2) to label the content idea and format. This runs on ViralBle’s own schedule, not in response to a member’s request; it uses no information about you and does not fall back to Gemini.
Third, the ranked videos and their labels are shared analysis, visible to every ViralBle member with access to the feature, not generated for you alone. What stays private to you is the list of videos you save and any feedback you give.
ViralBle labels this analysis as a detected pattern based on public evidence, not a prediction or guarantee that a format will perform well for any particular channel.
4. What we collect and why
| Category | Examples | Purpose |
|---|---|---|
| Account information | Email, display name, account identifiers | Sign-in and account management |
| Public YouTube data | Video titles, descriptions, thumbnails, statistics, public comments | Providing requested features |
| ViralBle-generated analysis | Topic suggestions and titles, outlier scores, Shorts format rankings and labels | Displaying results |
| Channel profile | Your channel, the competitor and niche channels you choose, business description | Tailoring analysis to your channel |
| Saved content ideas | Idea title, outline, notes, schedule date | Your private content-planning calendar |
| Payment information | Processed by our payment provider | Processing purchases |
| Usage data | Features used, request counts | Operating the Service and managing usage |
We do not knowingly collect information from children, and the AI-powered features described in Section 2 are not directed to individuals under 18.
Our free tools’ comment forms use Akismet, a third-party spam-filtering service, which may place a cookie on your device for that purpose.
5. How we share information
We share information with Google to provide the YouTube API features described above and the Gemini processing described in Section 2; with DeepSeek to provide the AI analysis features described in Section 2; with OpenRouter and TypeSafe AI to screen public comments with Jev as described in Section 2; with Paddle, our payment processor and merchant of record, to process ViralBle PRO purchases and prepaid credit packages; and with service providers that provide authentication, database hosting, and account or support email, only as needed to operate ViralBle.
Viral Shorts Radar’s ranked videos and labels are visible to other ViralBle members using the feature, as described in Section 3. Your channel profile, competitor list, and saved ideas are never shown to other members.
We do not sell your personal information.
6. Retention of public YouTube API Data
ViralBle deletes or refreshes Non-Authorized YouTube API Data, including public metadata, thumbnails, statistics, and comment text, no later than 30 calendar days after retrieval or its most recent refresh. We use reasonable efforts to display current API Data.
A Viral Shorts Radar video is removed from the rankings once it falls outside this 30-day window.
7. Your choices and rights
You may delete your ViralBle account and request deletion of stored data related to you through your account’s Profile page or by contacting support@viralble.com. We will delete that data as soon as possible and no later than seven calendar days after a valid request or account-deletion event, except where retention is required by applicable law.
Deleting data stored by ViralBle does not delete content stored on YouTube. To delete content from YouTube, use YouTube directly or an authorized API client that supports deletion.
If you used the legacy free-tool Google sign-in, you can review or revoke that connection through Google’s security settings page.
For a request about data DeepSeek, OpenRouter, TypeSafe AI or Google process directly as described in Section 2 — for example, a deletion request that reaches beyond what ViralBle itself stores — contact support@viralble.com and we will coordinate the applicable request with the relevant provider on your behalf.
8. Changes to this policy
We will update this Privacy Policy before material changes to our data practices. Where required, we will notify you or obtain consent before using information in a materially new way.
9. Contact
Questions about this Privacy Policy: support@viralble.com