Publisher privacy policy

Information the publisher uses

• Google OAuth access and refresh tokens, the permissions granted, and token expiry information.
• The authorized YouTube channel's identifier, handle and name, used to verify the intended destination.
• Selected local MP4 videos, their titles, descriptions, language, audience and visibility settings, and synthetic-media disclosures.
• Uploaded video IDs, processing and publication status, selected video metadata and aggregate view, like and comment counts.
• Local source notes, media hashes, review records, publication receipts and performance snapshots.

The read-only permission may permit access to more account information than these operations use. The publisher does not request a Google password, read private messages, collect individual viewers' profiles or read comment bodies for performance tracking.

Purpose and sharing

Authorization data is used to verify the channel, upload approved content, check results and retrieve aggregate performance counts. The channel operator uses those counts to compare English and Spanish videos and male and female presenters. They are not a measurement of individual viewers.

Google receives authorization requests, video files and publication metadata. Public videos and their descriptions become visible to YouTube viewers. Google handles that information under the Google Privacy Policy and YouTube's terms.

The local workflow runs with Codex. Its operator may give Codex editorial instructions, public news sources and sanitized operational reports needed to manage the authorized channel. Reports can include public channel or video IDs, titles, publication status and aggregate counts. Credentials are kept out of prompts, source control and public artifacts. Codex's processing is subject to the operator's service agreement and data controls; this policy does not promise a particular third-party training setting.

Our permitted use and sharing of Google API data is limited to these authorized publisher features and necessary security or legal handling, in accordance with the Google API Services User Data Policy, including its Limited Use requirements where applicable. We do not sell that data, use it for ad targeting or credit decisions, or supply it for training general-purpose AI models. A new purpose or additional permission requires renewed operator agreement.

Local storage and retention

Google tokens are stored on the Windows operator's computer using Windows Data Protection API encryption for that Windows user. Videos, reviews, publication records and aggregate performance snapshots are stored locally. The operator controls access to those files and any copies.

Tokens are retained only while needed for the active authorized connection. Other cached Google API metadata must be refreshed or deleted within 30 days. Historical authorized statistics may be kept for the active comparison work only while authorization and the continued existence of the relevant videos are rechecked at least every 30 days. Historical counts retain their original observation times; a later refresh is not substituted for an earlier checkpoint.

The operator must remove data when it is no longer needed, authorization can no longer be maintained or a deletion request is received. This installation relies on operator-assisted retention and deletion, not an automatic purge service. Local API data may also appear in exported reports and receipts; cleanup must include those copies. Data is not stored in a public account database on this website.

Original local scripts, rights records and rendered videos are production assets, not videos downloaded from YouTube. Their retention is managed separately. Removing a Google connection does not authorize publishing from another account.

Publication receipts prevent duplicate uploads. Deleting a local receipt or source file does not delete a video already published on YouTube. That video must be managed separately in YouTube Studio.

Stop access or request deletion

You can revoke Rounds News Desktop Publisher's access through your Google account's third-party connections. Revocation prevents future authorized API operations. It does not automatically remove existing local copies or published videos.

For deletion of the publisher's stored credentials and account or performance data, follow the data deletion instructions or contact @rounds.news on Instagram. Our policy is to complete those requests as soon as possible and within seven calendar days. The operator will verify the request without secret credentials, stop the affected local job, remove the relevant stored data and copies, and confirm what was done. Authorized operators can also remove those files from their own installation.

These public pages

The publisher information pages have no Google sign-in or upload form and add no advertising or analytics script. The website privacy policy describes browser preferences, hosting, approximate weather location and external images on the news website. Following a link to Google, YouTube or Instagram brings you to that service's own data practices.

If the publisher's permissions or data use change, this policy will be updated before those changes are enabled.