YouTube Studio Automation

Owner-operated application

Privacy policy

Last updated: 17 November 2026.

YouTube Studio Automation is operated by Tyrone for his own three channels: Next Tense, Fortune Theory and Era Unknown. It has no public registrations, customer accounts or subscription service. Privacy questions and deletion requests can be sent to mostynventures@gmail.com.

Information accessed and its purpose

The application uses YouTube API Services. It accesses channel identifiers and names to confirm the destination, and video metadata, visibility, processing status, thumbnails and caption information to validate owner-authorised uploads. It stores local production files, approval records, job history and upload receipts to support review, recovery and duplicate prevention.

Read-only YouTube Analytics access has been authorised for future channel-performance reporting. Recurring live analytics collection is not active. When enabled with the owner’s approval, channel-level reports will be used to assess the owner’s videos and inform production decisions.

Google authorisation

youtube.readonly
Read channel and video information for identity and status checks.
yt-analytics.readonly
Read the authorised channel’s analytics reports; no analytics write access.
youtube.force-ssl
Support approved video, thumbnail and caption operations. Google grants broader content-management permissions, including deletion capability, than this application currently uses. The application’s local approval controls restrict actual actions; the permission itself is not read-only.

Google handles sign-in and consent. The application receives access and refresh tokens, not the Google password. It does not request Gmail, Drive, contacts, payment information or Google account passwords through this integration.

Storage and security

Each channel’s tokens are stored separately in macOS Keychain. The application’s working Desktop OAuth client configuration is stored in a local file restricted to the owner’s account. Job records, API readback records and production files remain on the owner’s Mac; they are not all encrypted by the application. Protection of other local records depends on the owner’s Mac login, disk-encryption and backup settings; this policy does not claim that those settings have been enabled or audited.

Credentials are excluded from public pages, source-control exports and review packages. The public information pages do not contain channel tokens or connect to the local dashboard. Network authorisation and API traffic use Google’s HTTPS endpoints; the consent callback listens locally on the Mac.

Sharing and other services

Google receives authentication requests and API operations. Authorised uploads send the selected video, metadata, thumbnail and captions to YouTube with the approved visibility. Current live tests are private. This application does not sell Google user data or use it for advertising, credit decisions or general-purpose AI model training.

The runtime currently uses local production tools; paid external AI services and further vidIQ research are disabled. Sending Google-derived data to a new provider would require a separate, disclosed and authorised change. The owner may expressly authorise technical maintenance access to local records; Google credentials must not be shared in prompts or logs.

Google’s own handling of information is described in the Google Privacy Policy. Use and transfer of Google API information must follow the Google API Services User Data Policy, including its Limited Use requirements.

Retention, deletion and revocation

The current application stores local records until the owner reviews and removes or refreshes them. It has no automatic expiry, purge, revocation-cleanup service or self-service deletion interface. The owner is responsible for the following manual retention rules: keep tokens only while the connection is needed; refresh or delete other stored API data within 30 days; and retain eligible authorised analytics history only as needed, with authorisation and relevant video-existence checks at least every 30 days.

Request removal of locally stored Google/YouTube data by emailing the owner. The owner handles requests manually and is responsible for deletion as soon as possible and within seven calendar days. Following revocation, affected API data must be deleted as soon as possible and within 30 calendar days. The owner must review local records and backups under their control; these deadlines are operational duties, not automated features. Independently created scripts and media are separate from API-derived data.

Revoke access at Google Account permissions. Revocation stops future authorised access but does not itself erase local records or videos already uploaded to YouTube. Contact the owner for local deletion; use YouTube’s controls to remove content there. Unattended operation remains disabled pending validation of retention, revocation and recovery safeguards.

Information-page visitors and changes

The public information site is served through Cloudflare Pages. These page files contain no forms, advertising, analytics scripts or third-party embeds, and do not set cookies or use browser storage. Cloudflare processes visitor network information, such as IP addresses and request/routing data, to deliver and protect the site; its service may apply security mechanisms under its own policies. See Cloudflare’s Privacy Policy. Cloudflare hosts only these information pages, not the Mac application, its Google credentials, channel data or production files. Following a link or sending an email uses the destination service under its own policies.

Material changes to data use or permissions require an updated notice and appropriate owner consent before activation. Public publishing and the autonomous trial remain disabled.