Facebook Posts Scraper (No Login)

Pages, profiles AND groups in one actor - no login.

Scrape Facebook posts from any page, profile, or public group without logging in. Facebook posts no login required - call it from the Apify Console, the API, or your own backend. This facebook posts scraper returns post text, reactions, comment counts, top comments, SD and HD video URLs with thumbnails, and timestamps - covering Facebook page posts, Facebook profile posts, and Facebook group posts in a single run. Paginate as deep as you need. Optionally deep-enrich a known post URL (share count, view count, captions, music), pull full comment threads and replies, or fetch short-video transcripts.

Scope: this Actor extracts from known page, profile, group, or post URLs. It does not search posts by keyword or hashtag.

What you get out of the box (no surcharge)

• Date handling and top comments are included, not charged as extras. Some competing actors bill date filtering as a paid +$2/1k add-on; here it is part of every run.
• SD AND HD video URLs plus a thumbnail on every video post - richer media output than scrapers that return SD only or a single URL.
• Group mode returns post content only - never member lists. A hard rule of this Actor.

Fast-path: pair this Actor with the Comments Scraper

Pull a post here to get its feedbackId, then page its comments quickly with our Facebook Comments Scraper. Need full comment threads at scale? Use our dedicated Comments Scraper. This Actor's comment add-on is for convenience when you already have the posts.

---

Table of contents

• Free plan limit
• Why this Actor
• Modes
• Use cases
• Quick start
• Inputs
• Output
• Performance
• Limits and limitations
• Tips and best practices
• Use the Actor via the Apify API
• Scheduling and webhooks
• Integrations
• Errors and reliability
• FAQ
• Related scrapers
• Compliance
• Terms of Service - summary
• Master Terms of Service - V4.0
• Actor-Specific Addendum
• Support
• Changelog

---

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.

---

Why this Actor

• Multi-source in one run. Pages, profiles, and public groups - one schema, one output.
• One input field for everything: paste URLs, handles, @handles, page IDs, and group IDs together in any mix. The Actor figures out the right shape for each one.
• SD AND HD video URLs plus a thumbnail on every video post - richer media output than scrapers that only return SD or a single URL.
• Date handling and top comments are bundled, not charged as extras. Some competing actors bill date filters as a paid add-on; here they are included.
• Concurrent fetching. Sources, posts within a page, and add-ons all run in parallel under a safe limit, with a measured 3.5x to 7.6x speedup over a serial implementation.
• Group mode returns post content only - never member lists. A hard rule of this Actor.
• No login, no cookies. Logged-off public view only.
• Flat output rows drop into BI tools, Google Sheets, and Postgres without nested-object gymnastics.

---

Modes

Pick one mode per run via the mode input.

profile mode - pages and profiles (the Facebook timeline scraper)

Pulls a page or profile's recent posts in reverse-chronological order - this is the facebook timeline scraper for Facebook page posts and Facebook profile posts. Accepts page URLs (https://www.facebook.com/pacemorby), profile URLs (https://www.facebook.com/zuck), handles (pacemorby, @zuck), or numeric page IDs (100063669491743, which is the fastest of the three - prefer pageId in profile mode whenever you have it).

Cursor-paginates automatically to reach maxPosts. Returns 3 posts per backend call.

group mode - public groups

Pulls a public group's recent posts. Accepts group URLs (https://www.facebook.com/groups/123456789) or bare numeric group IDs.

Returns post content ONLY - the Actor never requests, derives, or emits group member lists or any member data. This is a policy rule, not a missing feature.

single_post mode - one post / reel

Deep-fetches a single post or reel and returns the rich field set: reaction count, share count, view count, captions URL, music, author verification, feedback ID, and more. Useful when you already have post URLs and want a maximum-detail row per post.

Only accepts post / reel URLs - bare numeric IDs and handles do not resolve to a single post and are skipped with a warning.

---

Use cases

