Privacy Policy
Last updated: August 18, 2026
This Privacy Policy describes how Creator Upload Automation accesses, uses, stores, and protects information when using YouTube API Services and Google OAuth 2.0.
1. Scope
Creator Upload Automation is a private desktop tool used solely by the developer for YouTube channels owned or managed by the developer. The application is not offered to third-party users.
2. YouTube API Services
Creator Upload Automation uses YouTube API Services. By using features that interact with YouTube, the user is also subject to the YouTube Terms of Service.
3. Information accessed
The application may access YouTube and Google-authorized data necessary to perform its functions, including:
- YouTube channel identifiers and channel titles.
- Video identifiers, titles, descriptions, visibility settings, thumbnails, upload status, processing status, and publication status.
- OAuth authorization tokens required to access the YouTube API on behalf of the authorizing user.
The application does not request, collect, or store the user's Google or YouTube password.
4. How information is used
Authorized data is used only to upload and manage videos on the developer's own YouTube channel, apply metadata and thumbnails, and verify upload or publication status. The application does not use authorized data for advertising, profiling, surveillance, or unrelated secondary purposes.
5. Storage
OAuth tokens and workflow metadata are stored locally on the developer's computer. This website itself does not provide a login form, does not collect YouTube account credentials, and does not intentionally use analytics, advertising trackers, or cookies.
6. Sharing and sale of data
Creator Upload Automation does not sell authorized user data. It does not share authorized user data with unrelated third parties. Data is transmitted to Google/YouTube only as necessary to use YouTube API Services.
7. Retention and deletion
Locally stored authorized data is retained only for as long as necessary to operate and verify the developer's publishing workflow. The user may delete locally stored application data and OAuth tokens. If authorization is revoked, related stored authorized data will be deleted as soon as practicable and within the period required by applicable YouTube API Services policies.
Deleting data stored by Creator Upload Automation does not delete data stored by YouTube. YouTube content must be deleted through YouTube or an authorized client that supports deletion.
8. Revoking access
The user can revoke Creator Upload Automation's access through the Google Account settings for third-party connections and permissions. After access is revoked, the application will no longer be able to access the authorized YouTube data.
9. Security
The application uses OAuth 2.0 and stores credentials locally with restricted file permissions. Reasonable technical and organizational safeguards are used to reduce the risk of unauthorized access.
10. Google Privacy Policy
Google's handling of information is described in the Google Privacy Policy.
11. Contact
For privacy questions about Creator Upload Automation, contact the developer using the support email listed for the application in the Google OAuth consent screen.