AI Media OS
A privately operated automation system that its owner runs on their own computer to research, produce, manage and upload videos to their own YouTube channel.
AI Media OS is not a public service. It is not offered to, sold to, or made available to anyone other than its owner. There is no sign-up, no user accounts, no hosted product, and no way for a third party to connect a Google Account to it. It authenticates to exactly one Google Account — the owner's own — and uploads only to the owner's own YouTube channel.
What it is
AI Media OS is a personal production pipeline. It runs locally on the owner's own Windows machine, alongside a local database and task queue. Nothing about it is multi-tenant: there is one operator, one configured destination channel, and one Google Account.
Given a topic, it carries out the steps a single creator would otherwise do by hand:
- selects a subject and checks it is not a repeat of something the channel has already covered;
- researches it against published sources and records the citations;
- fact-checks dates, names, figures and central claims;
- drafts a script and captions;
- plans and generates the visuals and the synthetic narration;
- renders the finished vertical video locally with FFmpeg;
- runs automated quality checks covering technical integrity, visuals, audio, caption timing, factual grounding and copyright provenance;
- uploads the result to the owner's own YouTube channel as a private video.
Content that fails a quality check is quarantined for the owner to review and is never uploaded.
Its use of the YouTube Data API
AI Media OS uses the YouTube Data API v3 for exactly two purposes, and requests exactly two OAuth scopes to do so. Both are requested during a single authorization, because Google's installed-application flow does not support adding a scope incrementally afterwards.
| Scope | Why it is needed |
|---|---|
.../auth/youtube.upload |
To upload the finished video file to the owner's own channel, via videos.insert using a resumable upload. This is the scope that performs the actual upload, and it is the system's core purpose. |
.../auth/youtube.readonly |
To confirm, before any bytes are sent, that the account that just authorized is the intended destination channel. The system calls channels.list(mine=true) and compares the returned channel ID against the one it has been configured with. If they do not match — or if the check cannot be completed at all — the upload is refused and the mismatch is recorded. This scope is read-only and is used as a safety check, not to collect data. |
The same read-only scope is also used after an upload to read back the resulting video's own status — its privacy setting and processing state — to confirm the upload landed as intended on the owner's channel.
No other Google or YouTube API is used. The system does not read subscriber lists, audience or viewer data, comments, messages, contacts, email, files, or any other person's data.
Privacy and synthetic-content disclosure
Every upload is created as private. The system has no capability to publish publicly or to schedule a public release: a non-private upload requires an explicit, per-video authorization that the automation never constructs. Making a video public is a separate, manual decision the owner takes in YouTube Studio.
Because the visuals are AI-generated and the narration is synthetic, every upload is marked as containing altered or synthetic content, is declared not made for children, and carries a disclosure to that effect in its description.
Google API Services User Data Policy
AI Media OS's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
The privacy policy sets out in full what is accessed, how it is used, where it is stored, how it is protected, how long it is kept, and how the owner deletes it.
Documents
Contact
AI Media OS is operated by a private individual. Questions about the system, this site, or its handling of Google user data: 4317anahabedian@gmail.com