Privacy Policy
Privacy contact: bucketlistwish1@gmail.com
Short Studio Uploader (“the Application”) is a private Windows desktop application used solely by its operator to manage channels owned by, or expressly authorized to, that operator. It is not offered to customers, employees, or the public. The Application uses YouTube API Services and the YouTube Analytics API after the operator grants authorization through Google OAuth 2.0.
1. YouTube API Services and applicable policies
The Application's use of information received from YouTube API Services adheres to the YouTube API Services Terms of Service and YouTube API Services Developer Policies. By using the Application, the operator also agrees to the YouTube Terms of Service. Google's processing of information is described in the Google Privacy Policy.
2. Authorization scopes
The Application requests only scopes used by its implemented owner workflow:
| OAuth scope | Purpose |
|---|---|
youtube.upload | Upload an operator-selected video to the confirmed authorized channel. |
youtube.readonly | Verify the connected channel and retrieve owned-channel video metadata, status, statistics, and processing information. |
youtube.force-ssl | Apply operator-reviewed metadata, localized metadata, captions, visibility, and scheduling changes. |
yt-analytics.readonly | Read performance reports for channels authorized by the operator. |
The Application never asks for or stores the operator's Google or YouTube password.
3. Data accessed, provided, and created
- Channel data: channel ID, title, upload-playlist information, and basic channel statistics.
- Video data: video ID, title, description, tags, category, default language, duration, thumbnail reference, visibility, scheduling and processing status, audience designation, caption availability, and public engagement counts.
- Authorized analytics: owner-authorized channel and video performance reports, including views, watch time, audience retention, engagement, traffic source, geography, device, content type, and subscription status where the API makes those fields available.
- Operator-selected upload data: local video files, titles, descriptions, tags, category, audience and synthetic-media choices, localized metadata, caption files, and an optional scheduled publication time.
- Local operational records: upload queue state, resumable-upload state, returned video and caption-track IDs, processing results, errors, and timestamps needed to prevent duplicate or incomplete actions.
4. Purpose and user control
Data is used only to operate and verify the operator's own publishing and analytics workflow. Before a write action begins, the Application clearly shows the destination channel, content, metadata, audience setting, synthetic-media disclosure, visibility, captions, and schedule. Uploads require an explicit in-application review followed by a separate Windows confirmation. The Application does not automatically upload merely because a file appears in a folder.
The Application does not scrape YouTube, download YouTube audiovisual content, automate views or engagement, manage unrelated users, sell API data, build advertising profiles, or expose Authorized Data to the public.
5. Storage and security
OAuth tokens are encrypted using the operating system's secure storage and kept in a local application-data directory on the operator's access-controlled Windows computer. Queue records and analytics files are also stored locally. OAuth tokens and client secrets are excluded from the studio's analysis exports and are not intentionally placed in public source control.
This public information site does not provide an account system, does not run the desktop Application, and does not use advertising or cross-site tracking cookies.
6. Sharing
Upload content, metadata, authorization information, and API requests are transmitted to Google/YouTube only as necessary to carry out the operator's explicit actions. YouTube API Data is not sold, licensed, or shared with unrelated third parties. Authorized Data is visible only to the authorizing operator and agents expressly approved by that operator.
7. Retention and refresh
- OAuth tokens are retained only while authorization remains active and only for the purposes covered by the granted consent.
- Authorized non-statistical API Data is deleted or refreshed no later than 30 calendar days after retrieval unless a shorter period is required.
- Statistical API Data and clearly labeled operator-calculated metrics are retained only for the period permitted by the YouTube API Services Developer Policies and any written data-storage approval granted through a compliance audit. Until such approval is granted, applicable API Data is refreshed or deleted within the standard policy period.
- Local upload-source files created by the operator are not YouTube API Data and remain under the operator's own file-retention controls.
8. Revocation and deletion
The operator can review or revoke the Application's Google access at any time through the Google security settings page. Revocation prevents future authorized API access. Following revocation or a verified deletion request, the operator will remove the corresponding locally stored OAuth token and Authorized Data as soon as possible and no later than seven calendar days. Any other API Data related to an authorization found to be invalid is deleted within the applicable YouTube policy deadline.
To request access to or deletion of data, or to ask a privacy question, contact bucketlistwish1@gmail.com. Because the Application is owner-only, requests are handled directly by the sole operator after identity and channel authority are verified.
9. Changes
If the Application begins accessing or using data for a materially different purpose, this policy will be updated and renewed consent will be obtained where required before the changed use begins. The effective date above will be revised when this policy changes.