DopeStream Whop Publisher

Privacy Policy

How DopeStream handles information.

Policy version: 17 October 2026

This policy covers DopeStream Whop Publisher, the personal content application operated by the owner of dopeasspapi.com. It uses YouTube API Services to manage the owner’s authorized @thedopestream channel.

1. Operator and scope

The application is intended for its owner, not for public registration or connecting unrelated people’s channels. Contact the operator at dopeassbalr@gmail.com about access, correction, revocation or deletion. This policy covers the application’s Google and YouTube data processing; Google’s own processing is described in the Google Privacy Policy.

2. Information accessed and stored

• Authorization: OAuth access and refresh tokens, authorized scopes, token-expiry information and connection-verification records. The application does not receive the Google account password.
• Channel identity: the authorized YouTube channel ID, title and handle, where provided by the API, to prevent operations on a different channel.
• Video and publishing information: video IDs, titles, descriptions, channel association, privacy and scheduling settings, audience settings, paid-promotion declarations, processing status, and API responses or error information needed to verify an operation.
• Owner-provided project material: source footage, rendered videos, subtitles, captions, campaign instructions, source-rights evidence, approvals, content hashes and publishing receipts.

The dedicated connection currently requests youtube.force-ssl and offline access. Its workflow does not request YouTube Analytics or Reporting API scopes, contacts, Gmail, calendars or unrelated Drive files. Although Google’s permission includes deletion, ratings and comments, those operations are not implemented in this publishing workflow.

3. Purposes and limitations

Information is used to verify the owner’s channel, prepare and upload authorized videos, apply approved metadata and advertising disclosures, schedule approved releases, verify results, prevent duplicate uploads and diagnose failures. Offline access supports token refresh for these functions. Google-derived data is limited to the owner-facing features described here and is not sold, used for ad targeting or transferred to data brokers. DopeStream follows the Google API Services User Data Policy, including its Limited Use requirements.

Google authorization is separate from permission to publish. The application does not use the dedicated grant to manage other channels. It does not treat campaign participation, earnings or advertising eligibility as verified merely because a platform connection works.

4. Storage and security

The Windows desktop implementation encrypts saved OAuth credentials with Windows Data Protection API (DPAPI), bound to the owner’s Windows account. Decrypted credentials are used in memory for authorized API calls. Google authorization and API requests use encrypted HTTPS connections; the desktop authorization flow returns through a temporary listener bound to the local computer’s loopback address.

Media, captions, reports, approvals and API response snapshots are stored in the owner’s local project folders. Selected status records are copied to the owner’s private Command Center and its backups. These ordinary project files are not all individually encrypted by the application. Protection also depends on Windows access controls, device security and any backup or synchronization services the owner enables. Such services may hold additional copies; DopeStream does not independently verify every device or provider’s storage location.

5. Sharing and service providers

Google/YouTube receives video files, metadata and API requests when the owner authorizes those operations. The owner’s private Command Center receives selected workflow and publication records. TikTok publishing through Metricool is a separate connection; the dedicated Google OAuth tokens are not supplied to Metricool or TikTok by this workflow.

If the owner expressly uses an AI assistant or another agent for support, selected project information, API response data or screenshots may be shared with that provider under the owner’s instructions and the provider’s terms. This is not required for the daily local runner. OAuth secrets should not be pasted into assistant messages or public pages. Google user data must not be used to train or improve generalized AI or machine-learning models. This policy does not claim that every external assistant’s data-use settings have been independently audited.

Access is limited to the owner and agents the owner expressly authorizes, except where a disclosure is required for security or law. Application data is not provided to advertisers, brokers or other campaign participants for their independent use.

6. Retention and deletion

The owner retains authorization credentials only while needed for the authorized connection. Older encrypted credential generations and backups can also exist and must be included when removing access. YouTube API response data is subject to YouTube’s storage rules: ordinary stored API data must be refreshed or deleted within 30 days; any permitted longer-lived data remains subject to the applicable authorization checks. Original footage and metadata supplied by the owner are distinct from data retrieved from YouTube.

Retention and deletion are owner-operated procedures; the current application does not provide an automatic account-erasure button or a verified background purge of every backup. The operator is responsible for reviewing and refreshing or deleting API snapshots, and for locating relevant copies in local reports, private Command Center records and backups. These procedures must not be used to keep API data beyond the applicable YouTube limits.

To request deletion, email dopeassbalr@gmail.com with the channel handle and the records concerned. Do not send passwords or OAuth tokens. After confirming the request, the operator will delete the application’s relevant stored user data as soon as possible and within seven calendar days, including applicable backup copies. Deleting an application record does not delete the video or data held by YouTube. Removing publishing history can affect duplicate protection, so further publishing must be held until safe authorization and records are established again.

7. Revoking Google access

You can revoke DopeStream Whop Publisher’s access at any time in Google Account permissions. Removing the Google grant prevents continued authorized access but does not, by itself, erase every local file or backup. Notify the operator to complete local deletion. Following a direct revocation/deletion request, related authorized data is removed as soon as possible and within seven calendar days. Authorization checks must also detect revocation through Google and trigger removal within the deadlines in the YouTube API Services Developer Policies.

Revocation or local deletion does not automatically remove a video or cancel a schedule already stored by YouTube. To remove or change content on YouTube, use YouTube Studio or another expressly authorized method. This workflow does not implement video deletion.

8. Website visits and changes

These information pages do not collect Google passwords, initiate OAuth or embed a YouTube player. The static hosting provider, Cloudflare, may process visitor IP addresses and request metadata to serve and secure these public pages, under its Privacy Policy. This hosting does not receive the application’s local OAuth token files or private publishing records. These pages add no analytics scripts, advertising pixels, contact forms or embedded video players. Any future change in website tracking must be disclosed before it is enabled.

If Google-data access, purposes or sharing materially changes, this policy and the application disclosures must be updated, and fresh consent obtained before the new use begins. Any rights available under applicable data-protection law remain unaffected.