• Brand and competitor monitoring - track a page's or profile's post output and engagement over time.
• Group social listening - pull public group post content (no member harvesting).
• Content research - a Facebook content scraper for studying what posts perform across pages, what hooks people are using, post length vs. engagement.
• Sentiment datasets - build text + engagement datasets for analysis or labeling.
• Engagement tracking - reactions, comment counts, and top comments over time.
• Lead-feed for outreach - pair with the Facebook Comments Scraper to pull commenters from high-intent posts.
• AI pipelines - supply post text to your own pipelines, subject to the Terms of Service.
• Video monitoring - SD and HD URLs let you build a video archive or analyze video performance.

---

Quick start

1. Click Try for free on this Actor's page.
2. Pick a mode (profile, group, or single_post).
3. Paste anything that identifies your target into the Profiles, pages, groups or posts field - one per line. Mix URLs, handles, and IDs freely.
4. Click Save & Start.
5. When the run finishes, open the Output tab and download as JSON, CSV, Excel, RSS, or HTML, or pull via the Apify API.

That is the whole flow. The defaults (30 posts per source, top comments included, all paid add-ons off) are sensible.

---

Inputs

Input	Type	Required	Default	Description
mode	enum	yes	profile	profile, group, or single_post.
sources	array of strings	yes	example URL	URLs, handles, @handles, page IDs, or group IDs - one per line. Normalized based on mode.
maxPosts	integer	no	30	Stop after this many posts per source. Minimum 3. Backend returns 3 posts per call, so larger values mean more pagination.
includeTopComments	boolean	no	true	Include the small batch of top comments returned with each post (bundled, no extra cost).
fetchAllComments	boolean	no	false	Billed add-on. Paginate the full comment thread per post.
fetchCommentReplies	boolean	no	false	Billed add-on. Pull replies per comment. Requires fetchAllComments.
fetchTranscript	boolean	no	false	Billed add-on. Captions for short videos (under 2 minutes). Empty transcripts are not billed.
enrichSinglePostFields	boolean	no	false	Billed add-on. Per-post deep fetch for share / view count, captions, music, verification, etc.

Sources - what you can paste

The Sources field accepts any mix of the following, one per line:

You paste	Mode	Resolves to
https://www.facebook.com/pacemorby	any	URL as-is
facebook.com/pacemorby, m.facebook.com/x, fb.com/y	any	https://www.facebook.com/... (normalized)
pacemorby or @pacemorby	profile, group	https://www.facebook.com/pacemorby
100063669491743 (numeric)	profile	sent as pageId (fastest path)
100063669491743 (numeric)	group	https://www.facebook.com/groups/100063669491743
https://www.facebook.com/groups/123456789	group	URL as-is
https://www.facebook.com/reel/486651220706068/	single_post	URL as-is

Duplicates are deduplicated automatically. Bare numeric IDs and handles are skipped in single_post mode (with a warning) because that mode requires an actual post URL.

Example input

{
    "mode": "profile",
    "sources": [
        "pacemorby",
        "100063669491743",
        "@zuck",
        "https://www.facebook.com/cnn"
    ],
    "maxPosts": 30,
    "includeTopComments": true
}

---

Output

One row per post, flat at the top level so the Apify table view and CSV / Excel exports render cleanly with no nested objects to unwind. Fields that are not populated by the run are simply absent from the row (no null padding).

Always present

Field	Type	Description
mode	string	The mode this row was produced in.
source	string	The source string as the Actor normalized it (URL or pageId:...).
page	integer	1-based page number within the source's pagination.
fetchedAt	string (ISO 8601)	When this row was emitted.

Present on successful post rows

Field	Type	When populated	Description
id	string	always	Facebook post ID.
url	string	always	Post URL.
permalink	string	always	Permalink to the post.
text	string	when post has text	Post text content.
authorName	string	always	Author display name.
authorId	string	always	Author numeric ID.
authorShortName	string	usually	Author short name.
reactionCount	integer	always	Total reactions.
commentCount	integer	always	Total comments.
publishTime	integer	always	Unix timestamp (seconds).
publishTimeIso	string (ISO 8601)	always	Same time, ISO 8601 - use this in the date column.
videoSdUrl	string	video posts	SD video URL.
videoHdUrl	string	video posts	HD video URL.
videoThumbnailUrl	string	video posts	Thumbnail image URL.
topComments	array	when includeTopComments=true	Few top comments with author and timestamp.

