Data & access
Privacy policy
Last updated: 17 November 2026
Botovod YouTube is a personal utility for the owner of the Botovod YouTube channel. Access is limited to the channel owner.
What the application accesses
The owner authorizes the application on Google's OAuth consent screen. The application requests two permissions:
youtube.readonlyโ read YouTube information, used by the current authorization utility to check that the connected channel is the intended channel.youtube.uploadโ upload videos to the owner's channel when the owner approves a video. The authorization utility itself does not upload or publish videos.
The current channel check receives the channel ID and channel information returned by the YouTube Data API. OAuth access and refresh tokens allow the utility to make authorized requests without asking for the owner's Google password.
How data is used
Google data is used only to authorize access to the owner's channel, verify the intended channel, and carry out uploads approved by the owner. Uploads involve sending the approved video and its supplied metadata to YouTube.
The current authorization utility has no channel analytics database and does not download private videos. It does not sell Google data, send it to advertising or analytics services, or send it to AI models for training.
The application follows the Google API Services User Data Policy, including its Limited Use requirements. Data obtained through Google APIs is used for the disclosed channel operations; it is not reused or transferred to another application for an unrelated purpose.
See the Google Privacy Policy.
Storage and sharing
OAuth credentials, tokens, and the verified channel ID are saved in protected local storage controlled by the owner.
The current utility communicates with Google's authorization and API services for the requested operations. It does not provide third parties with the owner's tokens or channel data.
Credentials remain locally stored until the owner replaces or deletes them.
Revoking access and deleting data
The owner can revoke the application's access through the Google security settings. Google explains how to review and remove access.
The owner can also delete the locally stored credentials. Removing Google access does not delete local files; deleting local files does not by itself revoke Google's authorization. Both steps are available to the owner.
Deleting credentials does not delete videos already uploaded to YouTube. Those videos remain under the owner's control in YouTube.
This information site
These static pages do not include sign-in forms, public registration, analytics scripts, tracking pixels, or a way to submit credentials. Google authorization takes place on Google's own consent screen through the local utility.
When these pages are hosted online, the hosting provider may process standard web-request information to deliver the site and maintain its security.
Contact and changes
For privacy questions, use the support email displayed on the Google consent screen for Botovod YouTube.
This policy will be updated before the application begins using Google data for a different purpose. Any additional Google permissions will require the owner's consent.