Privacy policy

Information the app accesses

• Google authorization: access and refresh tokens issued after the owner grants permission. Google handles the sign-in process; the app does not collect the Google account password.
• Channel information: the connected channel's ID, title and handle.
• Video information: video IDs, titles, links, visibility and upload or processing status.
• Local publishing material: the video file, title, description, tags, audience declarations and delivery records selected for upload.

The current requested permissions are youtube.upload and youtube.readonly. The app does not request Gmail, Google Drive or AdSense API access.

How information is used

The app uses this information to identify the chosen channel, upload selected videos privately, check the result, and record delivery information. Local upload records help prevent accidental duplicate uploads.

The app has no advertising, profiling, data-sale or AI model-training functionality. Google user data is used for the publishing functions described here.

Storage and services involved

Google authorization tokens are stored on the owner's computer in a restricted local application folder. They are not part of this website or its hosted files.

Video files and delivery records are stored in the owner's project folders. Those folders may be synchronized by a storage service configured by the owner, including Google Drive. This is separate from the app's Google API permissions.

Selected videos and metadata are sent to YouTube through the API. When the owner operates the app through an AI-assisted desktop service such as Codex, selected project information and command outputs may also be processed by that service under its terms and account settings.

This informational website contains no account sign-in form, upload form, application database or analytics scripts added by the operator. The hosting service may process ordinary connection and security logs, such as IP addresses and request information.

Retention and deletion

Authorization tokens remain on the owner's computer until replaced or removed; Google may also expire or revoke them. Local project files and delivery records remain until the owner deletes them. This version of the app does not automatically delete those local records.

The owner can remove the local token files and project records from their computer. If project folders are synchronized or backed up, copies and retention settings in those services should also be reviewed. Deleting a local record does not delete an uploaded YouTube video; video removal is managed separately in YouTube Studio.

For help with access, correction or deletion, contact the operator as described below.

Withdraw Google access

You can revoke the app's access at any time from Google Account connections. Find the app and remove its access. Revocation prevents continued authorized API use; it does not itself erase local project files or uploaded videos.

Google and YouTube policies

Use of YouTube features is also subject to the YouTube Terms of Service and Google Privacy Policy. The app's use and transfer of information received from Google APIs must follow the Google API Services User Data Policy, including its Limited Use requirements.

Contact and updates

For app and privacy questions, contact the channel owner using the support email displayed on the app's Google consent screen.

The operator will update this page if the app's permissions or data practices change. The date above identifies the latest version.