Two personal command-line tools, run by one person on their own computer: one uploads that person's finished videos to their own TikTok drafts inbox, the other reads how their own published YouTube videos performed.
The operator produces short vertical videos on their own machine. When a cut is finished, this tool sends the video file to the TikTok Content Posting API, which places it in the operator's TikTok drafts inbox. Nothing is published.
The caption, the privacy setting and the publish time are chosen afterwards by the operator, by hand, in the TikTok app. The tool cannot set them and never asks the API to.
One person: the operator who runs it. It has no accounts, no sign-up, no server, and no other users. It runs on the operator's own computer and is authorized against the operator's own TikTok account.
The second tool asks YouTube about the operator's own published videos: how many views, likes, comments and shares each one has, and the average percentage of the video that viewers watched. The operator reads those numbers to judge which editorial choices were worth making.
It asks only about the authorizing channel's own uploads, and the answer is a total per video. It never asks for another creator's channel, and no individual viewer is named or counted separately.
One OAuth token per platform, on the operator's computer, so the tools do not have to ask for authorization every time, and a file of the numbers already fetched. That is all. See the privacy policy for the detail.
video.upload (TikTok) — place a video in the authorizing account's drafts inbox.youtube.readonly (Google) — list the authorizing channel's own videos and their public counts.yt-analytics.readonly (Google) — read that channel's own view statistics.
It does not request video.publish, so nothing it uploads to TikTok becomes
public without the operator publishing it by hand. Both Google scopes are read-only, so
nothing on the YouTube channel can be posted, edited or deleted through them.