Privacy policy

YouTube access and purpose

The utility uses YouTube API Services. With the owner’s Google authorization, it accesses channel identity; broadcast and video titles, descriptions, category and audience settings; visibility and livestream settings; broadcast identifiers, stream bindings and ingestion settings; and live status. It uses this information to identify the authorized channel and encoders, preserve broadcast settings, create and bind replacement broadcasts, and check that the feeds are live.

The requested permission is https://www.googleapis.com/auth/youtube.force-ssl. Google describes this permission broadly. The utility implements reads and broadcast creation and binding; it does not implement deletion of videos or modification of ratings, comments, or captions.

Google’s handling of information is described in the Google Privacy Policy.

Storage and sharing

OAuth access and refresh tokens, configuration, operational identifiers, transition records, and diagnostics are stored on the owner’s Mac. File permissions restrict access; this is not a claim that every stored file is encrypted. Broadcast settings and control requests are sent to Google’s YouTube API. OBS and the Pond relay send livestream media directly to YouTube.

The utility does not sell Google user data, use it for advertising profiles, or use it to train models. It does not share that data with these public information pages. Chris Stream Rotation’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Retention and local removal

Necessary authorization credentials are kept while the connection is in use. While the Mac and utility are running, regular maintenance refreshes current stream information and removes completed operation records after 29 days. An unresolved operation that becomes too old is blocked for owner review, with its cached API metadata removed and a local marker retained to prevent accidental replay.

If Google reports that the refresh authorization is no longer valid, the utility disables further API automation and clears its OAuth token and cached broadcast records. Temporary network or service failures do not trigger this removal. Separately managed OBS and Pond encoder configuration, including their stream keys, is preserved.

For deletion of locally stored Google data, contact contact@bastressanalytica.com. The owner handles deletion requests within seven days. Local deletion does not delete broadcasts or archives on YouTube. Maintenance resumes when the Mac and utility are running again; the owner can also arrange local removal directly.

Revoking authorization

The owner can revoke this utility’s Google access in Google Account connection settings. Revocation does not itself delete YouTube broadcasts or archives. OBS and the Pond relay use separate stream keys, so revoking OAuth access may not stop an active stream. To stop broadcasting, stop the encoders and disable their automatic restart or scheduling as appropriate.

Information website

These static pages offer no account sign-up and receive no Google OAuth credentials or camera feeds. The hosting provider, Cloudflare, may process ordinary website request information to deliver and secure the pages. See the Cloudflare Privacy Policy.

Contact

For privacy questions or local data removal, email contact@bastressanalytica.com.