Listenbox

Managed YouTube publishing

How Listenbox uses YouTube permission, private preparation, publication approval, playlists, and account disconnection.

Published Updated

The permission Listenbox requests

Listenbox requests only https://www.googleapis.com/auth/youtube.force-ssl when you connect a YouTube publishing destination. YouTube's youtube.upload scope is insufficient: it does not authorize videos.update, which applies the metadata and visibility you approve, or playlistItems.insert, which performs optional playlist placement.

Listenbox uses the publishing scope for these operations:

  • channels.list identifies the authorized channel.
  • playlists.list displays that channel's existing playlists.
  • videos.insert uploads media you provided with private visibility.
  • videos.list monitors processing and verifies the video's state.
  • videos.update applies the approved title, description, and final public, unlisted, or private visibility.
  • playlistItems.list and playlistItems.insert prevent duplicate placement and optionally add the video at position zero in your selected playlist.
  • videos.delete is used only to compensate an unpublished, Listenbox-created back-catalog upload when that operation is cancelled.

Listenbox does not access or modify ratings, comments, or captions. A direct YouTube import by itself requests read-only access and never publishes to YouTube. If the same account is also connected for publishing, Listenbox uses one canonical shared connection, so disconnecting it stops both uses.

What you approve for every publication

Connecting a destination does not authorize all future uploads by itself. You must first save the destination's required settings and an explicit default visibility. For a normal episode, Listenbox shows the final title, description, and visibility for review. For a back-catalog run, you choose one final visibility for the run. Each action also requires this certification:

I certify that I have the necessary rights and that this content complies with YouTube's Community Guidelines.

Listenbox records that approval for the specific episode or run. Later changes to destination defaults do not alter work already approved.

Private preparation and final delivery

Listenbox prepares each new YouTube upload as private. Publishing the episode changes that same video to the final visibility you selected—even when the selected final visibility is private—and optionally adds it once to the chosen playlist. Publishing the RSS episode and finalizing YouTube use one visible, idempotent dashboard action, while their durable outcomes remain independent.

Removal, disconnection, and external revocation

Removing a show's publishing destination stops publishing for that show and removes its settings and unfinished delivery state. It does not revoke a Google connection still used by another destination or import, and it does not delete YouTube videos. Deleting a Listenbox episode or podcast also leaves its published YouTube videos untouched. Manage or delete published videos in YouTube Studio.

Disconnecting a YouTube account from team settings is account-wide. Listenbox requests immediate revocation from Google, removes the stored token and provider-derived Authorized Data, and stops dependent publishing and import work. If Google already considers the token invalid, local cleanup still completes. Published YouTube videos remain untouched.

Listenbox schedules validation daily. Each active connection becomes due once its last successful validation is 25 days old. Validation refreshes the Google access token, confirms the authorized channel, refreshes channel and selected playlist details, validates stored delivery references, and removes stale provider-derived caches. This keeps active connections and Authorized Data inside the 30-day limit without waiting for a publishing action.

If access is revoked in Google Account settings, Listenbox detects it during the next authorized operation or scheduled validation. Confirmed invalid authorization stops dependent YouTube work, removes the unusable credential and related Authorized Data, and notifies team members who can reconnect. Published videos remain on YouTube. Temporary network failures, timeouts, malformed responses, rate limits, and Google server errors are retried and never treated as revocation.

YouTube Terms of Service · Google Privacy Policy · Listenbox Terms · Listenbox Privacy Policy