Facebook Videos Downloader Privacy Policy

This Privacy Policy applies only to the Video Downloader Chrome extension, also described as Facebook Videos Downloader (the “Extension”). The Chrome Web Store extension ID is depedcledfjjdoikcjfbdjlncjfbpjjg.

This page explains how the Extension collects, reads, handles, stores, uses, and shares user data when you use it to find, download, and organize Facebook videos, images, photo albums, and supported Facebook embedded videos.

This privacy policy is provided by Plugins Hub. For questions, contact contact@pluginshub.site.

Facebook Videos Downloader is an independent Chrome extension. It is not affiliated with, endorsed by, sponsored by, or operated by Facebook, Meta Platforms, Inc., or any Meta product.

1. What the Extension Does

Facebook Videos Downloader runs in your browser and helps you save Facebook media that you choose to access. Depending on the page and feature you use, the Extension can:

Detect Facebook videos on Facebook.com pages and in supported Facebook embedded frames
Download individual Facebook videos
Download videos or images in bulk from supported Facebook profiles, pages, groups, search results, albums, feeds, Watch pages, and video sections
Download supported Facebook photo albums and image resources
Resolve available video qualities, direct media URLs, thumbnails, and stream URLs
Merge separate video and audio streams locally in the browser when Facebook provides split streams
Save files to your device through the Chrome downloads feature
Organize saved files into folders based on the source page, profile, group, album, or media type
Check Free and Pro plan limits and subscription status

You do not provide your Facebook password to Plugins Hub or to the Extension. If Facebook content is visible only to your Facebook account, group membership, page permissions, or browser session, you must be signed in to Facebook in your browser for the Extension to access that content.

2. User Data Read or Processed by the Extension

The Extension processes different types of data for different features. The sections below describe each category, why it is used, where it is stored, and whether it is shared.

2.1 Facebook Page and Media Data

When the Extension is active on Facebook.com or in a supported Facebook embedded video frame, it may read or process:

Facebook page URLs, video page URLs, embedded video URLs, album URLs, group URLs, profile URLs, and search result URLs
Facebook video IDs, image IDs, album IDs, group IDs, profile or page identifiers, and source usernames or page names when available on the page
Video titles, thumbnails, duration, available quality information, DASH manifests, direct video URLs, audio stream URLs, video stream URLs, cover images, and media file URLs
Image URLs, thumbnail URLs, album titles, photo set IDs, and related media resource URLs
Captions, descriptions, timestamps, or visible metadata when needed to identify or name the downloaded media
Folder names, sanitized filenames, download queue state, progress state, pause/resume/stop state, and download results
The page structure needed to add visible download buttons and to identify supported media

Purpose: this data is used to detect downloadable Facebook media, show download controls, resolve media resources, create filenames and folders, run bulk downloads selected by you, and save files to your device.

Storage and handling: most of this data is handled in browser memory while the Extension is running. Some data may be stored in local browser storage as cached results, task state, download state, settings, or local history so the Extension can continue or display progress.

Sharing: Plugins Hub servers do not receive your downloaded Facebook videos, images, albums, media files, media lists, captions, folder names, or detected media results. Some Facebook media URLs or stream URLs are requested directly from Facebook, Meta, or Facebook CDN domains from your browser so the media can be downloaded.

2.2 Facebook GraphQL Request Data

To support bulk downloads from Facebook pages, groups, albums, search results, and video sections, the Extension uses Chrome’s webRequest permission to read certain Facebook GraphQL POST requests made by the Facebook page you are visiting.

The Extension only stores matching Facebook GraphQL requests that are relevant to supported media discovery. The locally stored request data may include:

The Facebook GraphQL request URL
fb_api_req_friendly_name
av
__user
__a
__dyn
__csr
__hsi
__comet_req
fb_dtsg
jazoest
lsd
variables
doc_id

The variables field may include information needed by Facebook to load the selected page or media list, such as profile IDs, page IDs, group IDs, album IDs, pagination cursors, search text, search filters, or media identifiers, depending on the feature you use.

Purpose: the Extension uses these request fields to repeat or continue Facebook media-list requests from your browser so it can find videos, images, albums, thumbnails, and pagination results for the download task you started.

Storage and handling: this data is stored locally in chrome.storage.local under the Extension’s requests storage key. The Extension limits stored request records and removes request records for a browser tab when that tab is closed.

Sharing: Plugins Hub servers do not receive this Facebook GraphQL request data. The Extension may send these request fields back to Facebook.com from your browser when it fetches additional media results for the task you started. Because those requests are made to Facebook, Facebook or Meta receives them and may process them under Facebook’s own policies.

2.3 Facebook Cookies and Session Status

The Extension uses Chrome’s cookies permission to check whether a Facebook c_user cookie exists for facebook.com.

Purpose: this check tells the Extension whether the current browser appears to be signed in to Facebook, so the Extension can display the correct connection or authorization state.

Storage and handling: the Extension checks the number of matching c_user cookies. It does not store the cookie value in Plugins Hub systems.

Sharing: Plugins Hub servers do not receive your Facebook cookie values. Facebook cookies may be included by Chrome in normal requests to Facebook.com when you browse Facebook or when the Extension makes Facebook requests from your browser.

2.4 Facebook Video Tokens and Request Parameters

For one-click video downloads, the Extension may read Facebook page script data and media metadata, including:

async_get_token
Facebook USER_ID
Video IDs
Video titles
Video page URLs
Facebook embedded video URLs
Direct video URLs, DASH manifests, audio stream URLs, and video stream URLs

Purpose: the Extension uses this data to request available video resources from Facebook endpoints such as facebook.com/video/video_data_async/, Facebook video or embed pages, m.facebook.com, and fbcdn.net media resources.

Storage and handling: these values are used in browser memory or message passing inside the Extension while resolving and downloading a selected video. They are not uploaded to Plugins Hub servers.

Sharing: these values may be sent to Facebook, Meta, or Facebook CDN domains from your browser because they are part of the Facebook media request needed to download the selected video. Plugins Hub does not receive or store these values on its servers.

2.5 Downloaded Video, Audio, Image, and Album Files

When you download media, the Extension may process:

Direct media URLs
Video and audio stream URLs
Binary video stream data
Binary audio stream data
Merged video output
Image files, thumbnails, and album image resources
File names and folder names used by Chrome downloads

Purpose: this data is used to create the final file and save it to your device.

Storage and handling: downloads are handled locally in Chrome. When Facebook provides separate audio and video streams, the Extension creates an offscreen document and uses FFmpeg WebAssembly bundled with the Extension to merge the streams locally. Temporary stream data and generated blob URLs are processed in browser memory and cleaned up after the download flow completes.

Sharing: Plugins Hub servers do not receive downloaded media files, merged files, stream bytes, generated blob URLs, filenames, or folder names. Chrome receives the download URL, filename, and folder path through the local chrome.downloads API so it can save the file on your device.

2.6 Local Settings, Usage, and Extension State

The Extension stores some operational data in your browser, including:

Extension settings such as request interval
Current task ID, last task time, and active task state
Locally cached Facebook request records
Daily Free plan usage counters, billing-period start, billing-period end, and remaining usage state
Local subscription status or product information used to display Free or Pro access
Download queue state, progress state, and cached lookup results
Cached Facebook GraphQL document IDs or related local lookup data
Locally detected text used to identify Facebook live videos in different languages
Review prompt timestamp, if a review prompt is shown

Purpose: this data is used to operate the Extension, manage downloads, prevent duplicate prompts, remember settings, enforce Free plan limits locally, and improve reliability while you use the Extension.

Storage and handling: this data is stored in chrome.storage.local or browser localStorage on your device. It is not uploaded to Plugins Hub servers unless you choose to share it with support.

Sharing: Plugins Hub servers do not receive this local operational data during normal Extension use.

2.7 Account, Authentication, Pricing, and Subscription Data

The Extension can be used for free within the free limits. If you sign in or use paid features, the Extension may process account and subscription data.

Plugins Hub may receive or process:

Your Google account email address
Your Google account name
Your Google account profile photo
Supabase authentication session information used to keep you signed in
Product name and product ID for Facebook Videos Downloader
Your email address and product ID when checking subscription status
Subscription status, purchase status, renewal status, cancellation status, plan type, and related billing records
Stripe customer IDs, subscription IDs, checkout status, product IDs, price IDs, transaction status, and payment status

Purpose: this data is used to authenticate you, connect your account to paid access, display pricing, check whether Pro features are active, process payments, and provide customer support.

Storage and handling: Google/Supabase authentication access and refresh tokens are stored in chrome.storage.sync by the Extension so sign-in can work across extension views. Depending on your Chrome settings, Chrome may sync chrome.storage.sync data through your browser account. Plugins Hub stores account and subscription records on backend systems as needed to operate paid access.

Sharing: account and subscription data may be shared with Google Sign-In, Supabase, Stripe, Gmail, and Zoho Mail as described in Section 7.

2.8 Support Data

If you contact Plugins Hub for help, we may receive:

Your email address
Your name
Your message
Screenshots or attachments you send
Extension version, browser version, error details, or troubleshooting information you choose to provide

Purpose: this data is used to respond to your request, investigate problems, verify purchases, and provide support.

Storage and handling: support messages may be retained in email or support systems for customer service, fraud prevention, business records, and legal compliance.

3. User Data Plugins Hub Does Not Collect Through Its Servers

Plugins Hub does not collect, upload, host, sell, or review the following through its servers during normal Extension use:

Downloaded Facebook videos, images, albums, audio streams, or merged media files
Lists of Facebook media detected on a page
Facebook captions, comments, reactions, friends lists, group member lists, messages, or private communications
Your Facebook password
Your full Facebook cookie values
Your general browsing history outside the Facebook pages or supported Facebook embedded frames where the Extension is operating
The contents of unrelated webpages
Advertising identifiers for tracking

The Extension is not used for advertising tracking, behavioral profiling, data brokerage, resale of user data, spyware, or AI processing of downloaded Facebook media.

4. How User Data Is Used

The Extension uses locally processed Facebook data only to provide the media download features selected by you, including:

Detecting supported Facebook videos, images, albums, and embedded media
Showing download buttons and Extension controls
Fetching additional Facebook media results for a bulk task you started
Resolving direct media URLs and stream URLs
Downloading selected files
Merging video and audio streams locally when needed
Saving files to your device
Organizing downloads into folders
Managing task progress, retries, pause/resume behavior, and local settings
Enforcing Free plan limits and enabling Pro access after subscription verification

Plugins Hub uses account, authentication, pricing, subscription, payment, and support data only to:

Authenticate users who choose to sign in
Display Free and Pro pricing
Check subscription or purchase status
Enable paid features
Process payments through Stripe
Respond to support requests
Prevent fraud or misuse
Maintain security
Keep tax, accounting, payment, and business records
Comply with legal obligations

5. How User Data Is Stored

User data may be stored in the following places:

Browser memory. Used temporarily while detecting media, resolving URLs, downloading streams, merging files, and updating progress.
Chrome local extension storage. Used for request records, settings, task state, usage counters, cached lookup results, review prompt timestamps, and similar operational data.
Browser localStorage. Used for some cached lookup data needed by the scraper.
Chrome sync extension storage. Used for Google/Supabase authentication tokens if you sign in. Chrome may sync this data according to your browser settings.
Your device downloads folder or selected download location. Used for downloaded videos, images, albums, and generated files.
Plugins Hub backend systems. Used only for account, pricing, subscription, purchase, and support records.
Stripe. Used for payment and billing records.
Gmail or Zoho Mail. Used for support and account-related communications.

You can delete local Extension data by uninstalling the Extension or clearing the Extension’s site and extension storage in Chrome. Downloaded files remain on your device until you delete them.

Server-side account, payment, subscription, and support records are retained for as long as needed to provide paid access, process payments, maintain business records, comply with legal, tax, accounting, and reporting obligations, resolve disputes, prevent fraud, and enforce agreements.

6. Chrome Extension Permissions

The Extension uses Chrome permissions for the following purposes:

storage: stores local settings, cached Facebook request records, task state, usage counters, review prompt timestamps, cached lookup data, subscription-related state, and authentication tokens.
cookies: checks whether the Facebook c_user cookie exists so the Extension can determine whether the browser appears signed in to Facebook. The Extension does not send Facebook cookie values to Plugins Hub.
downloads: saves selected videos, images, albums, and generated files to your device through Chrome.
webRequest: reads selected Facebook GraphQL POST request fields from Facebook.com so the Extension can continue media-list requests for the download task you start.
offscreen: runs a local offscreen document for stream downloading, blob creation, and local FFmpeg WebAssembly processing when video and audio streams must be merged.
Facebook.com host access: lets the Extension run on Facebook pages, detect Facebook media, and make Facebook media requests from your browser.
fbcdn.net host access: lets the Extension download Facebook CDN media resources.
pluginshub.site host access: lets the Extension fetch pricing, authenticate, and check subscription status with Plugins Hub services.

