Privacy Policy
Short version: the extension extracts Facebook group and Page post data only when you start a scrape from the extension popup. Scraped posts are stored locally in your browser and exported to files on your device. The publisher does not receive scraped Facebook posts, comments, images, media URLs, exported files, or your Facebook login information. Pro license activation and validation are handled through DodoPayments.
What This Policy Covers
This policy explains how the Facebook Group & Page Post Scraper Chrome extension handles data. The extension is designed to let users collect visible Facebook group and Page posts from their own browser session and export that data to JSON or CSV files.
This extension is not affiliated with, endorsed by, or sponsored by Meta Platforms, Inc. or Facebook.
Single Purpose
The extension has one purpose: to export visible Facebook group and Page post data selected by the user from the active Facebook tab into local JSON or CSV files, with optional local downloads of captured media assets.
Information Handled By The Extension
Facebook post data
When you start a scrape, the extension may read and store visible data from the current Facebook group or Page feed, including:
- Post author names and profile URLs.
- Post text, timestamps, reactions, comment counts, share counts, and post URLs.
- Image URLs, direct video URLs when available, and link metadata visible in the page.
- Loaded comments if comment collection is enabled.
Local settings and scrape metadata
The extension stores local settings and scrape progress, such as post count limits, scroll delay, target URL, target type, scrape start and finish times, batch keys, and progress counters.
License and quota metadata
For free quota tracking and Pro licensing, the extension stores a per-install identifier, quota counters, Pro license key, license activation instance ID, cached license status, and validation timestamps. This metadata is stored with Chrome extension storage. Some license and quota metadata uses chrome.storage.sync, so Chrome may sync it through the user's signed-in Chrome profile if Chrome Sync is enabled.
Information We Do Not Collect
- We do not collect or store your Facebook password.
- We do not collect Facebook cookies, session tokens, or authentication cookies.
- We do not collect your general browsing history.
- We do not collect location, health, financial, or payment card information through the extension.
- We do not run analytics, tracking pixels, or advertising SDKs inside the extension.
How Information Is Used
- Scraped Facebook post data is used to show progress, preview results, continue a scrape, and let you export JSON or CSV files.
- Settings are used to remember user choices such as scrape limits and scroll delay.
- Quota metadata is used to enforce the free usage limit.
- License metadata is used to activate, validate, cache, and deactivate Pro licenses.
- Optional asset URLs are used only to start local downloads through Chrome's downloads API when you enable asset downloads.
Where Information Is Stored
Scraped post data, scrape metadata, and settings are stored in Chrome extension storage on your device. Exported JSON, CSV, and downloaded media files are saved to locations managed by your browser and operating system.
License and quota metadata may be stored in Chrome's sync storage. The publisher does not receive Chrome Sync data unless the extension sends specific license validation data to DodoPayments as described below.
Information Shared With Third Parties
Scraped Facebook content is not sent to the publisher or to a scraping server. The extension does not transmit scraped posts, comments, exported files, image URLs, or media files to the publisher.
The extension uses DodoPayments for checkout and Pro license management. When you activate, validate, or deactivate a Pro license, the extension sends the license key, license instance ID when available, and per-install identifier to DodoPayments over HTTPS. Payment pages and subscription management pages are hosted by DodoPayments outside the extension. DodoPayments' privacy policy is available at https://dodopayments.com/privacy-policy.
We may disclose information if required by law, to protect against fraud or abuse, or as part of a merger, acquisition, or sale of assets, only where permitted by applicable law and Chrome Web Store policies.
Data Sale And Advertising
We do not sell user data. We do not use or transfer user data for personalized advertising, retargeting, interest-based advertising, creditworthiness decisions, lending eligibility, or data broker purposes.
Human Access To Data
The publisher does not receive scraped Facebook content, so the publisher's personnel do not read your scraped posts or exported files. If you choose to send files or screenshots for support, only the information you voluntarily provide will be reviewed for that support request.
Retention And Deletion
- Scraped data remains in local Chrome extension storage until you use the extension's clear-data control, overwrite it with a new scrape, remove the extension, or clear the relevant browser data.
- Exported files and downloaded media remain on your device until you delete them.
- License metadata remains while the extension is installed or until you deactivate the license where supported by the extension.
- Quota metadata remains while the extension is installed to enforce free usage limits.
Security
License activation and validation requests are transmitted over HTTPS. Scraped Facebook content is processed locally by the extension and stored using Chrome extension storage. You are responsible for protecting your device, operating system account, browser profile, exported files, and downloaded media.
Chrome Web Store Limited Use Disclosure
The extension's use of data is limited to providing and improving its single purpose: exporting visible Facebook group and Page posts selected by the user into local files. The extension does not transfer scraped Facebook content to third parties. The extension does not use user data for advertising. The extension does not allow humans to read user data except where the user voluntarily provides data for support, where required by law, or where necessary for security or abuse investigation.
Changes To This Policy
We may update this policy when the extension's behavior, permissions, third-party providers, or legal requirements change. The updated effective date will be shown at the top of this page.
Contact
For privacy questions or deletion requests, contact the publisher using the support contact listed on the Chrome Web Store listing for this extension.