Data handling

Privacy policy

Effective 25 October 2026

This policy describes the owner-operated Nevosoft Channel Studio production workspace and its local desktop uploader. Contact: blagodarq@gmail.com.

Google and YouTube information

When a channel owner authorizes the desktop uploader, it receives OAuth access and refresh tokens. It uses the YouTube API to identify the selected channel, including its ID and title, and to read upload and publication status for videos it manages. It submits the video, thumbnail, captions and metadata prepared by the operator to that channel.

The current desktop client requests youtube.upload and youtube.force-ssl. Google's management permission is broader than the features this tool uses: it can authorize changes and deletion of videos, ratings, comments and captions. The current uploader uses that permission for captions and channel/video checks; it does not automatically delete videos or act on comments.

How the information is used

Google user data is used to connect the intended channel, upload the owner-approved package and keep production records consistent with YouTube. The uploader checks the authorized channel ID against the configured destination before saving its connection. Uploads are requested as private.

Google user data is not sold, rented, used for advertising, used to build advertising profiles or used to train AI models. OAuth credentials are not sent to AI providers. Other production features may use AI with separately supplied production material; that does not give an AI provider access to the connected Google account.

Storage and security

Desktop OAuth credentials and channel tokens are stored on the operator's PC in a credentials folder excluded from the source repository. Protection of those local files depends on the PC's account and filesystem security. The desktop uploader sends requests to Google over HTTPS.

Video files, thumbnails, captions, metadata and production records are stored locally and may also be stored in the owner's private review studio hosted on Cloudflare. Channel IDs, uploaded-video IDs and status records may be synchronized there. The desktop client's Google OAuth credentials are not included in that synchronization.

These public information pages do not receive OAuth tokens or offer a Google sign-in flow. They include no advertising or analytics scripts. Cloudflare may process ordinary request information, such as IP addresses, browser details and request times, to deliver and protect the pages and operate hosting logs.

Sharing and access

Google receives the files, metadata and API requests needed for the YouTube operations the owner initiates. Cloudflare hosts the private production workspace, any review copies synchronized to it, and these information pages. Access to the private workspace is restricted to its authorized users. The tool does not publish private production files through these information pages.

Retention, revocation and deletion

Local authorization credentials are retained until the operator removes or replaces them. Production files and records remain until the operator deletes them. Removing a local token does not itself revoke Google's grant, and revoking access does not itself delete existing local files or videos already uploaded to YouTube.

You can revoke access from your Google account's third-party connections. To remove stored local authorization, delete the corresponding channel credential file on the PC. To request deletion of associated production records or review copies, contact blagodarq@gmail.com. Videos already uploaded to YouTube are managed separately in YouTube Studio.

Google API Limited Use

Nevosoft Channel Studio's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Changes and questions

This policy will be updated when the application's data practices change. The effective date appears above. Questions and data requests can be sent to blagodarq@gmail.com.