pip-anywhere

Privacy Policy — PiP Anywhere

Last updated: 26 July 2026

Short version

PiP Anywhere collects nothing, transmits nothing, and contains no network code.

What the extension stores

Four settings, kept in chrome.storage.sync so they follow your Chrome profile:

Key	Value
hotkey	your shortcut for standard Picture-in-Picture
docHotkey	your shortcut for whole-player Picture-in-Picture
autoPiP	whether videos may pop out automatically
showToast	whether to show the brief on-screen confirmation

That is the complete list. Chrome syncs these through your own Google account; they never reach the developer or any third party. Removing the extension removes them.

What the extension does not do

• No analytics, telemetry, crash reporting or usage counters.
• No servers. The extension makes no HTTP, WebSocket or fetch requests of any kind — the source contains no networking calls at all.
• No reading, storing or transmitting of page content, browsing history, URLs, form data, credentials, cookies or media.
• No advertising, no tracking identifiers, no fingerprinting.
• No remote code. Every line that runs ships inside the package; nothing is fetched or evaluated at runtime.
• Nothing is sold or shared, because nothing is collected.

Why it asks for access to all sites

Picture-in-Picture must be requested by a script running in the same frame as the <video>, and video can be on any site — very often inside a cross-origin iframe belonging to an embedded player. The extension therefore runs a small content script in every frame.

That script only ever looks for <video> elements and calls the browser’s own Picture-in-Picture API on the one you are watching. It does not read page text, and it sends nothing anywhere.

Verifying this

The extension is open source. Search the package for fetch, XMLHttpRequest, WebSocket, or sendBeacon and you will find no matches.

Contact

Questions or concerns: ayub.kosimov@gmail.com

This site is open source. Improve this page.