Privacy policy
Effective November 19, 2026.
Google data the tool uses
When the operator authorizes Video Uploads, the tool uses YouTube permissions to read the authorized channel’s name and identifier, check that it is the expected channel, and upload selected videos to that channel. It sends the selected video, title, description, category, and audience setting to YouTube. It reads the resulting video identifier, channel identifier, and privacy status to check the transfer. It does not request Gmail, contacts, or Drive access.
Storage and retention
The operator stores the OAuth refresh credential in 1Password. The tool obtains short-lived access tokens as needed. Local transfer records keep the file path, file hash, title, video and channel identifiers, visibility, and transfer status. They do not store OAuth tokens. The operator retains these records as part of the video project and can remove them at any time.
Use and disclosure
The tool uses Google data only to authorize the requested transfer, verify the intended channel, and report the transfer result. It sends the selected video and its metadata to Google for YouTube processing. It does not sell Google data, use it for advertising or model training, or give other users access to it. This site has no app analytics, account forms, or uploader credentials.
Revoke access and remove data
The operator can remove Video Uploads access in their Google Account and remove the saved credential and local transfer records separately. To remove an uploaded video, use YouTube Studio. Removing OAuth access does not delete videos already uploaded.
For questions, use the support address shown on the Google consent screen for Video Uploads. See the Google Privacy Policy for Google’s handling of data.