Present only with the matching add-on

Field	Type	Add-on
comments	array	fetchAllComments
replies	array	fetchCommentReplies
transcript	string	fetchTranscript (videos under 2 min)
enrichRaw	object	enrichSinglePostFields (deep-enrich response, also drives the next fields)
shareCount	integer	enrichSinglePostFields or single_post mode
videoViewCount	integer	enrichSinglePostFields or single_post mode
videoLengthSeconds	integer	enrichSinglePostFields or single_post mode
videoCaptionsUrl	string	enrichSinglePostFields or single_post mode
imageUrl	string	enrichSinglePostFields or single_post mode
musicId, musicTitle, musicAlbumArt	string	enrichSinglePostFields or single_post mode
feedbackId	string	enrichSinglePostFields or single_post mode (use it as the fast-path for the Facebook Comments Scraper)
authorIsVerified	boolean	enrichSinglePostFields or single_post mode
authorUrl	string	when the API returns it

Present on error rows

When a source fails (HTTP 4xx or network), the row replaces all post fields with:

Field	Type	Description
error	string	HTTP status and short body, or network error message.

The run continues with the next source - one bad source does not crash the whole run.

Output example (timeline mode, no add-ons)

{
    "id": "1204545088344463",
    "url": "https://www.facebook.com/reel/486651220706068/",
    "permalink": "https://www.facebook.com/reel/486651220706068/",
    "text": "I've had such a blast doing the challenge...",
    "authorName": "Pace Morby",
    "authorId": "100063669491743",
    "authorShortName": "Pace Morby",
    "reactionCount": 133,
    "commentCount": 12,
    "publishTime": 1734553170,
    "publishTimeIso": "2024-12-18T20:59:30.000Z",
    "videoSdUrl": "https://video-...mp4",
    "videoHdUrl": "https://video-...mp4",
    "videoThumbnailUrl": "https://scontent-...jpg",
    "topComments": [
        {
            "id": "Y29tbWVudDox...",
            "text": "How can I sign up?",
            "publishTime": 1734569761,
            "author": { "id": "pfbid02...", "name": "Sample Commenter", "gender": "MALE" }
        }
    ],
    "mode": "profile",
    "source": "https://www.facebook.com/pacemorby",
    "page": 1,
    "fetchedAt": "2026-06-03T19:33:42.649Z"
}

Dataset views

The Actor ships three Apify dataset views:

• Posts overview - the table that opens by default: post ID, author, text, permalink, reactions, comments, publish date, mode, source.
• Video posts - thumbnail (rendered inline), SD URL, HD URL.
• All fields - the raw rows, every key the run produced.

Export formats

The Apify dataset can be downloaded or streamed in any of:

• JSON (one array)
• JSONL (one row per line - ideal for big runs and AI pipelines)
• CSV
• XLSX (Excel)
• HTML (preview)
• RSS (atom-like feed)
• XML

---

Performance

The Actor runs sources, posts within a page, and add-ons in parallel under a safe concurrency limit.

Measured speedups vs. a strictly serial implementation (mocked 500 ms backend latency):

Scenario	Serial	Concurrent	Speedup
Profile / group mode, 10 sources	5.0 s	1.44 s	3.5x
Single_post mode, 30 URLs	15 s	1.97 s	7.6x
Per-post add-ons (enrich + comments + transcript) on one post	serial	one Promise.all	~3x on the add-on phase
Replies across N comments	serial	5 wide	up to 5x on replies

Concurrency limits used (hard-coded, no input knob to misconfigure):

• 5 sources at a time in profile / group mode
• 10 sources at a time in single_post mode
• 3 posts at a time within a returned page
• 5 reply fetches at a time

