Privacy Policy

1. What Rayxoo Media Keeper does

Rayxoo Media Keeper observes the media requests the browser already makes while you visit a page, lists the streams it detects and lets you save them into the download folder you choose. HLS (M3U8) playlists and direct MP4 / WebM files are fetched, merged and remuxed locally. When no direct link is available you can record a video that is playing on the page.

The Chrome Web Store edition contains no native executable, no Native Messaging host, no DRM / Widevine / CDM code, no device profiles and no content-key handling. It does not support YouTube or any other service that prohibits downloading, and it does not bypass paywalls, login restrictions, encryption, access controls or copyright protection. These limits are stated in the store listing, in the extension popup and settings screens, in the messages shown when a refused URL or a protected stream is encountered, and on our website.

2. Data handled on your device only

• Extension settings, UI language, download history metadata (file name, URL, status, progress), trial or quota counters, queued task state and licence state. Stored in chrome.storage.local and IndexedDB on this device.
• Media segments buffered in IndexedDB while a download is in progress, and the finished files written only to the download folder you choose.
• Downloaded media files. We never receive or retain a copy of any video or audio.

This information stays on your device unless you deliberately enable the optional account described in section 4.

3. Data used transiently to perform a download

• The media URL and request metadata such as Referer and Origin.
• When a media CDN requires the same login state as the player, the relevant session cookie is replayed on that one media request.

This is web browsing activity in the limited sense of media request URLs. It is processed locally, only for the user-facing feature “detect and save the media this page is playing”, which is described prominently in the Chrome Web Store listing and in the extension interface. Cookie values are never written to logs, never uploaded, never included in analytics and never shared with advertisers.

4. Optional account data

If you choose to sign in, the account service receives your email address, an authentication token, and a device identifier used to enforce the licence and trial quota. Sign-in uses Chrome’s identity.launchWebAuthFlow against Rayxoo’s own account service. There is no third-party social login. Account data is used only to validate a licence and, if you turn it on, to synchronise your own settings and task metadata.

Buying a licence is a separate, optional step on our website (plans & pricing). Checkout is processed through PayPal on our secure billing page. PayPal supplies us with the purchase email address and a transaction reference so we can issue and manage the licence key; subscription status and renewal dates are also stored with the licence. No payment card, bank account or PayPal credential is ever seen by the extension or stored by us.

We do not collect page text, form inputs, keystrokes, passwords, clipboard contents (except when you explicitly click “paste from clipboard” in the batch import box), advertising identifiers, location, or a cross-site browsing profile.

5. Data we do NOT handle

• Content keys, DRM licences, CDM device profiles or credentials from protected streams — this edition has no capability to obtain or use them.
• Any media from YouTube or Google video hosting services — access to these platforms is disabled in the extension.
• Financial or payment information. Purchases are processed outside the extension through PayPal on our secure billing page. We receive only the purchase email and a transaction reference needed to issue and manage a licence; card, bank and PayPal credentials are never handled by the extension or stored by us.
• Health information, personal communications or children’s data. Rayxoo Media Keeper is not directed at children under 13 and we do not knowingly collect their data.

6. How data is used and shared

Data is used solely to detect streams, run the download queue, enforce the trial or quota, and provide the optional account sync you enable. We do not sell personal data. We do not transfer it to advertising platforms, data brokers or other information resellers. We do not use or transfer it for personalised advertising, behavioural profiling, creditworthiness or lending decisions. We do not allow humans to read user data except where necessary for security or to comply with law.

The only third parties involved are:

1. The media hosts you deliberately download from. Those requests originate from your own browser and carry only the headers and cookies needed to reproduce the page session.
2. If you sign in, the Rayxoo account and licensing backend.
3. If you buy a licence, PayPal as the payment processor. It handles the payment on its own checkout pages under its own privacy policy; we receive only the purchase email and transaction reference described in section 4.

7. Retention and deletion

Local settings, download metadata and buffered segments stay on your device until you clear them in the extension or uninstall it. Finished downloads are yours and are never uploaded. Account data is kept while the account exists; you can request deletion at support@rayxoo.com. Uninstalling the extension removes all extension storage and IndexedDB data associated with it.

8. Permissions and security

The Chrome Web Store edition requests 13 Chrome permissions plus host access. Each is justified permission by permission in the Developer Dashboard. It does not request the debugger, nativeMessaging or declarativeNetRequestFeedback permissions. All processing happens inside the Chrome extension sandbox. FFmpeg is bundled locally as a WebAssembly module; no JavaScript or WASM is loaded from a network host at runtime, and the content security policy permits local scripts only. Data transmitted to the account backend uses modern HTTPS cryptography.

9. Limited Use affirmation

“The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.”

Rayxoo Media Keeper does not call Google APIs. The quoted sentence is retained as the standard affirmative Limited Use disclosure should any Google API ever be introduced in a future version; it will be reviewed before that release.

10. Changes and contact

We will update this policy and its effective date when our data practices change. Questions, deletion requests or privacy complaints can be sent to our support team using the address below.

Rayxoo Media Keeper is an independent technical tool. Only save media you own, have permission to save, or are otherwise legally entitled to store, and respect the terms of service and copyright of the sites you visit.