Privacy
Privacy Policy
Last updated September 30, 2026
This policy describes the YouTube Player for Twitch Chrome extension, this information site, and the separate workflow used by the maintainer to submit extension releases.
Information stored by the extension
The extension does not require an account. It stores its settings and playback state in Chrome’s extension-local storage on your device. This includes Auto-sync and quality preferences, remembered YouTube video IDs for Twitch channels, and the current active video ID for a channel.
Recent-stream history can include a YouTube video ID, its title and channel name, the time it was added, and whether you pinned it. The history list can be cleared from the extension. The extension’s local storage is cleared when the extension is removed. When you enable Force Highest Quality, the extension also reads and updates Twitch’s local video-quality preference in your browser.
Requests to YouTube and Twitch
When you search for a stream, the extension reads the current Twitch channel name and, when available, the YouTube channel link shown on that Twitch page. It requests YouTube search results, public channel-stream information, or video-page details as needed. The search term, linked channel URL, and selected video ID may be included in those requests. Playback loads the selected video using YouTube’s embedded player.
These requests go from your browser to YouTube; the extension does not proxy them through a developer-operated server. YouTube may receive ordinary request information and process it under Google’s Privacy Policy and YouTube’s privacy information. Twitch also processes your use of Twitch under its Privacy Notice.
Sharing by the extension
The extension does not send its locally stored settings, playback state, or stream history to the developer. The current extension source contains no developer analytics, advertising, or telemetry service.
Maintainer-only publishing workflow
Separately from extension use, the maintainer uses GitHub Actions to prepare extension releases. When publishing is enabled, the workflow can use the maintainer’s Google OAuth client credentials and refresh token stored as GitHub repository secrets. On a push to the main branch while publishing is enabled, the workflow exchanges those credentials with Google for an access token and uses the Chrome Web Store API to check the target item’s status and submit the extension package and version for review.
The workflow is configured to target this extension’s Chrome Web Store item. The Google OAuth permission itself is publisher-wide and can operate on other Chrome Web Store items that the authorized account manages. These publishing credentials and release requests are maintainer data; they are not collected from extension users or included in the extension package. Google and GitHub process this information under their own privacy policy and privacy statement.
This information site
This static site does not provide accounts or forms and does not include analytics, advertising pixels, or other developer tracking code. It is hosted by Cloudflare. When visitors access the site, Cloudflare may process information such as IP addresses, traffic-routing data, system configuration information, and other information about traffic to and from the site. See Cloudflare’s Privacy Policy.
Your choices
You can clear the extension’s recent-stream history from its menu. Removing the extension clears its extension-local storage. You can also choose whether to use YouTube or Twitch features and review the privacy controls offered by those services.
Contact
For questions about this policy or the extension, contact ypftsupport@vrnrn.com.