# Privacy Policy **Effective date:** Audust 13, 2026 Livestream Scheduler (“the Application”) is maintained by Christopher Rutledge. This policy explains how the Application accesses, uses, stores, and deletes information when you connect a YouTube channel. ## YouTube API Services The Application uses YouTube API Services. By connecting a YouTube channel, you authorize the Application to perform the scheduling and livestream-management actions you configure. Use of YouTube is also governed by: - [YouTube Terms of Service](https://www.youtube.com/t/terms) - [Google Privacy Policy](https://policies.google.com/privacy) - [YouTube API Services Terms of Service](https://developers.google.com/youtube/terms/api-services-terms-of-service) ## Information We Access After you authorize access through Google OAuth, the Application may access: - Your YouTube channel identifier and channel name. - Scheduled and active livestream broadcasts. - Reusable livestream configurations and ingestion information. - Broadcast titles, descriptions, visibility, audience designation, and scheduled times. - Broadcast and stream lifecycle or health status. - Information necessary to create, update, bind, start, stop, and complete livestream broadcasts. The Application never requests, receives, or stores your Google or YouTube password. ## How Information Is Used YouTube information is used only to: - Confirm that the intended YouTube channel is connected. - Create and manage broadcasts requested by your schedule. - Generate broadcast titles and scheduled times. - Bind broadcasts to the configured livestream. - Monitor livestream readiness and status. - Start and complete broadcasts as configured. - Diagnose errors and prevent duplicate broadcasts. The Application does not use YouTube information for advertising, profiling, analytics, or unrelated purposes. ## Information Stored on Your Device Livestream Scheduler is a desktop application. Its schedules, settings, execution history, broadcast identifiers, and OAuth authorization tokens are stored locally on the Windows computer running the Application. OAuth credentials and tokens are encrypted using Windows Data Protection for the current Windows user. They are not intentionally written to application logs or transmitted to the developer’s servers. OBS sends audio and video directly to YouTube. The Application does not upload or retain copies of livestream audiovisual content on servers operated by the developer. ## Sharing and Sale of Information We do not sell, rent, or trade personal information or YouTube API data. We do not share authorized YouTube information with advertisers, data brokers, or unrelated third parties. Information is communicated to Google and YouTube only as necessary to perform authorized API operations. The public website is hosted through Cloudflare and may be subject to Cloudflare’s standard network and security logging practices. ## Data Retention Authorization tokens are retained locally while the YouTube connection remains active and are used only for the permissions granted by the user. Broadcast identifiers and related status information may be retained locally to prevent duplicate broadcasts and support recovery. Stored YouTube API data is refreshed or deleted when it is no longer required and in accordance with YouTube API Services policies. Diagnostic logs are limited and must not intentionally contain OAuth tokens, livestream keys, or Google account passwords. ## Revoking Access You may revoke the Application’s Google authorization at any time through: [Google Account third-party access settings](https://security.google.com/settings/security/permissions) The Application will also provide a disconnect or delete-data function. Disconnecting removes locally stored OAuth authorization and associated cached YouTube account information. Removing local data does not delete broadcasts or other content stored by YouTube. After authorization is revoked or deletion is requested, locally stored authorized data will be deleted as soon as reasonably possible and no later than seven calendar days, except where retention is legally required. ## Data Deletion Requests To request deletion of information associated with your use of Livestream Scheduler, contact: [[email protected]](mailto:[email protected]) Include enough information to identify the installation or authorization involved. Do not send passwords, OAuth tokens, or livestream keys by email. ## Security Reasonable technical measures are used to protect locally stored authorization data, including Windows user-scoped encryption and transport encryption for Google and YouTube API requests. No security method can guarantee absolute protection. Users are responsible for securing the Windows account and computer on which the Application runs. ## Children’s Privacy Livestream Scheduler is not directed to children. Connecting a channel does not automatically designate its content as made for children. Users are responsible for selecting the correct YouTube audience designation for their broadcasts. ## Changes to This Policy This policy may be updated when the Application’s features, data practices, or applicable platform requirements change. The effective date above will be updated when revisions are published. ## Contact Questions or complaints about this policy may be sent to: [[email protected]](mailto:[email protected])