# Facebook Comment Scraper - Posts & Reels \[NO COOKIES] ✅ (`unseenuser/fb-comments`) Actor Pull every comment from any public Facebook post or reel: text, timestamp, reply count, author, and a full per-reaction breakdown (like, love, care, haha, wow, sad, anger and more). Fetch threaded replies on demand. No login, no cookies. Built for sentiment, NLP and social listening. - **URL**: https://apify.com/unseenuser/fb-comments.md - **Developed by:** [Unseen User](https://apify.com/unseenuser) (community) - **Categories:** Social media, Developer tools, Automation - **Stats:** 4 total users, 3 monthly users, 100.0% runs succeeded, 4 bookmarks - **User rating**: 5.00 out of 5 stars ## Pricing $3.00 / 1,000 results This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are a software tools running on the Apify platform, for all kinds of web data extraction and automation use cases. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Actors are written with capital "A". ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. The best way to integrate Actors is as follows. In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js.md): ```bash npm install apify-client ``` In Python projects, use official [Python client library](https://docs.apify.com/api/client/python.md): ```bash pip install apify-client ``` In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md): ````bash # MacOS / Linux curl -fsSL https://apify.com/install-cli.sh | bash # Windows irm https://apify.com/install-cli.ps1 | iex ```bash In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp.md). If your project is in a different language, use the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ## 💬 Facebook Comments Scraper (No Login) > **Scrape Facebook post and reel comments - text, timestamp, reply count, full per-reaction breakdown and author. Threaded replies on demand. No login, no cookies.** > **Tier:** Combined-Endpoint Bundle - Engagement / Sentiment Niche --- ### 📋 Quick Reference | Property | Value | |---|---| | **Public Name (Apify Title)** | `💬 Facebook Comments Scraper (No Login)` | | **Apify Slug** | `UnseenUser/facebook-comments-scraper` | | **Short Description (160 chars)** | Scrape Facebook post and reel comments - text, timestamp, reply count, full per-reaction breakdown and author. Threaded replies on demand. No login, no cookies. | | **Effective Date** | May 5, 2026 | | **Keywords** | `facebook comments scraper`, `comment reactions`, `social listening`, `sentiment analysis`, `threaded replies`, `no login facebook` | --- ### ⚡ Why This Actor? Input a public Facebook post or reel URL, get back every comment with text, timestamp, reply count, author, and a full per-reaction breakdown (thankful, like, love, care, haha, wow, sad, anger, pride, confused) on every single comment. Fetch threaded replies on demand. No login, no cookies. The per-reaction breakdown is native here - the category leader returns only a single likes count, and a competitor charges for it as a premium feature. This works on known post and reel URLs (or feedback IDs); it does NOT search across comments by keyword, and it never touches private content. ### 🎯 Use Cases - **Sentiment and NLP research** - feed comment text and per-reaction signal into models - **Social listening** - track how an audience reacts to a post or campaign in detail - **Engagement analysis** - measure not just likes but the full emotional reaction mix per comment - **Community management** - surface threaded replies for moderation and response triage - **Audience research** - understand who is commenting and how they react - **Lead signals** - spot high-intent commenters on a relevant post (with lawful basis for any follow-up) ### 🚀 Quick Start 1. Click **Try for free** on this Actor's page 2. Enter the required identifier (see Inputs Overview below) 3. Run the Actor 4. Download results as JSON, CSV, or XLSX, or pull via Apify API ### ⚙️ Inputs Overview | Input | Type | Required | Description | Example/Allowed Values | |---|---|---|---|---| | `postUrls` | array of strings | ✅ | Public Facebook post or reel URLs to scrape comments from | `https://www.facebook.com/reel/753347914167361` | | `feedbackIds` | array of strings | ❌ | Fast path: pass a `feedback_id` (from the companion Post actor) instead of a URL | `feedback:123...` | | `maxComments` | integer | ❌ | Max comments per post. Default 200, minimum 1 | `200` | | `fetchReplies` | boolean | ❌ | Pull the reply thread for every comment that has replies | `false` | | `maxRepliesPerComment` | integer | ❌ | Max replies per comment when replies on. Default 50 | `50` | | `excludeAuthorGender` | boolean | ❌ | Strip the inferred `author.gender` field from every output row | `false` | ### 💰 Pricing Pay-per-event model on Apify. See the Actor's Apify page for exact per-event pricing. > **Fast mode:** passing a `feedback_id` (obtainable from the companion Facebook Post actor) tends to be faster than passing a URL. ### Free plan limit Free Apify users get up to **50 results per run**. Paying users are not affected and receive results normally. This limit was set by the Actor developer, not by Apify. To remove it and receive unlimited results, upgrade to any paid Apify plan: https://apify.com/pricing When a free plan run hits the cap, the Actor finishes successfully (status `SUCCEEDED`) and the run's status message explains what happened. No error is raised, so the first 50 results are fully usable as normal. ### 📤 Output Each result row carries the comment (or reply) object plus a `_metadata` block: ```json { "type": "comment", "postUrl": "https://www.facebook.com/reel/753347914167361", "parentCommentId": null, "comment": { "id": "Y29tbWVudDox...", "text": "Comment body text...", "created_at": "2025-09-01T01:10:40.000Z", "reply_count": 1, "reaction_count": 95, "reactions": { "thankful": 0, "like": 79, "love": 4, "care": 0, "haha": 1, "wow": 11, "sad": 0, "anger": 0, "pride": 0, "confused": 0 }, "author": { "id": "pfbid02Sdz...", "name": "Commenter Name", "gender": "FEMALE", "short_name": "Commenter" } }, "_metadata": { "fetched_at": "2026-05-25T12:34:56.789Z", "post_url": "https://www.facebook.com/reel/753347914167361", "feedback_id_used": null, "page": 2 } } ```` Reply rows set `type: "reply"` and populate `parentCommentId`. The Apify UI ships three dataset views out of the box: a comments overview, a per-reaction breakdown table, and an errors view. ### ❓ FAQ **Q: Is this legal?** A: Your downstream use of the data is your responsibility - see the full Terms of Service and the Actor-Specific Addendum below for details. **Q: Do I need any third-party account?** A: No. You only need an Apify account. **Q: What about Facebook's anti-scraping enforcement?** A: Meta's Terms restrict automated extraction. Your downstream use must comply with Meta's Terms. **Q: What if Meta sends a cease-and-desist?** A: Notify UnseenUser within 48 hours via the Apify profile contact form (apify.com/UnseenUser) and cease using this Actor immediately. **Q: Can I use this data to train AI?** A: NO. Meta's Terms prohibit AI training on Facebook data, and each comment is independently copyrighted by its author. **Q: What about minors?** A: Facebook has many under-18 users, and commenters may be minors. This Actor's Terms strictly prohibit using data of users you know or suspect are minors. **Q: Does the per-reaction breakdown really come on every comment?** A: Yes. Each comment row includes a `reactions` object with counts for thankful, like, love, care, haha, wow, sad, anger, pride and confused - not just a single likes total. **Q: Should I pass a URL or a feedback ID?** A: Either works. A `feedback_id` (from the companion Post actor) tends to be faster. Use it when you are paging a lot of comments from the same post. **Q: When should I enable threaded replies?** A: Only when you need the reply threads. **Q: What is the `author.gender` field?** A: An inferred gender label on comment authors. It should be treated as sensitive-adjacent and not relied on for accuracy. Set `excludeAuthorGender=true` to strip it from output rows. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ## Apify Actor - Terms of Service **Version:** 4.0 **Effective Date:** May 5, 2026 ------------------------------- ### 0. ACCEPTANCE BY USE - IMPORTANT **Read this section first.** These Terms of Service ("Terms") form a binding legal agreement between you ("User," "you," "your") and UnseenUser, the Publisher of this Apify actor ("UnseenUser," "the Publisher," "we," "us," "our"). #### 0.1 How You Accept These Terms You accept these Terms by **any of the following actions**, each of which constitutes a clear, affirmative act of acceptance: - (a) **Running the Actor** - Initiating any execution of the Actor on the Apify platform - (b) **Using any output** returned by the Actor for any purpose - (c) **Continuing to access** the Actor's listing or documentation after these Terms are visible #### 0.2 Continuing Acceptance Each time you run the Actor or use its outputs, you reaffirm your acceptance of the then-current Terms. If you do not agree to these Terms or any subsequent update, you must stop using the Actor immediately. #### 0.3 No Anonymous Acceptance You cannot disclaim acceptance by: - Failing to read these Terms before running the Actor - Running the Actor through automated systems - Sharing your Apify account with others who may not have read these Terms By the act of running the Actor on Apify, you bind yourself, your organization (if applicable), and any individuals or systems acting on your behalf or under your authority. #### 0.4 If You Do Not Accept ## **If you do not agree to these Terms, you must not run the Actor.** No use is authorized without acceptance. ### PREAMBLE - UNDERSTANDING THE ARCHITECTURE Before using the Actor, please understand the technical architecture of the service: #### The Data Flow You (User) -> Apify Platform -> Actor (software) -> Third-Party API -> Source Platform You (User) <- Apify Platform <- Actor (software) <- Third-Party API #### What Each Party Does - **You (the User):** Run the Actor on the Apify platform with input parameters you choose - **Apify:** Operates the cloud infrastructure that hosts and executes Actors. Apify is a Czech-incorporated company (Apify Technologies s.r.o.) governed by its own Terms of Service. - **The Publisher (us):** Publishes software code (the Actor) on Apify's platform. The Actor is a thin wrapper that translates your input into requests to a third-party API and returns the API's responses to you. **The Publisher does not operate scraping infrastructure. The Publisher does not store or retain data returned by the Actor. The Publisher does not see, log, or process the personal data of any individuals returned in the Actor's outputs beyond what is incidental to passing the data through.** - **Third-Party API Provider:** An independent third-party data infrastructure provider that operates scraping infrastructure and returns data from source platforms. - **Source Platform:** LinkedIn, TikTok, YouTube, Reddit, Linktree, etc. These are the platforms whose publicly visible data is accessed by the Third-Party API Provider. #### Why This Matters ## Your relationship with the Publisher is that of a **software user** to a **software vendor**. The Publisher has the responsibilities of a software vendor (functional code, accurate documentation) and the limits of one (the Publisher is not responsible for how you use the data you obtain). These Terms operate alongside but do not replace: - Apify's Terms of Service and Acceptable Use Policy (governing your relationship with Apify) - The Third-Party API Provider's Terms of Service (governing the underlying data infrastructure) - Source Platform terms (LinkedIn, TikTok, etc.) governing the public data accessed - Applicable law in your jurisdiction and the jurisdictions of data subjects These Terms incorporate the actor-specific addendum published in each Actor's individual listing ("Addendum"). In the event of a conflict, the more restrictive provision applies. *** ### 1. NATURE OF THE SERVICE #### 1.1 What the Actor Is The Actor is a software program published on the Apify platform. Each Actor: - (a) Accepts structured input from you on the Apify platform - (b) Translates that input into HTTP requests to an upstream third-party API - (c) Receives HTTP responses from that third-party API - (d) Returns the response data to you in a structured format on the Apify platform The Actor's source code is hosted on Apify's infrastructure. The Actor runs in Apify's cloud, not on the Publisher's servers. The Publisher operates no servers running the Actor. #### 1.2 What the Actor Is Not The Actor is **not**: - (a) A scraping tool - the Publisher does not operate scraping infrastructure, proxies, headless browsers, or fake accounts - (b) A direct connection to any source platform - connections to source platforms are made by the upstream Third-Party API Provider - (c) A data storage or data retention service - the Publisher does not maintain a database of any data the Actor returns - (d) A licensed access channel to LinkedIn, TikTok, YouTube, Reddit, X (Twitter), Meta, Linktree, or any other source platform - (e) Affiliated with, endorsed by, sponsored by, or authorized by any source platform #### 1.3 The Publisher's Limited Role The Publisher's role is limited to: - (a) Designing and writing the Actor's source code - (b) Publishing the Actor on the Apify Store - (c) Maintaining the Actor (updating it when API providers change schemas) - (d) Providing documentation and customer support via Apify's contact mechanism The Publisher is a software vendor, similar to a developer who publishes an app on the Apple App Store or Google Play Store. The Publisher is not a data provider, data broker, data processor, or data controller for purposes of GDPR, CCPA, Israel's Privacy Protection Law, or equivalent. #### 1.4 The Third-Party API Provider's Role The upstream Third-Party API Provider is an independent third-party company. They: - (a) Operate the actual data scraping infrastructure - (b) Maintain relationships with source platforms (or accept the operational risk of accessing public data without such relationships) - (c) Provide their own Terms of Service governing their operations - (d) Are responsible for compliance obligations relating to the data collection itself The Publisher is a customer of this provider. The Publisher is not their agent, partner, or representative. *** ### 2. WHO MAY USE THE ACTOR #### 2.1 Eligibility You may use the Actor only if: - (a) You are at least 18 years old or the age of majority in your jurisdiction - (b) You have legal capacity to enter into binding contracts - (c) You are not located in or resident of a country subject to comprehensive sanctions by the United States, European Union, United Kingdom, or Israel - (d) You are not on any prohibited persons list #### 2.2 User Representations By using any Actor, you represent and warrant that: - (a) **Truthful identity:** Information you provide about your identity and intended use is accurate - (b) **Lawful intent:** Your intended use complies with applicable law in your jurisdiction - (c) **Source platform compliance:** You will independently comply with the Terms of Service of any source platform whose data you obtain through the Actor - (d) **Data subject rights:** Where Actor outputs include personal data, you will respect data subject rights under applicable law - (e) **No prohibited use:** You will not use the Actor for any of the purposes prohibited in Section 4 These representations are continuous - they must remain true throughout your use. *** ### 3. PERMITTED USES The Actor may be used for any lawful purpose, including: - Market research and competitive analysis - Academic research - Journalism and investigative reporting - Internal business intelligence - Brand monitoring - Recruitment research where consistent with applicable employment law - Building products that further process publicly available information lawfully Specific permitted uses for each Actor are described in that Actor's individual listing and Addendum. *** ### 4. PROHIBITED USES You may not use the Actor for any of the following: #### 4.1 Illegal Activity Activity illegal under the law of your jurisdiction, the User's jurisdiction, or the jurisdiction of any data subjects. #### 4.2 Harassment, Stalking, and Personal Targeting - Compiling profiles for harassment, stalking, or doxxing - Tracking individuals' movements or activities without their knowledge - Building profiles of journalists, activists, dissidents, or vulnerable populations for retaliatory purposes #### 4.3 Discrimination - Using outputs for discriminatory employment, lending, housing, or insurance decisions based on protected characteristics - Building lists for discriminatory purposes #### 4.4 Spam and Unsolicited Commercial Communication - Sending unsolicited marketing in violation of CAN-SPAM, CASL, GDPR, PECR, Israeli Anti-Spam Law (Section 30A of the Communications Law), or equivalent laws - Building "lead lists" from scraped contacts without proper consent infrastructure - Reselling contact data for spam purposes #### 4.5 Fraud and Deception - Identity theft or impersonation - Generation of fake reviews, testimonials, or coordinated inauthentic behavior - Election interference or political disinformation - Securities fraud #### 4.6 Source Platform Abuse - Using outputs to circumvent technical protection measures of source platforms - Creating fake accounts on source platforms based on Actor outputs - Vote manipulation, engagement manipulation, or platform algorithm gaming - Building services that competitively substitute for source platforms #### 4.7 Reselling the Actor's Service - Reselling raw Actor outputs as your own data product or scraping-as-a-service - Sharing your Apify credentials to provide third parties indirect access - Building competing API services using Actor outputs #### 4.8 AI Training Without Authorization - Using Actor outputs as training data for commercial AI/ML models without separate licensing authority from the source platform #### 4.9 Sensitive Targeting - Specifically targeting or profiling based on health conditions, sexual orientation, religious beliefs, political opinions, or other sensitive characteristics - Targeting children under 16 (or local age of consent for data processing) #### 4.10 Privacy Law Violations - Processing personal data of EU/UK/California/Israeli residents without complying with applicable privacy law - Failing to honor data subject access, deletion, or objection requests - Processing data for purposes incompatible with its publication context *** ### 5. SOURCE PLATFORM TERMS - YOUR RESPONSIBILITY #### 5.1 Acknowledgment The Actor accesses publicly visible data on third-party platforms ("Source Platforms") through the upstream Third-Party API Provider. Source Platforms include LinkedIn, TikTok, YouTube, Reddit, X (Twitter), Meta/Facebook, Linktree, Komi, Pillar, Linkbio, Linkme, and Amazon. #### 5.2 Your Sole Responsibility You acknowledge: - (a) **You are solely responsible for ensuring your downstream use of data obtained through the Actor complies with the Source Platform's Terms of Service** - (b) The Publisher makes no representation that any specific use is permitted under any Source Platform's terms - (c) The Third-Party API Provider, not the Publisher, bears responsibility for the lawfulness of the data collection itself - (d) You should review Source Platform terms before commercial use: - LinkedIn: https://www.linkedin.com/legal/user-agreement - TikTok: https://www.tiktok.com/legal/page/global/terms-of-service/en - YouTube: https://www.youtube.com/static?template=terms - X: https://twitter.com/en/tos - Reddit: https://www.redditinc.com/policies/user-agreement - Meta: https://www.facebook.com/legal/terms - Linktree: https://linktr.ee/s/terms/ #### 5.3 Cease-and-Desist Compliance If you receive a cease-and-desist letter or other legal demand from a Source Platform regarding your use of Actor outputs, you must: - (a) Cease the contested use immediately - (b) Notify UnseenUser within 48 hours via UnseenUser's Apify profile contact form (https://apify.com/UnseenUser) - (c) Cooperate with the Publisher as needed to mitigate - (d) Not assert against the Publisher any claim arising from your inability to use the Actor for that Source Platform *** ### 6. DATA PROTECTION - REFLECTING ACTUAL ARCHITECTURE #### 6.1 Roles Under Privacy Law For purposes of GDPR, UK GDPR, CCPA, Israel's Privacy Protection Law (PPL) including Amendment 13, and equivalents: - **You (the User) are the Data Controller** of any personal data you obtain through the Actor and subsequently process for your own purposes - **The upstream Third-Party API Provider** is the entity that collects data from source platforms - they bear the responsibilities of data processors or controllers (depending on context) for the collection itself - **The Publisher acts solely as a software vendor**, not as a data controller or processor, because the Publisher does not store, retain, or substantively process personal data - the Actor merely passes API responses through #### 6.2 No Data Retention by the Publisher The Publisher confirms: - (a) The Publisher does not maintain a database of personal data obtained through the Actor - (b) The Actor passes data from the Third-Party API directly to you on the Apify platform - data does not flow through the Publisher's infrastructure - (c) Apify's standard execution and operational logging may include limited information about Actor runs (input parameters, run duration, data volume) - this is governed by Apify's own privacy practices - (d) The Publisher does not access, view, or analyze your Actor outputs except as needed for technical support if you specifically share them with the Publisher #### 6.3 Your Obligations as Data Controller Where your use of the Actor involves processing personal data, you are responsible for: - (a) Establishing a lawful basis for your processing (consent, legitimate interest with documented balancing test, contract, etc.) - (b) Providing transparent notice to data subjects as required by applicable law - (c) Honoring data subject access, rectification, erasure, restriction, and portability requests - (d) Implementing appropriate security measures - (e) Conducting Data Protection Impact Assessments where required - (f) Appointing a Data Protection Officer if your operations require one - (g) Registering databases with applicable supervisory authorities - (h) Honoring opt-out requests for direct marketing - (i) Cross-border transfer safeguards where data crosses borders #### 6.4 Israel's Amendment 13 - User Compliance If your use of the Actor involves Israeli residents' personal data, you must comply with the Privacy Protection Law as amended (Amendment 13, effective August 14, 2025). These obligations are yours as the data controller, not the Publisher's as the software vendor. #### 6.5 Sensitive Data Targeting Restrictions You will not use the Actor to specifically target, profile, or build datasets focused on: - Health or medical conditions - Religious beliefs - Political opinions - Sexual orientation or gender identity - Genetic or biometric data - Criminal history - Children under 16 *** ### 7. INTELLECTUAL PROPERTY #### 7.1 Actor Code The Actor's source code, schemas, documentation, and branding are owned by the Publisher. You receive a limited, non-exclusive, non-transferable, revocable license to use the Actor for permitted purposes during your active subscription/run with Apify. #### 7.2 Output Data The Publisher claims no ownership over the public data the Actor returns. Source Platforms may have copyright, database rights, or other rights in their data; data subjects may have copyright in user-generated content. Your use of output data must respect these rights independently. #### 7.3 Restrictions You may not reverse engineer, decompile, or reuse the Actor's code in a competing actor. #### 7.4 Feedback ## Feedback you provide may be used by the Publisher to improve products without compensation to you. ### 8. PRICING AND PAYMENT #### 8.1 Apify Platform Billing Pricing is administered through Apify's pricing models. Apify processes all payments. Apify's payment terms govern refunds and disputes. #### 8.2 Pricing Changes The Publisher may change Actor pricing with at least 14 days' notice via the Actor's Apify listing. #### 8.3 No Refunds for Misuse ## If your access is suspended or terminated for breach of these Terms, you forfeit any unused balance and are not entitled to refunds. ### 9. SERVICE AVAILABILITY AND CHANGES #### 9.1 No Uptime Guarantee The Actor depends on: - (a) The Apify platform - (b) The upstream Third-Party API Provider - (c) Source Platforms' continued public accessibility Any of these may change behavior, restrict access, or become unavailable without notice. The Publisher makes no uptime guarantees. #### 9.2 Service Discontinuation ## The Publisher may discontinue any Actor at any time. Reasonable notice will be provided when feasible. ### 10. DISCLAIMERS #### 10.1 "AS IS" Service THE ACTOR IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR PURPOSE, NON-INFRINGEMENT, OR ACCURACY OF DATA. #### 10.2 No Representation of Lawfulness The Publisher makes no representation that your specific use of the Actor or the data it returns is lawful in your jurisdiction or under any Source Platform's terms. The burden of determining lawfulness for your use case is yours. #### 10.3 No Endorsement of Source Content ## Content returned by the Actor was created by third parties. The Publisher does not endorse, verify, or take responsibility for it. ### 11. LIMITATION OF LIABILITY #### 11.1 Aggregate Liability Cap TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL THE AGGREGATE LIABILITY OF THE PUBLISHER FOR ALL CLAIMS RELATING TO THE ACTOR EXCEED THE GREATER OF: - (a) ONE HUNDRED U.S. DOLLARS (US $100), OR - (b) THE AMOUNTS YOU PAID THROUGH APIFY FOR USE OF THE ACTOR IN THE THREE (3) MONTHS IMMEDIATELY PRECEDING THE EVENT #### 11.2 Excluded Damages THE PUBLISHER IS NOT LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR LOSS OF PROFITS, REVENUE, OR DATA, EVEN IF ADVISED OF THE POSSIBILITY. #### 11.3 Time Limit ## Any claim must be brought within one (1) year of the event. ### 12. INDEMNIFICATION #### 12.1 Your Indemnification of the Publisher You agree to defend, indemnify, and hold harmless the Publisher from any: - Claims arising from your use of the Actor - Claims arising from your violation of these Terms - Claims arising from your violation of any law (including privacy law) - Claims arising from your violation of any Source Platform's Terms of Service - Claims arising from your processing of personal data obtained through the Actor - Reasonable attorneys' fees and costs of defending such claims #### 12.2 Defense The Publisher may assume defense at your expense. You will cooperate with the Publisher's defense. #### 12.3 Scope The indemnification covers reasonable, foreseeable third-party claims arising from your use. It does not extend to: - Claims arising from the Publisher's gross negligence or willful misconduct - Claims regarding the Actor's source code itself (those are the Publisher's responsibility) - Claims regarding the Third-Party API Provider's data collection (those are their responsibility) *** ### 13. SUSPENSION AND TERMINATION #### 13.1 Termination by the Publisher The Publisher may terminate your access for material breach, illegal use, breach of warranty, or upon credible legal demand. #### 13.2 Effects of Termination Your license ends, you must cease use, and applicable provisions survive. #### 13.3 Termination by You ## You may stop using the Actor at any time on Apify. ### 14. DISPUTE RESOLUTION #### 14.1 Informal Resolution First Send a detailed written description of the dispute via UnseenUser's Apify profile contact form (https://apify.com/UnseenUser) and wait 60 days for resolution attempt before any formal claim. #### 14.2 Governing Law These Terms are governed by the substantive laws of the State of Israel, without regard to conflict of law principles. #### 14.3 Exclusive Jurisdiction Any dispute shall be brought exclusively in the competent civil courts of Tel Aviv-Jaffa, Israel. #### 14.4 No Class Actions You agree to bring claims only in your individual capacity. #### 14.5 Attorneys' Fees ## The prevailing party recovers reasonable attorneys' fees. ### 15. MISCELLANEOUS #### 15.1 Entire Agreement These Terms (with Addendum and incorporated documents) are the entire agreement. #### 15.2 Severability Unenforceable provisions are reformed to the minimum extent or severed. #### 15.3 Assignment You may not assign without the Publisher's consent. The Publisher may assign to affiliates, successors, or acquirers. #### 15.4 Force Majeure Neither party is liable for failure due to events beyond reasonable control, including changes by Source Platforms or the Third-Party API Provider, or actions by Apify. #### 15.5 Third-Party Beneficiaries Apify and the upstream Third-Party API Provider are intended third-party beneficiaries of Sections 4 (Prohibited Uses), 5 (Source Platform Compliance), and 12 (Indemnification). #### 15.6 Survival Sections 0 (Acceptance), 4, 5, 6, 7, 10, 11, 12, 14, and 15 survive termination. #### 15.7 Language English controls. Translations are for convenience only. #### 15.8 Publisher Identification for Legal Process ## The Publisher operates on the Apify platform under the username **UnseenUser** (apify.com/UnseenUser). The Publisher is a registered legal entity. Upon receipt of valid legal process (subpoena, court order, or equivalent) directed through Apify's official channels, the Publisher's full legal identity may be disclosed as required by law. This Section ensures that you have a valid path to legal recourse if needed. ### 16. ACKNOWLEDGMENT By using any Actor, you acknowledge that: - (a) You have read these Terms - (b) You understand the architecture: you are using software (the Actor) on Apify's platform that calls third-party APIs - (c) You accept responsibility for your use, including for compliance with Source Platform terms - (d) Your indemnification obligations cover third-party claims arising from your use - (e) Disputes are resolved in Israeli courts - (f) The Publisher's identity, while not publicly disclosed in this listing, can be obtained through valid legal process via Apify For questions, use UnseenUser's Apify profile contact form (https://apify.com/UnseenUser) before running the Actor. *** ### APPENDIX - Document Version History | Version | Date | Summary | |---------|------|---------| | 1.0 | May 5, 2026 | Initial publication | | 2.0 | May 5, 2026 | Hardened (over-broad - treated User as data broker) | | 3.0 | May 5, 2026 | Architecturally accurate - Publisher as software vendor | | 4.0 | May 5, 2026 | **Anonymous Publisher.** All personally identifying information removed. Acceptance-by-Use mechanism formalized. | ---------------------------------------------------------------------------------------------------------------------------------------- ## *These Terms reflect best practices for anonymous Apify actor publishing as of May 2026. Not a substitute for legal advice. Consult qualified Israeli commercial counsel before deploying.* ## 🛡️ Actor-Specific Terms of Service Addendum ### 🛡️ Actor-Specific ToS Addendum - 💬 Facebook Comments Scraper This addendum supplements the Master Terms of Service V4.0. By running this Actor, you accept both the Master ToS and this addendum. #### A. Architectural Disclosure This Actor is a software wrapper on the Apify platform. It accepts your input parameters, retrieves Facebook comment data and (optionally) threaded replies via an upstream third-party API provider, combines the results into a structured output, and returns the combined data to you on the Apify platform. UnseenUser does not store, log, or substantively process the data returned. The data flows from the upstream provider through Apify's runtime directly to you. #### B. Nature of Data Returned This Actor returns Facebook comment data: comment text, timestamp, reply count, a total reaction count and a full per-type reaction breakdown (thankful, like, love, care, haha, wow, sad, anger, pride, confused), and the comment author's id, name, short name and an inferred gender label. When replies are enabled it returns the same shape for each reply with a parent comment id. Where the Actor's output includes individual people's names, photos, contact details, or content authored by them, that data constitutes **personal data** subject to GDPR, CCPA, Israeli Privacy Protection Law (including Amendment 13), and equivalent privacy laws in your downstream processing - but **only in your hands as the data controller**, not in UnseenUser's hands as the software vendor. Comment text, reaction patterns and an inferred gender label together make this a high-sensitivity dataset. #### C. Permitted Use Cases You may use this Actor for the following purposes (non-exhaustive list): - **Sentiment and NLP research** - feed comment text and reaction signal into models - **Social listening** - track audience reaction to a post or campaign - **Engagement analysis** - measure the full emotional reaction mix per comment - **Community management** - surface threaded replies for moderation and triage - **Audience research** - understand who comments and how they react - **Lead signals** - identify high-intent commenters with a lawful basis for any follow-up #### D. Specifically Prohibited Uses In addition to Master ToS Section 4 prohibitions, you may NOT: - Use commenter data to power mass-DM or auto-message tools that contact engagers - Build or sell engagement-scoring databases of named individuals (data broker activity) - Track sensitive-content engagement to identify or target vulnerable people - Republish comments verbatim in commercial products without licensing - Train commercial AI/ML models on comment text without separate licensing authority - Use the inferred `author.gender` field (or any reaction-based inference) to make employment, lending, housing or insurance decisions - Aggregate commenters across many posts to build personality or political profiles without consent #### E. Platform Terms of Service Considerations Meta's Terms of Service prohibit automated extraction. Meta has aggressively litigated against scrapers (Meta v. BrandTotal - settled with permanent injunction; Meta v. Octopus Data; Meta v. Bright Data - pending). Facebook's Terms of Service prohibit automated extraction. This Actor accesses publicly visible comment data via the upstream Third-Party API Provider - that provider bears responsibility for the lawfulness of the data collection. Your downstream use must independently comply with Meta's Terms of Service. If Meta issues a cease-and-desist regarding data obtained via this Actor, notify UnseenUser within 48 hours via the Apify profile contact form (apify.com/UnseenUser) and cease your use immediately. #### F. Combined-Endpoint Data Sensitivity This Actor combines comments and (optionally) threaded replies in one run. The combination yields data that is more sensitive than either alone: - Comments alone: per-comment opinion + reaction data (medium-high sensitivity) - Replies alone: threaded conversation data (medium-high sensitivity) - **Combined**: a full conversational graph around a post - who said what, who reacted how, and how others responded - which is exactly the kind of behavioral dataset Meta targets in its lawsuits Use the combined output thoughtfully: do not sell it as a product, do not build a "Facebook comment intelligence" people-database with it, and use it for your own internal research and listening. #### G. Comment and Reply Author Personal Data - Heightened Care Comments and replies are deeply personal data. They reveal opinions and beliefs, topical interests, social and political views (when reacting to such content), and relationships (whose content a person engages with). This is high-sensitivity data under GDPR. Your lawful basis (legitimate interest, consent) must be carefully documented, and the Article 6(1)(f) balancing test must consider whether the data subject would reasonably expect their public comment to be used for commercial outreach - which recent European DPA decisions increasingly hold to be NO. Where possible, store only the engagement signal ("engaged with topic X") rather than the full comment text (GDPR Article 5(1)(c) data minimization). #### H. Reaction-Type Semantic Sensitivity Each Facebook reaction type carries meaning beyond a binary like: - **like** - neutral acknowledgment - **love / care** - strong positive or supportive connection - **haha** - humor (can be inappropriate on serious posts) - **wow** - surprise - **sad** - sympathy or distress - **anger** - strong negative reaction - **thankful / pride** - gratitude or affiliation - **confused** - uncertainty or disagreement The reaction type itself is meaningful behavioral data. Aggregating these patterns to label individuals (for example, "always reacts anger to political posts" used to flag a person) is high-sensitivity automated decision-making under GDPR Article 22 and requires a specific lawful basis and a route to human review. #### I. The `author.gender` Field - Special Care The output includes an inferred gender label on comment authors. You MUST treat this as sensitive-adjacent: - Do not over-promise its accuracy (it is inferred, not declared) - Do not use it as a basis for any decision about a person (hiring, pricing, targeting) - Use `excludeAuthorGender=true` to strip it from the dataset where it is not needed - Inferring or processing data that reveals protected characteristics can engage GDPR Article 9 (special categories) - tread carefully #### J. Comment Author Copyright and AI Training Each comment and reply is independently copyrighted by its author. You may quote with attribution (typically fair use), aggregate metrics (counts and reaction types are facts, no copyright issue), and perform sentiment analysis where results are aggregated (typically fair use). You may NOT republish comments verbatim in commercial products, translate and republish without authorization, build a "Facebook comment search engine," or train commercial AI/ML models on comment text without proper licensing. Recent litigation (NYT v. OpenAI, Andersen v. Stability AI, Reddit v. Perplexity) shows AI training on platform content is contested. Your AI training use is your own legal exposure. #### K. Sensitive-Engagement Patterns Some posts attract particularly sensitive comments: - **Layoff announcements** - commenters often include affected employees - **Illness or bereavement disclosures** - commenters share intimate personal information - **Political or social controversies** - commenters reveal protected-category views Do NOT weaponize these disclosures: do not build "vulnerability lists" from inferred life events, do not use bereavement comments as triggers for grief-targeting marketing, and do not use illness disclosures to identify candidates for medical products without explicit consent. #### L. Aggregation Boundary - The Critical Line The line between permitted listening and prohibited surveillance / data-broker activity is drawn around aggregation: | Use | Status | |---|---| | Analyze comments on one of your own posts for sentiment | ✅ Permitted | | Measure reaction mix on a competitor's campaign post | ✅ Generally permitted with proper lawful basis | | Aggregate one named individual's comments across many posts into a profile | ❌ Surveillance - prohibited | | Build and sell a database of "who commented angrily on which topics" | ❌ Data broker activity - prohibited under California Delete Act, GDPR Article 14, Israeli Privacy Law Amendment 13 | #### M. Minor Protection - CRITICAL Facebook has a significant under-18 user population, and commenters may be minors who do not disclose age. You MUST: - NOT use this Actor to scrape comments of users you know or suspect are minors - NOT use this Actor for any product or service targeted at minors without parental-consent mechanisms compliant with COPPA (US), GDPR Article 8 (EU), and Israeli Privacy Law (heightened sensitivity for minors) - DELETE any data you discover relates to a minor unless you have valid parental consent If a comment or author profile suggests the subject is under 18, treat the data as belonging to a minor by default. This restriction is non-negotiable. #### N. Data Subject Rights and Cease-and-Desist Protocol Individuals whose comment data you collect have rights under GDPR / CCPA / Israeli Privacy Law: access, deletion (Article 17), objection to direct marketing (absolute under Article 21), rectification, and portability. Build operational processes from day one to honor these with a typical 30-day SLA (a dedicated request email, a response log, a linked privacy policy). If a data subject contacts YOU directly demanding deletion, honor it promptly, do NOT route them to UnseenUser (the software vendor is not the data controller), you may suggest they contact Meta directly since the data originates there, and document the request and your response. If Meta, the upstream Third-Party API Provider, or a regulator contacts UnseenUser regarding your use, UnseenUser will notify Apify per Master ToS Section 8, may suspend access pending investigation, and you agree to provide documentation of your lawful basis on reasonable request. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- **Document Version:** 4.0 (anonymous Publisher, UnseenUser identified) **Master ToS Version:** 4.0 # Actor input Schema ## `postUrls` (type: `array`): Public Facebook post or reel URLs to scrape comments from. Either postUrls or feedbackIds must be provided. ## `feedbackIds` (type: `array`): Optional fast path: pass a feedback\_id (obtained from the companion Facebook Post actor) instead of a URL. Tends to be faster than passing a URL. ## `maxComments` (type: `integer`): Maximum number of comments to fetch per post. Pagination stops when this number is reached or when has\_next\_page becomes false. ## `fetchReplies` (type: `boolean`): COST WARNING: billed add-on. When true, for each comment with reply\_count > 0 the Actor calls the replies endpoint and emits each reply as its own dataset row. Leave off unless you need threaded replies. ## `maxRepliesPerComment` (type: `integer`): Maximum replies fetched per comment when fetchReplies is true. ## `excludeAuthorGender` (type: `boolean`): When true, the Actor strips the inferred author.gender field from every output row. This field is sensitive-adjacent and should be excluded if you do not need it. See README section I. ## Actor input object example ```json { "postUrls": [ "https://www.facebook.com/reel/753347914167361" ], "maxComments": 200, "fetchReplies": false, "maxRepliesPerComment": 50, "excludeAuthorGender": false } ``` # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "postUrls": [ "https://www.facebook.com/reel/753347914167361" ] }; // Run the Actor and wait for it to finish const run = await client.actor("unseenuser/fb-comments").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "postUrls": ["https://www.facebook.com/reel/753347914167361"] } # Run the Actor and wait for it to finish run = client.actor("unseenuser/fb-comments").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "postUrls": [ "https://www.facebook.com/reel/753347914167361" ] }' | apify call unseenuser/fb-comments --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=unseenuser/fb-comments", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "Facebook Comment Scraper - Posts & Reels [NO COOKIES] ✅", "description": "Pull every comment from any public Facebook post or reel: text, timestamp, reply count, author, and a full per-reaction breakdown (like, love, care, haha, wow, sad, anger and more). Fetch threaded replies on demand. No login, no cookies. Built for sentiment, NLP and social listening.", "version": "0.0", "x-build-id": "djcurm8w6DzaJSPbT" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/unseenuser~fb-comments/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-unseenuser-fb-comments", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/unseenuser~fb-comments/runs": { "post": { "operationId": "runs-sync-unseenuser-fb-comments", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/unseenuser~fb-comments/run-sync": { "post": { "operationId": "run-sync-unseenuser-fb-comments", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "required": [ "postUrls" ], "properties": { "postUrls": { "title": "Post / reel URLs", "type": "array", "description": "Public Facebook post or reel URLs to scrape comments from. Either postUrls or feedbackIds must be provided.", "items": { "type": "string" } }, "feedbackIds": { "title": "Feedback IDs (fast path)", "type": "array", "description": "Optional fast path: pass a feedback_id (obtained from the companion Facebook Post actor) instead of a URL. Tends to be faster than passing a URL.", "items": { "type": "string" } }, "maxComments": { "title": "Max comments per post", "minimum": 1, "type": "integer", "description": "Maximum number of comments to fetch per post. Pagination stops when this number is reached or when has_next_page becomes false.", "default": 200 }, "fetchReplies": { "title": "Fetch threaded replies", "type": "boolean", "description": "COST WARNING: billed add-on. When true, for each comment with reply_count > 0 the Actor calls the replies endpoint and emits each reply as its own dataset row. Leave off unless you need threaded replies.", "default": false }, "maxRepliesPerComment": { "title": "Max replies per comment", "minimum": 1, "type": "integer", "description": "Maximum replies fetched per comment when fetchReplies is true.", "default": 50 }, "excludeAuthorGender": { "title": "Exclude author.gender from output", "type": "boolean", "description": "When true, the Actor strips the inferred author.gender field from every output row. This field is sensitive-adjacent and should be excluded if you do not need it. See README section I.", "default": false } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } } } } } } } } } ```