VidsDrop Companion

Detects permitted media streams and sends them to the local VidsDrop desktop app. YouTube and Google services are excluded.

VidsDrop Chrome Web Store Submission Notes Use this file when submitting the VidsDrop Companion extension to the Chrome Web Store. Store URLs Homepage URL: https://vidsdrop.tryproo.com/ Privacy policy URL: https://vidsdrop.tryproo.com/privacy.html Gumroad product URL: https://prooai.gumroad.com/l/VidsDrop Chrome Web Store URL: fill in after approval Listing Copy Extension name: VidsDrop Companion Short description: Local companion for VidsDrop: detect permitted media streams and send them to the desktop app. Detailed description: VidsDrop Companion is the optional browser extension for VidsDrop, a local desktop app for creator backup, permitted media archiving, and simple pre-edit workflows. The extension helps when a permitted media page loads a stream inside your real browser session. Open the page, press play, and VidsDrop Companion can detect visible HLS/DASH media streams and direct media files that the page loads. You can then send a selected item to the VidsDrop desktop app running on your own computer. VidsDrop handles the local queue and saving workflow from there. Core features: Detect HLS/DASH streams and direct media files loaded by supported pages. Group detected streams by browser tab so you can choose the right item. Send selected streams to the local VidsDrop desktop app at 127.0.0.1. Preserve request context such as Referer, Cookie, Origin, and User-Agent headers when those are required for a permitted media request. Copy or send open tab URLs to VidsDrop for batch workflows. Keep temporary diagnostic logs in the browser profile so connection or stream issues are easier to troubleshoot. Keep the processing local on your computer; the extension does not upload media URLs, cookies, browsing data, or downloaded files to a VidsDrop cloud service. VidsDrop Companion is designed for creators, editors, educators, researchers, and teams who need a local workflow for media they are allowed to save. Common uses include backing up owned media, preserving licensed or internal training videos, collecting source files before editing, and sending permitted browser-visible streams to the VidsDrop desktop queue. The extension is not a standalone cloud service. It works with the VidsDrop desktop app, which must be running on your computer. Pro-only batch features are licensed by the local desktop app; the extension checks the local app before unlocking those workflows. Privacy and scope: Selected stream URLs and related request headers are sent only to the local VidsDrop app on your own computer. The extension does not sell user data and does not use advertising or analytics tracking. YouTube and Google video services are intentionally excluded from this extension. VidsDrop Companion is not a tool for saving content without permission. Use VidsDrop only for content you own, have permission to save, or are otherwise allowed to archive. VidsDrop Companion is built to keep the browser-to-desktop workflow clear: detect permitted browser-visible media, let the user choose what to send, and hand it to the local VidsDrop app for local processing. Single Purpose Single purpose statement: VidsDrop Companion detects media streams in the user's browser and sends selected items to the local VidsDrop desktop app for permitted local archiving and creator backup workflows. Permission Justifications webRequest: Needed to detect HLS/DASH/media stream requests and read request/response headers required to identify playable media streams. cookies: Needed only when a user sends a selected stream to the local VidsDrop app. Some permitted streams require the same session cookies the browser used in order for the local app to access the media request. tabs: Needed to read the active tab title/URL, group detected streams by tab, open the local VidsDrop dashboard, and collect open tab URLs for batch workflows. scripting: Needed to inspect the current page for video/source metadata and page titles, and to detect media manifests that are exposed by page scripts. storage: Needed to temporarily store detected streams and diagnostic logs inside the user's browser profile. host_permissions: <all_urls>: Needed because users may use VidsDrop Companion on many different supported media sites. The extension excludes YouTube and Google video services in code and should only be used for content the user owns, has permission to download, or is allowed to archive. Privacy Practices Recommended dashboard answers: Does the extension collect or transmit personally identifiable information? No. Does the extension collect authentication information? It may access Cookie headers only to send a selected media request to the local VidsDrop app at 127.0.0.1; it does not transmit cookies to a cloud service. Does the extension collect web browsing activity? It temporarily processes page URLs, media URLs and tab titles to detect streams and send selected items to the local app. Does the extension sell or share user data? No. Does the extension use data for advertising or analytics? No. Does the extension transfer data to third parties? No, except that purchases are handled by Gumroad outside the extension. Data destination: Selected media URLs and related headers are sent only to the local VidsDrop desktop app running on the user's computer at 127.0.0.1:7777 or the development fallback 127.0.0.1:8000. Gumroad / Landing Strategy Gumroad should mention the extension, but it should not make the extension look like a separate paid product. Recommended Gumroad wording: Includes the VidsDrop Companion browser extension for supported streaming pages. The extension sends detected, permitted media streams to the local VidsDrop desktop app. YouTube and Google video services are excluded from the extension. Landing page structure: Primary CTA: Download VidsDrop for macOS and Windows -> Gumroad. Secondary CTA after Chrome Web Store approval: Install VidsDrop Companion -> Chrome Web Store. Do not present Gumroad and Chrome Web Store as equal alternatives. Users need the desktop app first; the extension is optional. Before approval: Do not link to an unpacked extension as the main public install path. Mention "browser extension included" in Gumroad only if the downloaded package includes clear install instructions. After approval: Add the Chrome Web Store URL to Gumroad. Add a secondary "Install Chrome extension" link on the landing page. Add the Chrome Web Store URL to this file. Assets Needed Store listing icon, 128x128 PNG with transparent padding: release/chrome-web-store-icon-128.png Store listing icon source: release/chrome-web-store-icon-128.svg In-package 128x128 icon: extension/icons/icon128.png 48x48 icon: extension/icons/icon48.png Screenshots: capture the popup and a VidsDrop queue flow. Promo tile: create after final Chrome Web Store listing copy is approved. Review Risk Notes Highest-risk areas: Broad <all_urls> host permission. cookies permission. Stream detection/download wording. Mitigation: Keep the single purpose narrow. Explain that data is sent to the local app only. Keep privacy policy public and specific. Avoid "download anything", "YouTube downloader", "TikTok downloader", "Instagram downloader" language in the store listing. Include a short screen recording for the reviewer if the dashboard asks for one.