Private YouTube uploader

Privacy policy

Effective date: 15 October 2026.

Hypnotic Shorts YouTube is operated by Noor for his own YouTube channels. Its connection client is named Hypnotic Shorts uploader. This app uses YouTube API Services. This page explains the data used by this uploader. Google's handling of data is described in Google's Privacy Policy.

What the tool uses

The tool receives Google OAuth access and refresh tokens so it can act on the selected channel. It stores those tokens with the OAuth client details, the channel's ID and title, an expected account label and the connection time. Google handles sign-in; the tool does not receive or store a Google password.

For each upload, the tool reads the video file and sends it to YouTube with its title, description, tags, category, visibility and audience/disclosure settings. It reads the resulting channel, visibility and upload/processing status to check the result.

It keeps an upload receipt containing the local file path, size, dimensions, duration and file fingerprint; the upload metadata; channel and video IDs; times and status; and the operator's approval, review and copyright-check declarations. The receipt also contains the Notion and Drive links supplied by the operator. The uploader does not fetch those pages or use this Google connection to read Drive files.

Why this data is used and where it goes

This data is used to connect the correct channel, upload approved content, confirm the result and prevent duplicate uploads. The uploader communicates with Google for sign-in, token refresh, channel checks and uploading. Uploaded videos and metadata are held by YouTube under the selected visibility settings and Google's policies.

Connection files and receipts are stored on the operator's computer or server with access restricted to the operating-system account that runs the tool. Authorized operators and automation may read upload metadata and results to manage the workflow. Credentials must not be placed in AI chats, public pages or source repositories. The uploader does not sell account data or use it for advertising.

Retention and removal

The current tool has no automatic retention or deletion job. The operator handles retention and removal manually. Google-returned API data must be refreshed or removed within 30 days unless YouTube's policies permit longer storage. A request to delete this data must be handled within seven days. Connection files must be removed when access is no longer needed or is revoked.

The operator's original video files and independently created approval records are managed separately from Google-returned API data. The operator keeps the records needed to identify prior uploads and prevent duplicates, subject to the applicable YouTube storage rules. Workflow copies and backups must also be included when handling a deletion request. Contact the operator below to request removal.

To stop future access, remove this app from Google Account connections, then stop the uploader and remove its saved connection files from each computer, server and any backup. One app connection may cover more than one channel, so revocation can stop other channel connections too.

Removing app access or a local file does not delete videos already uploaded to YouTube. The channel owner manages those videos in YouTube Studio. To remove local videos, receipts or workflow copies, contact the operator. Before removing upload history, stop publishing and reconcile existing YouTube uploads so the deleted history cannot cause duplicate posts.

Contact: jamakzai12@gmail.com. Return to the homepage.