The free-user 50-row cap remains exact under all concurrency - verified with 100 single_post URLs racing 10-wide producing exactly 50 rows.

How long should a run take?

Rough rule of thumb for production runs against real Facebook:

Run shape	Typical wall-clock
1 profile, 30 posts, no add-ons	5 to 15 s
10 profiles, 30 posts each, no add-ons	25 to 60 s
1 profile, 30 posts, all add-ons	60 to 180 s (comments paginate)
30 single posts, no add-ons	5 to 10 s

Real latency varies with Facebook's response time, transcript availability, and how many comment pages a post has.

---

Limits and limitations

• No keyword or hashtag search. This Actor extracts from known page, profile, group, or post URLs only. There is no ?q= endpoint for Facebook posts.
• No login session. Posts that require login, friends-only posts, and private group content are not visible to this Actor by design.
• Group mode = post content only. Member lists, member counts, and member metadata are not available and will not be added.
• Single_post mode does not auto-resolve handles. Pass a real post / reel URL.
• Timeline endpoints return 3 posts per call. A maxPosts=30 profile run does 10 backend calls. The 3-per-page format is set upstream.
• Transcripts only for short videos. Videos longer than ~2 minutes do not have transcripts and the call is suppressed (and not billed).
• Free Apify users: 50 dataset rows max per run (see Free plan limit).
• Logged-off view. Reaction counts, comment counts, and other numbers reflect the public, logged-off view of the post.

---

Tips and best practices

• Use numeric pageId in profile mode when you have it. Faster than URL resolution.
• Set maxPosts to what you actually need. Pagination costs add up - if you only need the latest 9 posts, set maxPosts: 9, not 100.
• Start with timeline mode, then upgrade to enrichment only on the posts you care about. Run profile mode first to get IDs and permalinks; then run single_post mode (or enrichSinglePostFields=true) on the subset that warrants the extra cost.
• Use the feedbackId fast path. Single_post mode (or enrichSinglePostFields=true) returns a feedbackId. Pass that to the Facebook Comments Scraper for faster, cheaper comment scraping than this Actor's comment add-on.
• For periodic monitoring, schedule the Actor and deduplicate downstream on id - the Actor returns the most recent posts each run.
• For groups, confirm the group is public (logged-off browsing works). Private groups will return empty / error.
• For video posts, the SD and HD URLs are time-limited Facebook CDN URLs - download them quickly if you need to archive.

---

Use the Actor via the Apify API

This Actor doubles as a facebook post data api: hit one HTTP endpoint, get clean JSON rows back. Use it from any client (curl, Python, Node, your backend). Replace <APIFY_TOKEN> with your Apify API token.

Start a run (synchronous - waits for completion)

curl -X POST \
  "https://api.apify.com/v2/acts/unseenuser~facebook-posts-scraper/run-sync-get-dataset-items?token=<APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
    "mode": "profile",
    "sources": ["pacemorby"],
    "maxPosts": 30
  }'

The response is the dataset rows as a JSON array.

Start a run (asynchronous)

curl -X POST \
  "https://api.apify.com/v2/acts/unseenuser~facebook-posts-scraper/runs?token=<APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
    "mode": "profile",
    "sources": ["pacemorby"],
    "maxPosts": 30
  }'

You get a run object back. Poll GET /v2/actor-runs/<RUN_ID> for status, or use a webhook (see below).

Python (apify-client)

from apify_client import ApifyClient

client = ApifyClient("<APIFY_TOKEN>")
run = client.actor("unseenuser/facebook-posts-scraper").call(run_input={
    "mode": "profile",
    "sources": ["pacemorby"],
    "maxPosts": 30,
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["id"], item["reactionCount"], item["permalink"])

Node.js (apify-client)

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<APIFY_TOKEN>' });
const run = await client.actor('unseenuser/facebook-posts-scraper').call({
    mode: 'profile',
    sources: ['pacemorby'],
    maxPosts: 30,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
for (const item of items) console.log(item.id, item.reactionCount, item.permalink);

---

Scheduling and webhooks

• Schedules. Open this Actor's Schedules tab on Apify to run it on a cron, daily, weekly, or any custom interval. Pass the same input you would in a manual run. Combine with deduplication on id to build an always-fresh dataset.
• Webhooks. Configure a webhook on the Actor's Integrations tab to POST to your endpoint when a run finishes. The payload includes the run ID and default dataset ID so you can fetch results immediately.
• Run events. Subscribe to ACTOR.RUN.SUCCEEDED, ACTOR.RUN.FAILED, or ACTOR.RUN.ABORTED.

---

Integrations

This Actor's output drops straight into:

• Google Sheets via Apify's built-in integration - the flat row shape maps one-to-one to spreadsheet columns.
• Make (Integromat) and Zapier via the Apify modules.
• Airbyte and other ETL tools via the Apify dataset HTTP API.
• Postgres, BigQuery, Snowflake via JSONL export + COPY / load jobs.
• n8n, Pipedream, custom backends via webhooks.

Because the rows are flat, you do not need a JSON unwind / unnest step before loading.

---

Errors and reliability

• Retries: the Actor retries the underlying API with exponential backoff (1 s, 2 s, 4 s) on 429, 502, 503, and 504. Other 4xx and 5xx surface immediately.
• Per-source error isolation: an error fetching one source emits an error row in the dataset (with the error field) and the run continues with the next source. One bad URL does not crash a 50-source run.
• No partial post pushes: a row is either fully built (with the add-ons that were requested) or emitted as an error row. There are no half-formed rows.
• Status messages: when the free-plan cap is hit the run finishes SUCCEEDED and sets a runtime status message explaining the cap and how to remove it.

---

FAQ

Are pages, profiles, and groups all supported? Yes - choose with the mode input. Single posts and reels are also supported via single_post mode.

Does it search by keyword or hashtag? No. It extracts from known page, profile, group, or post URLs.

How many posts per run? Up to maxPosts per source (default 30). The Actor paginates automatically. Free Apify users are capped at 50 dataset rows total per run.

Are video URLs HD? Yes - both SD and HD video URLs are returned for every video post, plus a thumbnail.

How are comments and transcripts billed? Comment threads, comment replies, transcripts, and per-post deep enrich are billed add-ons - off by default. Empty transcripts are not billed.

Do you scrape group members? No, never. Group mode returns post content only.

Should I use a Page ID or a URL in profile mode? A numeric pageId is faster than a URL - the Actor uses it directly when you paste one in.

Can I pass mixed input? Yes - the Profiles, pages, groups or posts field accepts any mix of URLs, handles, @handles, and numeric IDs in the same run. Each entry is normalized based on the selected mode.

Why are some fields missing from my rows? Fields not populated by the API are dropped from the row to keep output clean. The enrichment-only fields (share count, view count, captions, music, etc.) appear when you enable enrichSinglePostFields=true or use single_post mode.

Why are some posts skipped in single_post mode? Bare numeric IDs and handles do not resolve to a single post. Provide the full post or reel URL.

Does this Actor handle private content? No. It runs from a logged-off public view - posts that require login, friends-only posts, and private groups are not accessible by design.

Is this legal? This Actor is a thin software wrapper that delegates the underlying data collection to a third-party API provider. Your downstream use of the data is your responsibility. Review the Master Terms of Service (V4.0) and the Actor-Specific Addendum below before commercial use.

Do I need a separate API account? No. The Publisher (UnseenUser) holds the credentials for the underlying API provider. You only need an Apify account.

What about Facebook's anti-scraping enforcement? Meta's Terms restrict automated extraction. The Third-Party API Provider operates the data collection infrastructure and bears responsibility for the lawfulness of its architecture. Your downstream use must independently comply with Meta's Terms.

What if Meta sends me a cease-and-desist? Cease the contested use immediately and notify UnseenUser within 48 hours via the Apify profile contact form at https://apify.com/UnseenUser. See Master ToS Section 5.3 for the full protocol.

What about minors? Facebook has a significant under-18 user population. This Actor's Terms strictly prohibit using data of users you know or suspect are minors. If content suggests a minor, treat the data as belonging to a minor by default. See Addendum Section M.

Can I use this data to train an AI model? No - that is prohibited by both Meta's Terms and this Actor's Terms of Service. See the Compliance section and Addendum Section K.

What is the difference between this Actor and the dedicated Comments / Groups / Reels scrapers? This is the flagship multi-mode actor. The dedicated scrapers are deeper specialists for specific endpoints. See Related scrapers.

---

Related scrapers

Build a full Facebook post-intelligence stack:

• Facebook Comments Scraper - deep comment threads + the feedback_id fast path
• Facebook Groups Scraper - dedicated group-posts listing
• Facebook Pages Scraper - the page behind the posts
• Facebook Reels Scraper - the page's video content

See all 27 scrapers by unseenuser ->

---

Compliance

• Public, logged-off view only. No login, no cookies, no member harvesting.
• Personal data may appear in outputs (post authors, commenters). You are the data controller for your downstream use; UnseenUser acts solely as a software vendor (processor framing in the Master ToS V4.0). You handle data-subject rights, lawful basis, and retention.
• Meta's Terms of Service prohibit automated extraction. Your downstream use of the data is your responsibility.
• Privacy policy: apify.com/UnseenUser (contact form for the Publisher) and Apify's own privacy notice at apify.com/privacy-policy.
• See the full Terms of Service and the Actor-Specific Addendum below for details.

---

Terms of Service - summary

By running this Actor you accept UnseenUser's Terms of Service V4.0 and the Actor-Specific Addendum (both reproduced in full below). Highlights:

• Architecture: This Actor is a thin software wrapper. UnseenUser does not store or retain the data the Actor returns.
• Your role: You are the data controller for the data you receive. Comply with Meta's Terms and applicable privacy law (GDPR, UK GDPR, CCPA, Israel PPL incl. Amendment 13).
• Group mode: Post content only. No member data, ever.
• Prohibited: AI / ML training without separate licensing, harassment or stalking, discrimination, spam, fraud, election interference, sensitive-targeting, processing of data of minors.
• Video URLs and music: Possession of an SD / HD URL is not a licence to rebroadcast. Music rights belong to the rights holders.
• Cease-and-desist: If Meta or a regulator contacts you about data obtained via this Actor, cease use immediately and notify UnseenUser within 48 hours via https://apify.com/UnseenUser.

---

Master Terms of Service - V4.0

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, by running the Actor through automated systems, or by 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 company that operates scraping infrastructure and returns data from source platforms. The provider's identity is confidential to the Publisher's commercial relationship.
• Source Platform: Meta / Facebook is the source platform for this Actor. Other Actors in the Publisher's catalog may target additional source platforms.

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, the Third-Party API Provider's Terms of Service, the Source Platform's terms, and applicable law in your jurisdiction and the jurisdictions of data subjects. These Terms incorporate the Actor-Specific Addendum below; where conflict arises, 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. It (a) accepts structured input from you on Apify, (b) translates that input into HTTP requests to a third-party API operated by the Third-Party API Provider, (c) receives HTTP responses from that third-party API, and (d) returns the response data to you in a structured format on Apify. 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 Third-Party API Provider; (c) a data storage or data retention service; (d) a licensed access channel to Meta, Facebook, 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 designing and writing the Actor's source code, publishing it on the Apify Store, maintaining it when API providers change schemas, and 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 Third-Party API Provider is an independent third-party company that (a) operates the actual data scraping infrastructure, (b) maintains relationships with source platforms (or accepts the operational risk of accessing public data without such relationships), (c) provides its own Terms of Service governing its operations, and (d) is responsible for compliance obligations relating to the data collection itself. The Publisher is a customer of the provider, not its agent, partner, or representative.

2. Who May Use the Actor

2.1 Eligibility. You may use the Actor only if you are at least 18 years old or the age of majority in your jurisdiction, have legal capacity to enter into binding contracts, are not located in or resident of a country subject to comprehensive sanctions by the United States, European Union, United Kingdom, or Israel, and are not on any prohibited persons list.

2.2 User Representations. By using the Actor, you represent and warrant that (a) information you provide about your identity and intended use is accurate; (b) your intended use complies with applicable law in your jurisdiction; (c) you will independently comply with the Terms of Service of any source platform whose data you obtain through the Actor; (d) where outputs include personal data, you will respect data subject rights under applicable law; and (e) 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, and building products that further process publicly available information lawfully. Specific permitted uses for this Actor are described in the Addendum below.

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, the 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 the 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 Third-Party API Provider. For this Actor, the Source Platform is Meta / Facebook.

5.2 Your Sole Responsibility. You acknowledge that (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; and (d) you should review Source Platform terms before commercial use - for Meta / Facebook, see https://www.facebook.com/legal/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 at https://apify.com/UnseenUser, (c) cooperate with the Publisher as needed to mitigate, and (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 Third-Party API Provider is the entity that collects data from source platforms; it bears the responsibilities of a data processor or controller (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 that (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 Apify, not 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), governed by Apify's own privacy practices; and (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; and (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, or 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 the Apify platform, the underlying API provider, and 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, your violation of these Terms, your violation of any law (including privacy law), your violation of any Source Platform's Terms of Service, or your processing of personal data obtained through the Actor; plus 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), or claims regarding the Third-Party API Provider's data collection (those are its 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 at 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 the 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 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 the 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 a third-party API; (c) you accept responsibility for your use, including compliance with Source Platform terms; (d) your indemnification obligations cover third-party claims arising from your use; (e) disputes are resolved in Israeli courts; and (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 at 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.

---

Actor-Specific Addendum - Facebook Posts 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. It accepts your input parameters, calls the relevant public-content endpoints of a third-party API provider (covering page / profile timelines, public group posts, single post / reel deep enrich, post comments, comment replies, and short-video transcripts), combines the results into a structured output, and returns the combined data to you on Apify. UnseenUser does not store, log, or substantively process the data returned. The data flows from the third-party API provider through Apify's runtime directly to you.

B. Nature of Data Returned

This Actor returns Facebook post data from pages, profiles, and public groups: post text, author, reaction and comment counts, top comments (including an inferred author gender), SD and HD video URLs and thumbnails, and timestamps. Add-ons return full comment threads, replies, short-video transcripts, and deep-enrich fields (share / view counts, captions, music).

Post text, author details, comments, and any people featured are 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.

C. Permitted Use Cases

You may use this Actor for the following purposes (non-exhaustive list):

• Brand and competitor monitoring - post output and engagement.
• Group social listening - public group post content (no member harvesting).
• Content research - what posts perform.
• Sentiment datasets - text + engagement for analysis.
• Engagement tracking - reactions, comment counts, top comments over time.
• AI pipelines - post text into your pipelines, subject to Section K below.

D. Specifically Prohibited Uses

In addition to Master ToS Section 4 prohibitions, you may NOT:

• Scrape, derive, or emit Facebook group member lists or any member data (post content only).
• Republish post text, video, or comments verbatim in commercial products without licensing.
• Train commercial AI / ML models on post content, video, or music without separate licensing authority.
• Rebroadcast or redistribute post videos using the SD / HD URLs in a way that infringes creator or music copyright.
• Use commenter data to power mass-DM / auto-message tools or build engagement-scoring databases for sale.
• Use sensitive post or comment content (health, religion, politics) to profile or target individuals.

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). This Actor accesses publicly visible post data via the Third-Party API Provider; the 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 at https://apify.com/UnseenUser and cease your use immediately.

F. Multi-Endpoint / Multi-Mode Data Sensitivity

This Actor can combine timeline / group posts with comments, replies, transcripts, and deep enrich in one run. The combination builds a rich record of a source's content and the people engaging with it - more sensitive than any single call. Use it thoughtfully: do not sell the combined dataset as a product, do not build a "Facebook replacement," and use it for your own monitoring and research.

G. Group Posts - No Member Harvesting

For group mode, this Actor returns post content only. You may NOT use it (or pair it with other tools) to collect, infer, or build lists of group members; the underlying API provider exposes no member endpoint. Group membership itself can reveal special-category data (a health-support group, a religious or political group, an LGBTQ group), so member harvesting is both prohibited here and a serious GDPR Article 9 risk. Treat "we never scrape members" as a hard rule.

H. Post and Comment Author Personal Data

Post authors and commenters are identified individuals. Comments and post text reveal opinions, interests, and sometimes special-category views. Establish and document a lawful basis, apply data minimization (store the signal, not the full text, where possible), and honor data subject rights. The inferred comment-author gender field is sensitive-adjacent - do not rely on its accuracy and do not use it for decisions about a person.

I. Video URLs - Capability, Not Authorization to Use

This Actor returns direct SD / HD video URLs from Facebook's CDN. Possession of these URLs does NOT grant you the right to rebroadcast, republish, or redistribute the video, to remove attribution, or any waiver of the creator's (or music rights holders') copyright. You receive the same stream a normal viewer would, just as a direct link. The underlying rights are unchanged.

J. Content Copyright - Post Text, Video, Music

Post content is multi-layered copyright: text and video are the creator's; any music is separately owned by music rights holders. You may analyze and quote short excerpts with attribution (typically fair use) and use aggregated metrics (counts - facts). You may NOT republish full content as your own, strip attribution, or use the content beyond analysis without explicit licensing. Music rights holders (Universal Music Group, Sony Music, Warner Music) enforce copyright more aggressively than any other category.

K. AI Training - Special Notice

Meta's Terms of Service prohibit using Facebook data to train AI / ML models without authorization. Post text, video, comments, and music are no exception, and "AI pipelines" is listed as a use case precisely because it is the highest-risk one. The Publisher (UnseenUser) does NOT authorize, and has no ability to authorize, AI training use. Recent litigation (NYT v. OpenAI, Andersen v. Stability AI, Sony v. Stability AI over music) shows AI training on platform and music content is heavily contested. Get proper licensing or do not train on this data. Your AI training use is your own legal exposure.

L. Sensitive-Content Patterns

Some posts and their comment threads are particularly sensitive: layoff announcements (commenters include affected employees), illness or bereavement disclosures (intimate personal information), and political or social controversies (protected-category views). Do NOT weaponize these: do not build "vulnerability lists" from inferred life events, do not use bereavement content for grief-targeting marketing, and do not use illness disclosures to identify candidates for medical products without explicit consent.

M. Minor Protection - CRITICAL

Facebook has a significant under-18 user population, and posts, commenters, and people featured may be minors. You MUST:

• NOT use this Actor to scrape posts, comments, or content 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 content or an author suggests a minor, treat the data as belonging to a minor by default. This restriction is non-negotiable, and creating or distributing sexualized content of minors is illegal everywhere and strictly prohibited.

N. Data Subject Rights and Cease-and-Desist Protocol

Authors, commenters, and people featured have rights under GDPR / CCPA / Israeli Privacy Law: access, deletion, objection (absolute for direct marketing under Article 21), rectification, and portability. Honor these with a typical 30-day SLA.

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 underlying 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.

---

Support

• Bugs and feature requests: open an issue via the Apify contact form on https://apify.com/UnseenUser.
• Questions: check the FAQ above first - most common questions are answered there.
• Status: Actor runs are observable in real time via Apify's run UI. While a run is in progress you can also hit the Actor's live-view endpoints (HTML status page, /status, /items?limit=20) for a programmatic snapshot.
• Response time: typical reply within 1 to 2 business days for non-urgent items.

---

Changelog

• 1.0 (current) - Initial public release. Profile, group, and single_post modes; concurrent fetching; flat output; free-plan cap with status message; live-view web server; full dataset, key-value store, and OpenAPI schemas.