Saxplained Studio · Last updated 25 August 2026
Saxplained Studio is a private desktop application used by its operator to publish and manage videos on YouTube channels that the operator owns. It is not offered to, sold to, or installed by the general public.
The only person who signs in to this application is its operator, using their own Google Account to access their own YouTube channels. The application has no other users and no user accounts of its own.
When the operator signs in, the application requests the following Google API scopes:
youtube.upload — to upload video files to the operator's own channels.youtube.force-ssl — to set video titles, descriptions, thumbnails, visibility and
scheduling, and to add videos to the operator's own playlists.youtube.readonly — to list existing videos and playlists on those channels.yt-analytics.readonly and yt-analytics-monetary.readonly — to read
view and revenue statistics for those channels, for the operator's own reporting.All of this data belongs to the operator's own YouTube channels. The application does not access any other person's Google Account, YouTube channel, or data.
The application runs locally on the operator's computer. OAuth tokens issued by Google are stored on that computer, in the operator's user account, and are used only to authenticate subsequent requests to the YouTube Data and YouTube Analytics APIs. Video files, metadata and analytics retrieved from YouTube are held locally for the duration of the task being performed.
There is no server, no hosted database, and no analytics or telemetry collected by this application. No data leaves the operator's computer except in requests sent directly to Google's APIs.
Google user data obtained through these APIs is not sold, transferred, or disclosed to any third party. It is not used to train, develop, or improve any generalised artificial intelligence or machine learning model. It is used solely to perform the publishing and reporting actions the operator initiates.
Stored OAuth tokens can be deleted at any time by removing the application's local credential files, which immediately ends its access. The operator may also revoke the application's access at any time at myaccount.google.com/permissions. Revoking access invalidates the stored tokens permanently.
This application's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Any change to how the application handles Google user data will be reflected on this page, with the revision date above updated accordingly.
Questions about this policy can be sent to the support address listed on the Google consent screen for this application.