Last updated: 28 September 2026.
Yukkuri Upload Manager is a personal/internal desktop application used by the account holder to upload the account holder's own videos to YouTube. It uses YouTube API Services only for authentication, destination-channel identification, video upload, and thumbnail upload.
The application requests the OAuth scopes youtube.upload and youtube.readonly. These permissions allow the application to upload videos and thumbnails to an authorized YouTube channel and to identify the authenticated channel. The application does not request or store the user's Google password.
OAuth access and refresh credentials are stored locally on the user's computer so the user does not need to sign in for every upload. Video files, generated metadata, thumbnails, and upload-result records are also stored locally. The application does not maintain a remote user database.
Data is used only to authenticate the account, display the authorized destination channel, and upload the user's own selected video with user-reviewed metadata and visibility settings.
The application does not sell, rent, or share Google user data or YouTube API data with advertisers, data brokers, or unrelated third parties. Data is transmitted to Google/YouTube only as required to perform the authorized API operations.
OAuth credentials remain on the user's local computer until the user revokes access or deletes the local token file. Local project files and upload records remain until the user deletes them. The application does not intentionally retain remote copies of YouTube API data outside the user's local environment.
The user can revoke the application's access at any time from the Google Account connections/security settings. The application also supports local credential revocation and deletion of its locally stored OAuth token. The user can delete local project files and upload-result records at any time.
OAuth credentials are intended to remain on the user's own computer and must not be shared or committed to a public source-code repository. The application uses Google's OAuth 2.0 authorization flow rather than collecting account passwords.
Use of YouTube features is subject to the YouTube Terms of Service. Google's handling of information is described in the Google Privacy Policy.
[REPLACE WITH LEGAL NAME]
[REPLACE WITH CONTACT EMAIL]