The Extension does not use these permissions to track unrelated browsing activity, collect unrelated webpage content, or send unrelated browsing history to Plugins Hub.

7. How User Data Is Shared

Plugins Hub does not sell user data.

The following parties may receive data as described below:

Facebook, Meta, and Facebook CDN domains. When you browse Facebook, view embedded Facebook media, or use the Extension to fetch media results or media files, your browser sends requests to Facebook.com, m.facebook.com, Facebook embedded pages, and fbcdn.net. These requests may include Facebook cookies, Facebook request parameters, request tokens, account or session identifiers, media identifiers, group/page/profile identifiers, search parameters, and media URLs needed by Facebook to return the requested content. These requests are made directly from your browser to Facebook or Meta services, not through Plugins Hub servers.
Plugins Hub backend at pluginshub.site. Receives product/pricing requests and, if you sign in or use Pro features, your email address and product ID for subscription checks. Plugins Hub does not receive your downloaded Facebook files or Facebook media lists.
Supabase. Provides authentication and backend account/session services used by Plugins Hub. Supabase may process authentication tokens, account identifiers, email addresses, and related account records.
Google Sign-In. Provides optional sign-in. If you sign in with Google, Google provides Plugins Hub with your email address, name, and profile photo.
Stripe. Processes purchases, subscriptions, renewals, cancellations, invoices, and payment status. Plugins Hub does not store full credit card numbers.
Gmail and Zoho Mail. Used for support and account-related email communications.
Chrome and the local browser environment. Chrome stores extension data locally or in Chrome sync storage according to your browser settings, and Chrome receives download URLs, filenames, and folder paths through the local downloads API so files can be saved on your device.

We may also disclose information if required by law, subpoena, court order, legal process, or a valid government request, or if we believe disclosure is necessary to protect the rights, property, safety, or security of Plugins Hub, users, or others.

8. Your Choices and Controls

You control when to use the Extension and which Facebook pages, groups, profiles, albums, videos, images, search results, or embedded videos to process. If you do not want the Extension to process a page or media item, do not run the Extension on that page or item.

You can:

Stop, pause, resume, or cancel supported download tasks in the Extension UI
Delete downloaded files from your device
Clear local Extension data through Chrome settings
Uninstall the Extension to remove local extension storage
Sign out of the Extension
Manage Google connected-app access in your Google account settings
Contact Plugins Hub to request deletion of server-side account or subscription records, subject to legal, tax, accounting, payment, fraud-prevention, security, and dispute-resolution retention requirements

9. Security

Plugins Hub uses reasonable technical, administrative, and organizational safeguards designed to protect the limited account, subscription, payment-related, and support information processed by our services.

Facebook media downloading and stream merging are designed to happen locally in your browser. No method of electronic transmission or storage is completely secure, and we cannot guarantee absolute security.

10. Third-Party Platform Notice

Facebook Videos Downloader works with Facebook content and Facebook embedded media selected by users. Facebook, Meta, fbcdn.net, and third-party websites that display Facebook embedded media are not operated or controlled by Plugins Hub.

Your use of Facebook and third-party websites remains subject to their own terms, privacy policies, account settings, and permissions. The Extension does not give you ownership of third-party content and does not grant permission to use content in ways prohibited by law, copyright rules, or platform terms.

11. Children’s Privacy

The Extension and related services are not directed to children under 13, and children under 13 may not use them. Plugins Hub does not knowingly collect personal information from children under 13.

If you believe a child has provided us with personal information, contact contact@pluginshub.site and we will take reasonable steps to delete the information where required by law.

12. Changes to This Policy

Plugins Hub may update this Privacy Policy from time to time. When we make changes, we will update the “Last Updated” date and post the revised version on this page.

If we make material changes to how we collect, use, store, or share personal information, we will provide additional notice where required by law.

13. Contact

If you have questions, concerns, or requests about this Privacy Policy or Facebook Videos Downloader’s privacy practices, contact us:

Email: contact@pluginshub.site

Website: https://pluginshub.site