Data handling
Privacy information
Updated September 22, 2026. Operator: Noah Trujillo. Contact: noahtru0505@gmail.com.
Data used
With the channel owner's Google authorization, the app accesses the authorized YouTube channel's identity, uploads owner-approved video files and their titles, descriptions and publication settings, and reads video status and performance information. It does not ask for or store a Google account password.
Locally, the app stores scripts, media assets, revision comments, approvals, quality-check evidence, publication records, performance reports and operating records. OAuth credentials are stored in protected files on the owner's computer, outside the source repository and outside dashboard responses.
Purpose and sharing
The app uses this information to operate the owner's channel, process approved uploads, avoid duplicate uploads, retain editorial decisions and measure content performance. Uploading an approved video sends its content and metadata to YouTube. Publicly released video content and metadata are visible on YouTube.
If the owner enables the optional OpenAI revision planner, the app sends relevant draft content, revision comments and creative preferences to OpenAI to produce a supported edit plan. This connection is separate from Google authorization. Google OAuth tokens are not included in those planner requests. Other media providers may receive production inputs when the owner enables their workflows.
The app has no advertising or data-sale feature. Its local dashboard is not intended to be exposed publicly. The public website hosting these information pages is separate from the local dashboard and may process ordinary website request information under the website host's policies.
Retention and control
The current implementation retains local production and performance records and local backup snapshots until the owner removes them. There is no automatic retention deadline. Backups include the database and media but exclude OAuth and API credential files. The owner must also remove backup copies when deleting retained records.
The owner can revoke the app's Google access through Google's account permissions page. Revoking authorization prevents further authorized API access but does not itself remove videos already uploaded to YouTube or locally retained files. Videos can be managed in YouTube Studio. For questions or removal requests concerning the app's local records, contact the operator at the address above.