Privacy Policy
Last updated: September 17, 2026
This Privacy Policy describes how Publisher handles information when using YouTube API Services.
YouTube API Services
Publisher uses the YouTube Data API Services.
Publisher uses Google OAuth authorization so that a user can authorize Publisher to upload videos to a YouTube channel controlled by that user.
Publisher does not request, collect, or store the user's Google or YouTube password.
Use of information received from Google APIs is subject to the applicable Google and YouTube policies, including the Google Privacy Policy.
Information Publisher accesses
Publisher may access or use information necessary to perform authorized YouTube publishing operations, including:
- OAuth authorization credentials and tokens
- The identity of the YouTube channel associated with the authorization
- Information returned by YouTube about videos uploaded through Publisher
- Video identifiers and upload results
- Video metadata supplied for publishing, such as title, description, category, and privacy status
Publisher is designed primarily as a locally operated application for use by the person who authorized the YouTube account.
How information is used
YouTube-related information is used only to provide functionality requested by the user, including:
- Authenticating access to the user's YouTube channel
- Uploading user-selected videos
- Setting user-selected video metadata
- Setting the visibility selected by the user
- Confirming the result of an upload
- Performing other YouTube operations that the user explicitly requests and authorizes
Publisher does not use YouTube API data for advertising, profiling, surveillance, or sale to third parties.
Storage
OAuth credentials and authorization tokens used by the locally operated version of Publisher are stored on the user's local system.
Publisher may locally retain information needed to operate the publishing workflow, such as uploaded video identifiers and associated publishing metadata.
Publisher does not intentionally maintain a centralized database of users' YouTube API data.
Sharing
Publisher communicates authorized information with Google and YouTube as necessary to perform YouTube API operations requested by the user.
Publisher does not sell YouTube API data.
Publisher does not share authorized YouTube API data with unrelated third parties.
Video visibility and user control
The user controls whether an uploaded video is designated private, unlisted, or public, subject to limitations imposed by YouTube.
Publisher will not intentionally change the visibility of an existing YouTube video unless the user expressly requests that action.
Revoking access
Users may revoke Publisher's access to their Google account through Google's permissions management page:
Google Account — Third-party connections and access
After authorization is revoked, Publisher will no longer be able to use that authorization to access YouTube API Services.
Locally stored authorization credentials and associated YouTube API data should also be deleted when authorization is revoked or when the user requests deletion.
Deleting locally stored data
A user may delete Publisher's locally stored authorization data by removing Publisher's saved OAuth token or credentials through the application's authorization-management functionality or by deleting the corresponding local credential files.
A user may also request deletion of data stored by Publisher by contacting the developer using the contact method below.
Deletion of data stored by Publisher does not delete videos or other information stored by YouTube. Content stored by YouTube must be deleted through YouTube itself or through an authorized application that supports deletion of that content.
When deletion of Publisher-stored user data is requested, the data will be deleted as soon as reasonably possible and within the periods required by the YouTube API Services Developer Policies.
Security
Publisher is designed to protect OAuth credentials and YouTube API data from unauthorized access.
Users should not publish OAuth client secrets, refresh tokens, access tokens, or other authentication credentials in source-code repositories or other publicly accessible locations.
Cookies and advertising
The Publisher informational website does not use YouTube API data for advertising.
The locally operated Publisher application does not require advertising cookies or tracking cookies to provide its YouTube upload functionality.
Third-party services linked from this website, including Google, YouTube, and GitHub, may operate according to their own privacy policies.
Google and YouTube policies
Use of Publisher's YouTube integration is also subject to:
Contact
Questions, privacy concerns, or requests concerning Publisher may be submitted through the Publisher project's GitHub issue tracker: