Your data

Privacy policy

Effective October 4, 2026

This policy covers the Media Downloader Chrome extension and its website, operated by R3flex. Contact r3flexmlg@gmail.com with privacy, deletion, or support requests.

Media processing happens on your device. We do not send your browsing history, page contents, previews, or downloaded media to our licensing server. Premium billing uses separate purchase and license records.

1. Information the extension accesses

On websites where you allow access, the extension reads page and media URLs, page titles, post identifiers, creator handles, image dimensions, player details, and loaded media metadata to find the photos and videos you choose. It observes media request URLs and response content types to detect streams, including media in embedded frames.

Previews may use thumbnails or frames from the selected player. Optional creator-handle stamps use the detected creator handle. User-started post-photo batches and profile collection retain eligible media exposed by the page; profile collection can scroll the page. These features do not upload media to us.

Page media history, preview frames, detection metadata, and bounded stream buffers are kept in memory while their page or extension context is active. Stream assembly and format conversion run locally. Completed output may remain in the extension's temporary offscreen document until Chrome finishes the download.

2. Local storage and download records

Chrome extension local storage holds your preferences, disabled-site list, daily free-video count, migration settings, and, if connected, your license credential and cached entitlement. Temporary filename mappings use Chrome session storage. The extension reads Chrome download records to show and monitor its own recent downloads; it does not send those records to us.

The free allowance is five video downloads per browser profile per UTC day, plus unlimited photos. Usage counting stays on your device. Your downloaded files remain on disk and Chrome may retain its download history after you uninstall the extension. You can remove files and download history separately.

3. Requests to websites and visibility on a page

Media is requested directly from its source website or content delivery network. Some requests use the website session already available to your browser, depending on the source's credential requirements. Those websites receive ordinary network information, including your IP address. The extension does not read or copy browser cookies using a cookies permission.

The floating page panel is part of the host page's document. The host page can inspect its displayed media information and controls. Purchase credentials and billing operations stay in the extension's own context and the billing website, rather than this page panel.

4. Premium purchases and activation

Our backend stores purchase email, plan, amount and currency, Stripe order/payment/customer/subscription references, payment status, paid-through dates, cancellation status, and hashed recovery, login, and browser credentials in Cloudflare D1. We also retain processed payment-event identifiers and refund or dispute records to fulfill purchases reliably and prevent duplicate processing.

Stripe provides checkout and receives the information you enter there. Our server does not receive your full card number or security code. Stripe shares payment results and the purchase details needed to supply and manage Premium. See Stripe's privacy policy.

The website uses a secure, HTTP-only cookie to recognize a purchase session for up to 30 days. Browser activation credentials last up to one year and can be renewed through restoration. License checks send a random credential to our server; they do not include your visited sites or media. Paid status is normally refreshed after five minutes and can remain usable offline for up to six hours, within a subscription's paid period.

The website uses browser session storage for the extension connection identifier. If you open a private activation-test offer, its token is saved in website local storage so the offer remains available in other tabs in the same browser. The website removes that token when it recognizes a paid purchase or learns that the offer has expired; you can also clear it by clearing this website's data. Purchase restoration currently uses your purchase email and recovery key. Email-code restoration is disabled; if introduced, this policy will identify the email provider before that feature is enabled.

5. Hosting, security, and support

Cloudflare hosts the website, API, and purchase database and processes technical connection data such as IP addresses and request metadata to deliver and protect the service. The backend uses IP-based rate limits and purchase or email identifiers to limit abusive requests. See Cloudflare's privacy policy.

If you email support, your message and any information you choose to include are handled through our Gmail mailbox, provided by Google. Do not send card numbers, passwords, recovery keys, or private media unless needed for a support request and you choose to share it. See Google's privacy policy.

We use HTTPS, server-side payment verification, hashed credentials in the database, and encrypted server secrets. We do not include advertising or analytics scripts. We do not sell user data or use browsing-related data for advertising, profiling, or unrelated purposes. Service providers may process information internationally under their own applicable safeguards and policies.

6. Retention and your choices

Local preferences and credentials remain until cleared or the extension is removed. Disconnecting Premium removes the active license and pending connection credentials from that extension; it does not erase your purchase or cancel a subscription. Expired server login, browser, and verification credentials are scheduled for daily cleanup. Purchase, payment, and support records are retained as needed to deliver lifetime access, resolve disputes, prevent fraud, and meet applicable recordkeeping obligations. You can request access, correction, or deletion by email; records needed for those obligations may have to be retained.

The extension's per-site Disable control stops listing and downloading and stops background network collection for that site. It does not uninstall the page's already injected media hooks or immediately clear every bounded page-memory buffer. For a full site opt-out, revoke the extension's site access in Chrome and reload the page, or uninstall the extension. Closing the page releases its page-memory data.

You may use Chrome's extension settings to manage site access, disable the extension, or uninstall it. To cancel monthly billing, use the purchase page or contact support; uninstalling alone does not cancel billing. Depending on your location, you may also have rights to restrict or object to processing, receive a copy of your information, or complain to your local data protection authority.

7. Chrome Web Store Limited Use

Media Downloader's use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Browsing-related information is used only to provide the prominently described media discovery, preview, download, and local-history features. It is not transferred for advertising, sold to data brokers, or used to determine creditworthiness.

8. Changes and contact

We will update this page and its effective date when data practices change. Material changes will be disclosed through the website or extension as appropriate. Questions and privacy requests: r3flexmlg@gmail.com.