Effective August 31, 2026

Privacy Policy

How Retro Weather Live Automation handles Google account authorization and YouTube operational data.

1. Who operates this application

Retro Weather Live Automation is operated by EBL Systems as a private administrative tool for authorized weather-broadcast operators. Questions about this policy may be sent to jeffgbright65@gmail.com.

2. Information the application accesses

After an operator grants Google OAuth authorization, the application may access the minimum YouTube channel and live-broadcast information needed for its functions. This can include channel identifiers, broadcast identifiers, titles, descriptions, scheduled times, lifecycle status, stream identifiers, and API responses.

The application receives OAuth access and refresh tokens from Google. It does not receive or store the operator's Google password.

3. How information is used

Authorized information is used only to schedule and update live broadcasts, connect configured streams, perform broadcast transitions, monitor operational status, and diagnose automation errors for the consenting channel owner.

The application is not designed to build viewer profiles, collect contacts, process payments, or use YouTube information for advertising.

4. Storage and security

OAuth credentials are stored locally in a protected Windows secrets directory on systems controlled by the application operator. Operational logs may contain broadcast identifiers, timestamps, status results, and error information. Secrets are not intentionally written to public website files or shared logs.

Reasonable administrative, access-control, and system-security measures are used to protect locally stored information. No method of electronic storage can be guaranteed to be completely secure.

5. Sharing and sale

Google user data is not sold, rented, used for advertising, or shared with unrelated third parties. Information is transmitted to Google and YouTube as necessary to perform the operator-authorized API requests. It may also be disclosed when required by law or to protect the security and integrity of the service.

6. Retention and deletion

Authorization tokens are retained only while the operator keeps the application connected. Operational metadata and logs are retained only as long as reasonably necessary for broadcast operation, troubleshooting, security, or legal obligations.

After authorization is revoked or a valid deletion request is received, stored Google authorization data will be removed from active systems within seven days, except where limited retention is legally required.

7. Operator choices

Authorization can be reviewed or revoked at any time from Google Account permissions. Operators may also contact EBL Systems to request access to or deletion of information associated with their authorization.

8. Google API disclosure

Our use of information obtained through Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Use of YouTube services is also subject to the YouTube Terms of Service and Google Privacy Policy.

9. Changes to this policy

This policy may be updated when the application or applicable requirements change. The effective date at the top of this page will identify the latest version.