Privacy policy

What access is requested

With the account owner's permission, the application requests three YouTube Data API OAuth scopes: youtube.upload to upload videos; youtube.readonly to identify the authorized channel and verify playlist membership; and youtube.force-ssl to add an uploaded video to the owner's selected playlist. Google documents youtube.force-ssl as allowing access to view, edit, and permanently delete YouTube videos, ratings, comments, and captions. The application uses that scope only for playlist insertion; it does not delete videos or modify comments, ratings, or captions.

What data is stored

Google OAuth access and refresh tokens are stored locally on the owner's Windows computer in the YouTube uploader's credential file. Recipe source links, files, video identifiers, playlist identifiers, and status receipts may also be stored locally. The OAuth client secret is stored locally. This website does not receive these credentials.

Sharing and disclosure

The application sends only necessary requests and content to Google YouTube services in order to perform the operations described above. Google processes requests under its own policies. The application does not sell Google user data, transfer it to advertising brokers, or provide public access to the owner's local authentication tokens. Uploaded unlisted videos can be watched by anyone with the direct video link.

Retention and deletion

Local data remains on the owner's computer until the owner removes it. The owner can delete the local OAuth token file, revoke access at Google Account permissions, and delete uploaded videos or playlists through YouTube.

Website analytics

This informational site includes no tracking scripts, cookies, or advertising code. The hosting service may process routine access logs according to its own policies.

Updates and contact

The policy may be updated when the application changes. For privacy questions, contact the developer at shutupchub@gmail.com.