Privacy policy

Data the application accesses

With an authorized operator’s consent, yt_stream accesses YouTube stream, broadcast, and playlist identifiers; titles; broadcast configuration; lifecycle and stream status; and playlist membership. Encoder video is transmitted to YouTube for livestreaming and any recording handled by YouTube.

Google authorization credentials, including access and refresh tokens, allow the application to act on the selected channel. The application requests the https://www.googleapis.com/auth/youtube scope. This permission is broader than an upload-only permission and allows the API operations described on the homepage.

How data is used

The application uses this data to locate configured streams and playlists, create and bind broadcasts, monitor readiness, start and finish livestreams, remove conflicting unstarted broadcasts, and organize broadcasts in playlists.

The inspected automation has no functionality for selling Google user data, advertising profiling, or training generalized artificial intelligence or machine-learning models. Google user data is used for the operational purposes described here.

Storage and access

Authorization credentials are stored in configuration files on the machines running the automation. Operational output can include identifiers, titles, timestamps, status information, and API error messages. Authorized operators with access to those machines and their logs may access this information.

Video and channel resources transmitted to YouTube are processed and stored by Google under its policies and the channel’s settings. This website does not store the automation’s credentials, recordings, or channel metadata. Its hosting provider may process ordinary request information, such as IP addresses and browser details, to serve and secure the website.

Sharing and Google’s Limited Use requirements

Data is exchanged with Google and YouTube to provide the requested livestream functionality. Access to local credentials and operational data is limited to authorized operational purposes. yt_stream’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Retention and deletion

Local authorization files remain until an operator removes or replaces them. Local operational records follow the running machines’ log retention settings; this policy does not specify a fixed retention period. YouTube content remains subject to the channel’s retention and deletion settings.

To stop access, revoke the application through Google Account connections. To remove local credentials or logs, ask your authorized Poultry Patrol system administrator through your existing internal communication channel. Revoking access does not automatically erase files on the running machines or remove existing videos from YouTube. Manage those resources separately in YouTube Studio and the local system.

Questions and updates

This application is for authorized internal operators. Direct privacy questions and data-removal requests to your Poultry Patrol system administrator through your existing internal communication channel.

Material changes to these practices will be reflected on this page and communicated to authorized operators before new uses of Google user data are introduced.