Compliance Information

YouTube API Use

How Viral Ops uses official Google / YouTube API Services.

Viral Ops uses official Google / YouTube API Services to support an authorized channel publishing and reporting workflow. Viral Ops does not use browser automation to control YouTube Studio and does not scrape authenticated YouTube pages.

OAuth scopes

https://www.googleapis.com/auth/youtube

Used for:

Identifying and verifying the authorized YouTube channel
Uploading authorized video assets
Managing supported video metadata and publication state
Reconciling remote YouTube video state

https://www.googleapis.com/auth/yt-analytics.readonly

Used for:

Retrieving YouTube Analytics metrics for the authorized channel
Displaying internal reporting and performance information

Currently authorized channel

Channel name	PulseDrop
Handle	@thepulsedrophq
YouTube Channel ID	`UCLAHMO0EQtV2Zk5PrKQquJA`

The immutable channel ID is used to ensure Viral Ops cannot accidentally upload to another YouTube channel associated with the same Google account. If a different channel is authenticated, publishing is blocked.

Viral Ops is the software / API client under review. PulseDrop is the YouTube channel currently authorized and managed through Viral Ops — it is not the name of the API client.

YouTube metrics vs. Viral Ops metrics

Viral Ops displays two different kinds of number, and keeps them visually separated wherever they appear together.

Supplied by YouTube	Views, likes, comment counts, engaged views, watch time, average view duration, average view percentage, shares, subscribers gained and lost. These come directly from the YouTube Data API and YouTube Analytics API.
Calculated by Viral Ops	Engagement rate, subscriber conversion, watch minutes per view, views per hour. These are independently generated by Viral Ops, are not sourced from the YouTube API, and are not provided or approved by YouTube.

Viral Ops-derived figures are labelled as such in the application interface, in a separate panel from YouTube-supplied data, and the API response that carries them also carries the disclosure text. Viral Ops does not relabel a YouTube value as its own, and does not present its own calculation as a YouTube metric.

Additional data policy status

Viral Ops has applied for the additional YouTube API policy covering derived metrics and extended storage of statistical data. That application is pending and has not been granted. Until Google approves it, Viral Ops operates entirely under the ordinary data policies and does not rely on the extended 36-month storage period.

Data use

Viral Ops does not sell YouTube API data.
Viral Ops does not use YouTube API data for advertising profiles.
Viral Ops does not provide YouTube API data to advertising networks.
Viral Ops does not access unrelated YouTube channels without OAuth authorization.
Viral Ops does not use browser automation to control YouTube Studio.
Viral Ops does not scrape authenticated YouTube pages.
The application uses official Google / YouTube APIs only.

Retention and deletion

Stored YouTube data is subject to automated retention rules enforced by the application: video titles, descriptions, creator names and comment text are refreshed or deleted within 30 days; analytics and statistics for the authorized channel are kept only while that authorization remains active and is reconfirmed at least every 30 days; statistics for channels that have not authorized Viral Ops are deleted within 30 days.

Authorization can be revoked from within Viral Ops or from the Google security settings page. Stored data can also be deleted on request without disconnecting. Full detail, including the applicable deadlines, is in the Privacy Policy.

Viral Ops never deletes content from YouTube. Deleting the data Viral Ops has stored has no effect on videos, comments or any other content held by YouTube.

Project status

Public publishing capabilities are subject to the permissions and compliance status granted to the associated Google / YouTube API project.