← Wacky Insights Shorts Automation

Privacy Policy

Last updated: 7 September 2026

Overview

Wacky Insights Shorts Automation is a personal application used by the owner of the Wacky Insights YouTube channel. It is not a public service and is not intended for use by third parties. The application uses Google OAuth 2.0 and YouTube API Services to upload original videos to the owner's own YouTube channel.

YouTube API Services

Wacky Insights Shorts Automation uses the YouTube Data API. By using functionality provided through YouTube API Services, use is also subject to the YouTube Terms of Service and the Google Privacy Policy.

The application requests the https://www.googleapis.com/auth/youtube.upload OAuth scope so it can upload completed videos and associated upload metadata to the channel owner's YouTube account.

Information accessed and used

The application accesses only the Google/YouTube authorization needed for the owner to upload videos. It uses that authorization solely to perform owner-requested YouTube upload operations. The application does not use the YouTube Data API to read comments, subscribers, viewing history, analytics, advertising information, or other users' YouTube data.

The application does not sell Google user data, use it for advertising or profiling, or share it with third parties for unrelated purposes.

Data storage and security

OAuth client credentials and authorization tokens used by the automation are stored in private, access-controlled configuration such as repository secrets. They are not intentionally exposed in the public website or public source code.

The application does not maintain a public user database and does not maintain a separate database of YouTube user data retrieved from the YouTube Data API.

Data retention and deletion

Authorization credentials are retained only for as long as they are needed to operate the owner's automation. The owner can revoke the application's Google/YouTube authorization at any time from Google Account third-party connections. After revocation, the application can no longer use that authorization.

The owner can also delete stored OAuth credentials or tokens from the application's private configuration. Because the application is personal-use only and has no third-party accounts or public user database, there is no separate end-user account data retained by the application.

Google API Services User Data Policy

Use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements, where applicable.

Contact

Questions about this Privacy Policy or requests relating to stored authorization data can be sent to wackyhearts@gmail.com.