Stream Katcher processes the information needed to detect, inspect, save, play, sync, and export media. This Privacy Policy explains what stays on your device, what is sent to a service, and when you choose that transfer.
The short version.
- Media detection is performed for the current tab and captured results are kept locally by default.
- Account access, Library sync, Google Drive, Cloud export, and paid plans are optional features that send the information needed for the feature you select.
- We do not sell personal information, use captured media for advertising, or build an unrelated browsing profile.
- Stream Katcher does not store full payment-card numbers. Payment details are handled by the payment provider.
- You control capture, saved data, sync, connected destinations, and account sign-in through the extension and website.
What this policy covers.
This policy applies to the Stream Katcher browser extension, the Stream Katcher website, your Stream Katcher account, optional Library sync, Google Drive connection features, Cloud export, and Pro or Lifetime entitlement processing.
Stream Katcher is designed to work with media that your browser can access. It does not bypass DRM, decrypt protected media, or ask you to provide a password for a third-party website.
When the extension observes a request, the original website or CDN may still receive the browser request needed to load or play that resource. Stream Katcher does not claim ownership of the media you inspect; you are responsible for using content lawfully and respecting the source website's terms.
What we process and why.
Media and page context
Request URLs, page URLs, page titles, request and response headers, resource and content types, redirects, manifests, track metadata, source candidates, and preview frames. These are needed to detect and explain media loaded by the current tab.
Local extension data
Captured session data, saved asset metadata, thumbnails, storyboards, preferences, blocked-site settings, and download job state. This data is kept in Chrome storage on your device unless you explicitly use a cloud feature.
Account and authentication data
Your email address, account identifier, authentication session, and session timestamps when you sign in. Passwords are handled by the authentication provider and are not stored by Stream Katcher as readable passwords.
Synced Library data
When you enable sync, saved asset metadata and the asset payload may include source page URLs, source domains, titles, media properties, playback metadata, and user-created previews. Preview images may be stored in private object storage and returned through time-limited signed URLs.
Google Drive connection data
When you connect Google Drive, we may store the Google account identifier and the email address or display name returned by Google so we can associate the connection with your Stream Katcher account. Files are sent to Google Drive only when you explicitly choose a Google Drive action.
Cloud export data
When you choose Cloud export, the completed file, file name, MIME type, size, upload status, and storage key are sent to the configured Cloud upload service. The local upload token is stored in Chrome storage and is used only to authorize that export service.
Billing and entitlement data
When you purchase Pro or Lifetime, Whop processes payment and billing details. Stream Katcher receives limited metadata such as your account identifier, Whop customer ID, order or subscription ID, selected plan, status, and relevant timestamps so we can grant, maintain, or revoke access.
Support data
Information you choose to include in a feedback or support request, such as your email address, message, screenshots, diagnostic details, and the extension version.
Information we do not request
- We do not ask for your third-party website passwords.
- We do not store full payment-card numbers or payment authentication codes in Stream Katcher systems.
- We do not intentionally collect browsing history unrelated to a tab where you use the extension.
- We do not sell captured URLs, media metadata, account information, or synced Library data.
Why information is processed.
Many capture, parsing, preview, and browser-download operations happen on your device. We do not use captured media or browsing data for advertising, sale to data brokers, or unrelated behavioral profiling.
- detect and classify accessible video and audio streams in the current tab;
- show stream metadata, playback candidates, previews, and download status;
- save selected assets, preferences, and job state locally;
- provide account authentication, Library sync, connected destinations, and support;
- check plan capabilities and limits so Pro and Lifetime features are available to eligible accounts;
- process refunds, cancellations, subscription status changes, and entitlement revocations; and
- protect the reliability, abuse resistance, and security of the extension and website.
What the extension permissions do.
Stream Katcher requests broad host access because media can be delivered from a page's own origin, a CDN, a manifest host, or a separate segment host. The access is used for the extension's single purpose: detecting and inspecting media resources in tabs where you use Stream Katcher.
Side Panel
Displays detected media, stream metadata, previews, saved assets, and download actions beside the active tab.
Storage
Keeps session data, saved asset metadata, preferences, blocked-site settings, authentication state, and download job state available across views and browser sessions.
Web Request
Observes request URLs, request and response headers, resource types, content types, redirects, and status changes to identify accessible media streams. Header values that look like credentials are redacted from user-facing debug exports.
Downloads
Starts and tracks a file download only after you choose to save an accessible media asset or exported result.
Tabs
Associates captured requests with the active tab and reads its URL and title so results stay scoped to the current page.
Declarative Net Request
Applies temporary, session-scoped request-header rules during playback when an accessible media source needs its original request context.
Offscreen
Processes media frames, Blob data, previews, and media exports without opening a visible tab.
Unlimited Storage
Allows the local library and preview metadata to exceed the default extension storage quota when needed.
Host access
Observes media requests and related page context on websites where Stream Katcher is used so it can detect resources across origins.
How long information stays.
When you ask us to delete account-backed data, we will verify the request and remove or anonymize information that we are not required to retain. Some operational logs or transaction records may need to remain for a limited legal or security purpose.
- Session capture data is kept in Chrome session storage for the active workflow and can be cleared by ending or clearing that session.
- Saved local assets, preferences, and download job history remain on your device until you remove them, clear extension data, or uninstall the extension.
- Synced Library records and preview files remain in the account-backed service until you delete them, request deletion, or the account or service retention process removes them.
- Cloud-exported files remain in the configured Cloud storage until the service's retention or deletion process removes them. Remove a Cloud export through the available destination controls or contact support if you need help.
- Account and entitlement records may be retained for authentication, support, security, fraud prevention, transaction records, and legal obligations.
- Payment providers and Google may retain data under their own policies and legal obligations when you use their services.
You stay in control.
Depending on where you live, you may have rights to request access, correction, deletion, restriction, portability, or objection regarding personal information. We may need to verify your identity before completing a request. Deleting local data does not automatically delete data already sent to a cloud, payment, or destination provider; use that provider's controls or contact us for help.
- use local capture, playback, Library, and browser downloads without signing in;
- block capture for individual sites from the extension settings;
- remove saved assets, previews, download jobs, and local settings from the extension;
- enable or stop Library sync when you choose; local data can remain local;
- connect or disconnect Google Drive from its settings;
- cancel a Pro subscription through the payment provider's customer controls or by contacting support;
- delete your account and account-backed cloud data from your account profile, or request help through the Feedback page; and
- uninstall the extension to stop its access to browser tabs and requests.
How we protect information.
We use HTTPS, authenticated access, signed provider notifications, access controls, private storage, and time-limited signed preview URLs where appropriate. Authentication sessions are stored using the platform's secure session mechanisms. No internet service can promise absolute security, so avoid placing passwords, payment credentials, or unrelated sensitive information in media URLs, feedback, or debug exports.
We may update this policy when the product, providers, or data practices change. The date at the top of this page identifies the latest version. If a change materially affects how we use personal data, we will provide a more prominent notice where appropriate.
Questions or deletion requests.
The service operator and data controller is Nguyễn Hồng Đức. The address for legal notices is 30A Hang Tre, Long Binh, Ho Chi Minh, Viet Nam. For privacy questions, account-data deletion, billing metadata questions, or support, use the Feedback page on the Stream Katcher website or email hongducmmo@gmail.com. Please do not include passwords, full payment-card numbers, authentication codes, or private media files unless we specifically request a safe diagnostic sample.
Questions about this document?
Use the Feedback page for account, billing, privacy, or software-support requests.