Privacy Policy

1. Use of YouTube API Services

The client uses YouTube API Services. By using the client, an authorized operator may permit it to upload videos to the operator’s channel and read channel identity, video details, upload status, and video statistics. The client uses Google OAuth; it does not ask for or store a Google account password. Please also read the Google Privacy Policy.

2. Information accessed and stored

• Authorization: Google OAuth access and refresh tokens. The refresh token is stored in the local operating system’s keychain; short-lived access tokens are used to make authorized requests.
• Channel and video information: channel ID and name, video files chosen for upload, titles, descriptions, tags, video IDs, upload and publication status, and related local workflow records.
• Performance data: public video statistics returned by YouTube, including views, likes, and comment counts, when the reporting workflow is used. The operator may retain local analysis records.
• Contact information: messages sent voluntarily to the email address below.

This informational website does not offer an account, collect form submissions, or set first-party analytics cookies.

3. How information is used and shared

The client uses this information to confirm channel identity, upload operator-selected videos, track the outcome of those uploads, and analyze performance. Video files and metadata selected for upload are sent to YouTube. The client is operated internally and does not sell API data or provide it to advertising networks. Authorized local operators can access the records needed to run the workflow.

4. Storage and deletion

Workflow records and any locally retained statistics are kept only as needed for operation, reconciliation, and analysis, subject to applicable YouTube API data rules. An authorized channel owner can request access to or deletion of locally held channel data by emailing abandeng515@gmail.com with the channel URL or ID. We will verify the request before removing applicable local records and associated stored authorization tokens. A request to delete local records does not itself remove videos already uploaded to YouTube; those videos can be managed through YouTube Studio.

Separately, an authorized user can revoke the client’s Google account access at any time through Google security settings.

5. Security

The client runs in an operator-controlled environment. OAuth refresh tokens are held in the operating system keychain rather than in the public website. Access to the local workflow and its records is limited to authorized operators.

6. Changes and contact

We may update this policy when the client or applicable rules change. The current version will be posted here with a revised effective date. For privacy questions, concerns, or data requests, contact abandeng515@gmail.com.