What this connector is
This is a private, owner-operated tool. It lets the owner of the Questions to Stories YouTube channel review channel, video, playlist, and selected video metadata through Codex; review performance, audience, reach, retention, and estimated revenue in a localhost dashboard; and upload an explicitly approved local MP4 as a Private video. It is not offered for public signup. The connector uses YouTube API Services and is intended only for the authorized adult account owner.
Google data accessed
The connector requests youtube.readonly, youtube.upload, and yt-analytics-monetary.readonly. Depending on the owner’s request, it may access channel identity and statistics, owned videos, playlists, video metadata, views, engaged views, watch time, retention, traffic sources, geography, device type, subscriber activity, engagement, thumbnail reach, and estimated monetization reports available to the authenticated account. Google describes the analytics scope as permission to view monetary and non-monetary reports. It does not authorize changing monetization, payouts, ads, or account settings. The local connector limits its channel write surface to one hash-verified MP4 upload that is forced to Private; it provides no tool for unlisted/public publishing, editing, commenting, or deletion.
How data is used
Data is requested only to provide the owner’s local dashboard or answer the owner’s instructions in Codex. The dashboard is served on localhost and receives a sanitized analytics snapshot; OAuth credentials never reach the page. When the connector is invoked through Codex, requested YouTube data is provided to Codex and OpenAI so the requested analysis or response can be produced, subject to the owner’s applicable OpenAI terms and settings. For an approved upload, the local connector streams the selected MP4 directly from the owner’s device to Google’s YouTube API; the upload manifest and result may appear in the owner’s Codex task history, but the public website does not receive the video, analytics, or credentials. Data is not used for advertising, profiling, or sale.
Google API Limited Use
Use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Storage and protection
Google OAuth refresh tokens are stored locally in the owner’s macOS Keychain. The public website does not receive or store OAuth tokens, and it uses no account login, advertising cookies, or website analytics. Dashboard snapshots are held in the local process memory and refreshed from Google; they are not uploaded to this website. Connector responses may remain in the owner’s Codex task history according to the owner’s OpenAI settings.
Sharing and transfer
YouTube data is shared only with the services needed to fulfill the owner’s request—Google’s YouTube APIs and, when the owner asks Codex to work with the data, Codex/OpenAI. The local dashboard itself remains on the owner’s device. An owner-selected video file is transferred to Google only when the owner explicitly approves a Private upload. CircleHooks does not sell the data, share it with data brokers, or disclose it to advertisers.
Retention and deletion
Local OAuth credentials remain until the owner disconnects the connector or revokes access. The owner can revoke access at any time through the Google Account connections page and can remove local Codex task history through the controls provided by OpenAI. The dashboard does not create a durable local analytics database. Google may generate recurring thumbnail-reach report files for the authorized account; those remain subject to the owner’s Google and YouTube controls. Uploaded videos remain in the owner’s YouTube account until the owner removes them through YouTube; the connector exposes no deletion tool. A deletion request may also be sent to the developer contact shown on the OAuth consent screen and will be handled within 30 days.
Your choices
The owner decides when the connector runs, which date range it reads, and whether a prepared Private upload may proceed. The analytics scope is read-only. Google access can be reviewed or revoked at Google Account Connections. Google’s handling of information is described in the Google Privacy Policy.
Questions
Privacy questions may be sent to the developer contact shown on the Google OAuth consent screen. The site will be updated if this policy materially changes.