WTW?WHY THIS WAY?Publishing integration
Legal · Updated 23 October 2026

Privacy policy

This policy explains how the WHY THIS WAY? YouTube publishing integration uses Google account authorization and YouTube channel data.

1. Who operates the integration?

The WHY THIS WAY? channel operator controls the automated publishing integration. Questions or requests may be addressed to whythiswayyt@gmail.com.

2. What data may be accessed?

  • Google OAuth authorization data necessary to act on the owner’s behalf, including a refresh token and short-lived access tokens.
  • The authorized YouTube channel's ID, name, ownership/authorization status and relevant metadata.
  • Videos and creator-provided publishing details: video file, title, description, thumbnail, captions, video ID, upload status and publication receipt.

Only accounts specifically authorized by the channel operator can use this integration.

3. Why and how is data used?

The integration checks that the authorized Google account controls the correct YouTube channel, creates or updates creator-directed videos, uploads thumbnails and captions, checks video processing and visibility, and prevents duplicate uploads. A periodic Google OAuth refresh check tests connection health without posting videos. Google data and credentials are not used for advertising, sold, or fed into content-generation or AI training models.

4. Storage, processors and access

OAuth credentials are held in restricted GitHub Actions secrets. Workflow logs are designed to record health status, not credential values. Publication records containing video IDs and non-secret metadata may be retained in the private project repository. Relevant processing services include Google/YouTube and GitHub Actions. Access is restricted to authorized project operators and necessary infrastructure providers. Information is retained only for operational, security and publication audit needs.

5. Sharing and disclosure

We do not sell Google user data or share it with advertisers. Data is sent to Google's YouTube services only as necessary to carry out a creator-approved upload or related operation. Hosting and automation providers process data for the defined purposes under their applicable terms. We may disclose information where legally required.

6. Revocation and requests

The channel owner can revoke OAuth access in their Google Account third-party connections. Access revocation stops future authorized operations until the owner explicitly reconnects. To request access, correction or deletion of project-held data, contact whythiswayyt@gmail.com. Removal of public YouTube content is managed separately in YouTube Studio.

7. Security and updates

HTTPS protects this information website. OAuth credentials are never published on the website; publication jobs use credential checks, restrictive permissions and controls against duplicate uploads. We may update this policy if the integration's data use changes and will show the revision date.

8. Google API Services User Data Policy

The integration is intended to comply with the Google API Services User Data Policy, including its Limited Use requirements where applicable.