Forexahedron Broadcast Coordinator

Privacy Policy

This policy explains how the owner-operated application accesses, uses, stores, shares, retains, and deletes Google user data.

Data accessed

With the owner's explicit OAuth consent, the application may access YouTube channel information and live-broadcast data, including channel identity, broadcast and stream identifiers, titles, descriptions, schedules, privacy status, ingestion and lifecycle status, health information, and archive status.

How data is used

Google user data is used only to provide the application's visible broadcast-coordination functions: listing and inspecting the owner's YouTube state; creating, binding, monitoring, transitioning, ending, and reconciling an exact owner-approved unlisted live broadcast; and producing local operational evidence. The application does not use Google user data for advertising, profiling, eligibility decisions, or model training.

Storage and security

OAuth client configuration and refresh credentials are stored locally on the owner's computer in owner-only files. Short-lived access tokens are used only for authenticated Google API requests and are not intentionally written to public logs or repositories. Local operational receipts may retain YouTube resource identifiers, states, and timestamps for audit and recovery. Reasonable access controls are used, but no system can guarantee absolute security.

Sharing and transfer

Google user data is not sold, rented, or shared with advertisers or data brokers. It is not transferred to third parties except through requests to Google and YouTube that are necessary to provide the functions described in this policy, or when disclosure is required by law.

Retention, deletion, and revocation

OAuth credentials remain on the owner's computer until replaced, deleted, or revoked. Operational receipts are retained locally for security, audit, and recovery until the owner deletes them. The owner may revoke the application's Google access at any time from the Google Account connections page and may request deletion of locally retained Google user data by using the contact below.

Limited Use

The application's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Changes

This policy will be updated before Google user data is used for a materially different purpose. The revision date below identifies the current version.

Contact

Questions or deletion requests may be sent to pietras@gmail.com.