Privacy Policy

Account and session information. AW uses account/session information needed to authenticate you, maintain a signed-in session, protect the service, and associate your AW account with the connected creator workspace.

YouTube channel and video data. With youtube.readonly, AW reads the YouTube channel you authorize and read-only resource metadata needed for the creator catalog and historical comparisons. This can include channel identity and video identifiers, titles, descriptions, tags, thumbnails, publication state, and related resource metadata returned by the YouTube Data API.

YouTube Analytics data. With yt-analytics.readonly, AW reads authorized private channel Analytics used to build creator history, baselines, historical comparisons, forecasts, checkpoints, and experiments.

Google authorization identity. When AW's withdrawal controls are active, AW requests openid so it can derive a one-way keyed hash identifying the Google authorization principal associated with a grant. This is used to group and revoke the correct authorization safely. AW does not persist the raw Google OpenID subject or ID token.

Creator-entered content. Features such as Preflight may process text you enter, including a proposed title, idea, description, tags, outline, or script context.

AW uses authorized Google/YouTube data to provide creator-facing functions that are visible in the product: channel cataloging, historical analytics, creator baselines, comparisons, forecasts, checkpoints, experiment tracking, and creator-specific evidence.

AW keeps creator-specific authorized data and analysis separate from Algorithm Intelligence, which is an independent public-web research layer. AW does not use one creator's private YouTube Analytics to make platform-wide claims for other creators.

AW does not sell Google user data, use Google user data for advertising or ad targeting, determine creditworthiness, or use Google user data to train AW as a general-purpose machine-learning model.

OpenAI embeddings for Preflight. When you affirmatively opt in and run semantic Preflight, AW sends text needed to find topic-similar historical videos to OpenAI's embeddings API. This may include draft text you enter (such as title, idea, description, tags, outline, or script context) and current public title/description/tag metadata from videos in your authorized YouTube catalog. AW uses the returned vectors only for the visible similarity/forecast workflow. The current Preflight preview does not persist those embedding vectors in AW's database.

Independent public research. AW also uses OpenAI services in a separate Algorithm Intelligence pipeline to analyze public-web sources and evidence. That research pipeline is not a substitute for, or a pooling of, creators' private YouTube Analytics.

AW stores authorized Analytics/statistical history and AW-created creator evidence only for the creator-facing purposes described in this policy and subject to applicable YouTube API policies, the user's authorization, and any additional permissions required for particular derived analytics.

Mutable YouTube resource metadata such as titles, descriptions, tags, thumbnails, and channel names is periodically revalidated and refreshed. AW's lifecycle checks authorization and catalog state on a recurring schedule and rotates superseded mutable metadata rather than retaining stale copies indefinitely.

AW also periodically verifies that the connected Google authorization remains valid. If AW can no longer verify authorization, it stops using that authorization and handles associated API data according to applicable YouTube API revocation and deletion requirements.

After creator-data withdrawal, AW may retain minimized security, withdrawal, and audit evidence for limited operational periods. The current design permits short-lived withdrawal escrow evidence for up to 7 days and minimized audit evidence for up to 30 days; those records are designed not to retain or reconstruct the deleted creator dataset.

You can revoke AW's Google authorization at any time from your Google Account permissions ↗. Revoking Google access prevents AW from using that authorization for future Google/YouTube API access.

AW periodically reconfirms authorization state. If authorization has been revoked through Google, AW deletes associated API data as soon as practicable and within the time required by the YouTube API Services policies.

Authenticated users can request deletion of the YouTube channel data stored by AW from Settings. AW's withdrawal workflow is designed to stop new creator work, revoke the isolated Google grant when appropriate, and erase qualified creator-scoped data as soon as possible and within 7 calendar days of the user's request.

Deleting data stored by AW does not delete videos, channel data, or other content stored by YouTube. To delete content from YouTube itself, use YouTube or another authorized client that supports those actions.

Revoking Google authorization and requesting deletion of AW-stored data are related but distinct controls. Using AW's deletion control is the clearest way to tell AW that you want its stored creator data removed.

AW is designed so creator-specific authorized data is accessible only within the authenticated creator context that authorized it, except where limited access is required to operate, secure, troubleshoot, comply with law, or complete a user-requested data-control workflow.

AW does not request or store your Google or YouTube password. Google OAuth handles authorization to the requested scopes.

AW's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy ↗, including the Limited Use requirements.

If AW changes how it accesses, uses, stores, or shares Google user data, this policy and the relevant in-product disclosures will be updated before the new use is introduced. Where required, users will be asked to consent to the updated use before their Google user data is used for that new purpose.

Questions about privacy, Google/YouTube data access, or deletion can be sent to support@algowhisper.app. You can also review the Support page.