The short version. Barebyte Content OS is a private tool that only Barebyte operates, to publish videos of Barebyte's own games to Barebyte's own YouTube channel. It uses the YouTube API Services. It reads only what it needs to confirm the channel and its own uploads, keeps that on Barebyte's computer, and does not sell, share or use it for anything else.
Barebyte Content OS is not offered to the public. The only Google account that connects to it is the account that manages Barebyte's YouTube channel, and the only data it handles is that channel's. It processes no data about viewers, subscribers or anyone else.
Barebyte Content OS uses the YouTube API Services. By connecting a Google account to it, the account holder agrees to the YouTube Terms of Service. Google's handling of data is described in the Google Privacy Policy.
When the Google account is connected, it is asked to grant exactly two permissions (OAuth scopes):
https://www.googleapis.com/auth/youtube.upload — to upload a video that a person
at Barebyte has approved;https://www.googleapis.com/auth/youtube.readonly — to read the connected channel's
identity and the videos the tool uploaded.No other Google permission is requested.
Barebyte Content OS does not access comments, subscribers, viewing history, playlists other than the channel's own uploads, analytics, revenue, email, contacts or any other Google data.
Only to publish Barebyte's approved videos and to verify that they were published correctly. It is not used for advertising, it is not sold, and it is not used to train any machine-learning or artificial-intelligence model.
Barebyte Content OS's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Barebyte Content OS runs on Barebyte's own computer; Barebyte operates no server for it. The authorization token and the channel's identity are stored there, in files that only the operating system account running the tool can read. The record of each publication — the video's id, the channel's id, the approved title and description, the privacy setting, status and timestamps — is stored there too. None of this is placed in a source-code repository or sent anywhere other than to Google, as part of the requests described above.
None. The data described here is not shared with, sold to or disclosed to any third party. The only exchange is between the tool and Google's YouTube API Services, which is how the tool works. The videos themselves are published on YouTube at the privacy setting Barebyte approved.
Access can be revoked at any time from the Google account's security settings: security.google.com/settings/security/permissions. After revocation the tool can no longer read the channel or upload to it.
Barebyte Content OS is being connected to the TikTok API for Business (Accounts API). This section applies once Barebyte's own TikTok account has authorized it; until then the tool holds no TikTok data. Only Barebyte's own account connects; no other TikTok user's data is processed.
Use of TikTok is subject to the TikTok Terms of Service and the TikTok Privacy Policy.
These pages are hosted on GitHub Pages. Like any web host, GitHub may process ordinary web-request metadata — such as your IP address and user agent — for delivery, abuse prevention and security, under GitHub's own practices. These pages set no cookies, load no analytics, and load no scripts, fonts or images from third parties.
If Barebyte Content OS's use of YouTube data changes — a new permission, new data, a new use — this policy will be updated before that change is used, and the effective date above will change with it.
Open a privacy inquiry (GitHub issue tracker for Barebyte's policy pages). Questions are answered publicly, so the answer is visible to everyone with the same question.