Facebook Profile Scraper (No Login)

Accurate follower and like counts - the field most Facebook scrapers get wrong. Scrape public Facebook profiles for name, bio, follower and like counts, profile URL, ID, profile pictures and any contact info that is publicly listed. No login. JSON / CSV / Excel.

Choosing the right Facebook scraper:

• Need a business page (email, phone, hours, ratings, ad status)? -> Facebook Pages Scraper
• Need a person / creator (bio, followers, pics, ID)? -> Facebook Profile Scraper (you are here)

This Actor never logs in, never uses cookies, never touches private or friends-only data. That is the clean line between this and cookie-based profile scrapers - and the safer compliance posture.

It enriches known profile URLs - it does not search for people by name or keyword. There is no name or keyword discovery; you bring the profile URLs.

---

Table of contents

• Why this Actor
• What you get
• Free plan limit
• Quick start
• Inputs
• Sample input
• Sample output
• Output field reference
• Posts add-on
• Use cases
• How it works
• Performance and limits
• Error handling
• Output formats and integrations
• Compliance and legal
• FAQ
• Changelog
• Support
• Terms of Service
• Actor-Specific Addendum
• Related scrapers

---

Why this Actor

• Reliable follower and like counts. The single field most Facebook scrapers mangle. This Actor surfaces them cleanly so you can vet creators and prospects without second-guessing the number.
• No login, no cookies, no impersonation. Public, logged-off data only. This is the safer compliance posture compared with cookie-based scrapers that masquerade as a logged-in user.
• Person-first output. The default Overview view foregrounds the fields you actually want for people research (name, follower / like counts, bio, picture, URL, ID), instead of burying them in business-page fields that are almost always empty on personal profiles.
• Single, atomic job. One input (profile URLs) maps to one output (one row per profile). No magic, no surprises in your bill.
• Predictable cost. The default run is one structured row per profile URL you supply. The optional posts add-on is only used when you ask for it, so you can keep the cost surface minimal.
• Production-grade defaults. Per-URL error isolation, automatic retries with exponential backoff on transient failures, schema-driven Console rendering, OpenAPI-described live status view.

What you get

For every public profile URL you supply, one structured row in the Apify dataset:

• Identity: display name, stable numeric Facebook ID, canonical profile URL
• Audience: follower count, like count
• Bio: short intro / bio text (pageIntro)
• Pictures: small, medium, and large profile pictures plus the cover photo and profile photo objects
• Contact (if publicly listed): email, website, external links
• Inferred gender (treat as low confidence; do not use for decisions about a person)
• Optional posts timeline when includePosts is enabled
• Raw object preserving every field the source returned, including business fields that are usually empty on personal profiles
• _metadata block with the fetch timestamp, the originally requested URL, and a count of posts pulled

The default Overview view is rendered as a Console table that leads with the profile picture, name, follower / like counts and bio. JSON / CSV / XLSX downloads include every field.

---

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.

---

Quick start

1. Click Try for free on this Actor's Apify page.
2. Paste one or more public Facebook profile URLs into Profile URLs (for example https://www.facebook.com/zuck).
3. Leave Include public posts off unless you also want the recent post timeline.
4. Click Start.
5. When the run finishes, open the Output tab to browse results, or download as JSON / CSV / XLSX, or pull them via the Apify API.

The Actor accepts batches: drop in 1 URL or hundreds, it processes them sequentially with per-URL error isolation so one bad URL never sinks the whole run.

---

Inputs

Input	Type	Required	Default	Description
startUrls	array of strings	Yes	-	One or more public Facebook profile URLs. URLs must point to facebook.com (or fb.com).
includePosts	boolean	No	false	When true, also fetch the profile's recent public post timeline.
maxPosts	integer	No	9	Upper bound on posts pulled per profile when posts are enabled. Minimum 3, maximum 1000.

Sample input

{
    "startUrls": [
        "https://www.facebook.com/zuck",
        "https://www.facebook.com/finkd"
    ],
    "includePosts": false,
    "maxPosts": 9
}

Input notes

• One URL per row. Each entry in startUrls produces one dataset row (plus posts, if enabled).
• URLs only. This Actor enriches URLs; it does not search. If you have a name, look up the profile on Facebook first and copy the URL.
• Vanity or numeric. Both facebook.com/zuck and facebook.com/profile.php?id=... URLs are accepted.
• Invalid URLs become error rows, not crashes. The rest of the batch still completes.

---

Sample output

A successful row for a creator / public figure looks like this:

{
    "name": "Mark Zuckerberg",
    "id": "100088017857524",
    "url": "https://www.facebook.com/zuck",
    "pageIntro": "Founder and CEO at Meta.",
    "followerCount": 119000000,
    "likeCount": 119000000,
    "gender": "MALE",
    "profilePicLarge": "https://scontent-.../s200x200/....jpg",
    "profilePicMedium": "https://scontent-.../s148x148/....jpg",
    "profilePicSmall": "https://scontent-.../s100x100/....jpg",
    "coverPhoto": {
        "photo": {
            "image": { "uri": "https://...jpg", "width": 960, "height": 365 }
        }
    },
    "profilePhoto": {
        "id": "...",
        "url": "https://www.facebook.com/photo/?fbid=..."
    },
    "email": null,
    "website": null,
    "links": [],
    "category": null,
    "creationDate": null,
    "raw": { "...": "every field as returned upstream" },
    "_metadata": {
        "fetched_at": "2026-06-03T12:00:00.000Z",
        "profile_url": "https://www.facebook.com/zuck",
        "posts_fetched": 0
    }
}

A failed row (bad URL, profile not found, transient upstream error after retries) looks like this:

{
    "error": "Not a Facebook URL: https://example.com/not-a-profile",
    "_metadata": {
        "fetched_at": "2026-06-03T12:00:00.000Z",
        "profile_url": "https://example.com/not-a-profile",
        "posts_fetched": 0
    }
}

Error rows let you reconcile inputs to outputs and retry only what failed, without re-running the whole batch.

Output field reference

Field	Type	Description
name	string | null	Public display name
id	string | null	Stable numeric Facebook profile ID. Useful as a permanent key when the vanity URL changes.
url	string | null	Canonical public profile URL
pageIntro	string | null	Short bio / intro text shown on the profile
followerCount	number | null	Number of followers
likeCount	number | null	Number of likes
gender	string | null	Inferred gender, typically MALE, FEMALE, or UNKNOWN. Low confidence; do not use for decisions about a person.
profilePicLarge	string | null	URL of the largest available profile picture
profilePicMedium	string | null	URL of the medium profile picture
profilePicSmall	string | null	URL of the small profile picture
coverPhoto	object | null	Cover photo with image URI and dimensions, when present
profilePhoto	object | null	Profile photo permalink, when present
email	string | null	Publicly listed email, if any. Usually null on personal profiles.
website	string | null	Publicly listed website, if any
links	array	Publicly listed external links
category	string | null	Profile category. Usually null on personal profiles.
creationDate	string | null	Profile creation date when available. Usually null on personal profiles.
posts	array	Recent public posts. Present only when includePosts is true.
raw	object	The full unmodified upstream profile object, including business fields that are usually empty on personal profiles.
error	string	Present only on rows where a single profile URL failed. Other rows are unaffected.
_metadata	object	{ fetched_at, profile_url, posts_fetched } for traceability.

---

Posts add-on

Set includePosts: true to also fetch the profile's recent public post timeline (text, author, engagement counts, video details, top comments).

• Optional and gated. When includePosts is false (the default), no posts work is done.
• Limited by maxPosts. Default 9, minimum 3, maximum 1000. The Actor stops as soon as the limit is reached.
• Paginated. The Actor walks pages automatically and stops on the first empty page, short page, or stagnant cursor.
• Robust. A posts failure is logged but does not lose the profile row; the profile result is still pushed and the row's _metadata.posts_fetched will reflect what was actually retrieved (zero on failure).

Each post object includes (when present upstream) id, text, url, permalink, author, reactionCount, commentCount, videoViewCount, publishTime, videoDetails, and topComments[].

---

Use cases

• People prospecting. Turn a list of known profile URLs into structured contact and audience data, then route the rows into your CRM with the right consent metadata.
• Creator and influencer vetting. Verify follower / like counts on prospective partners before sending an offer, instead of trusting screenshots.
• Audience research. Profile a defined set of public accounts (newsroom subjects, panelists, conference speakers, podcast guests) into a clean dataset.
• Profile-to-ID resolution. Resolve a vanity URL to a stable numeric Facebook ID so your downstream system has a permanent key even if the vanity changes.
• CRM enrichment. Fill in name, bio, follower count, and picture for accounts you already track by URL.
• Content research. With the posts add-on, pull the recent public post timeline for a small set of profiles for editorial or competitive context.
• Journalism and investigative reporting. Snapshot public profile state at a given moment for stories that require auditable, time-stamped public data.

---

How it works

• Input: one or more public Facebook profile URLs.
• Pipeline: for each URL the Actor validates the URL, fetches profile data, and pushes a structured row to the dataset.
• Posts add-on: when enabled, the Actor walks the profile's recent post pages and attaches them to the row, stopping at maxPosts or when the upstream cursor exhausts.
• Default view: the Apify Console renders the dataset with a person-first Overview view (picture, name, followers, likes, bio, URL).
• Live view: while a run is active, the Actor's container exposes a read-only GET / status endpoint and a GET /health probe, both described by the Actor's OpenAPI schema.
• Run summary: at run end the Actor writes a output-run-summary record to the key-value store with the request count, processed count, returned count, cap status, and a human note when the cap was hit.

Performance and limits

• Throughput. Profiles are processed sequentially with per-URL error isolation. A typical profile call completes in a fraction of a second; large batches scale roughly linearly.
• Retries. Transient failures (HTTP 429, 502, 503, 504, network errors) are retried up to 3 times with exponential backoff (1s / 2s / 4s) before the row is marked as an error.
• Posts pagination. Bounded by maxPosts (default 9, max 1000) and terminates on empty pages, short pages, or stagnant cursors so a misbehaving upstream cannot loop indefinitely.
• Memory. Streams results into the dataset as they are produced; memory does not grow with batch size.
• Run cap (free plan only). 50 dataset rows per run. Upgrade any paid Apify plan to remove. Paying users are unaffected.

Error handling

• Per-URL isolation. A bad URL in your batch produces a single error row, not a failed run. The rest of the batch continues normally.
• Validation errors. Empty entries and non-Facebook URLs produce an error row with a descriptive error field.
• Posts-only failures. If the posts add-on fails after the profile call has already succeeded, the profile row is still pushed and posts_fetched reflects what was actually retrieved.
• Run-level errors. Missing required configuration (such as the upstream API key not being set by the Actor operator) causes a clean FAILED status with a readable status message, not a stack trace.
• Cap reach. Reaching the free plan cap is not an error; the run finishes SUCCEEDED with the developer-attributed status message explaining the cap.

Output formats and integrations

• Apify Console. Browse the dataset as a table (Overview view), inspect individual records as JSON, and download the whole dataset.
• Downloads. JSON, CSV, XLSX, JSONL, RSS, HTML, and XML are all available from the Dataset tab.
• Apify API. Fetch the dataset programmatically with GET https://api.apify.com/v2/datasets/{datasetId}/items. Use the format=csv (or xlsx, json, jsonl) query parameter to download in your preferred shape. Use view=overview to apply the person-first column projection.
• Webhooks. Configure a webhook on the Actor to push results into Make, Zapier, n8n, a Google Sheet, an Airtable base, or a custom endpoint when the run finishes.
• Scheduling. Use Apify schedules to refresh a watchlist of profiles on a recurring cadence.
• Composability. Chain this Actor's output into other Actors (for example, a CRM-loader Actor, an enrichment Actor, or a notification Actor) with Apify Tasks and Webhooks.

---

Compliance and legal

By running this Actor you accept its Terms of Service. Highlights:

• Public, logged-off data only. The Actor never authenticates and never sends cookies. Do not extend it to attempt private or friends-only data; doing so changes the legal posture entirely.
• No social-graph harvesting. This Actor returns a single profile's public details, not its friend list, follower list, or connections.
• Personal data. A personal Facebook profile is personal data of an identified individual under GDPR, UK GDPR, CCPA, and Israel's Privacy Protection Law (including Amendment 13). You are the data controller for any downstream processing.
• Lawful basis. Establish a documented lawful basis before processing (typically legitimate interest with a completed Article 6(1)(f) balancing test, or consent).
• Data subject rights. Build operational processes to honor access, deletion, objection, rectification, and portability requests with a typical 30-day SLA.
• Anti-spam. Comply with GDPR, CAN-SPAM, CASL, Israeli Anti-Spam Law, and equivalents before any outreach. Cold marketing without proper consent infrastructure is prohibited.
• Minors. Do not scrape or process data of users you know or suspect are minors. If a profile suggests an under-18 subject (school references, age-related content), treat it as a minor and delete unless you have valid parental consent.
• No AI training. Meta's Terms prohibit AI training on Facebook data, and the Actor's Terms strictly forbid it.
• No discrimination. Do not use the inferred gender field for employment, lending, housing, or insurance decisions.
• Cease-and-desist. If you receive a legal demand from Meta about data obtained via this Actor, cease the contested use, notify UnseenUser within 48 hours via the Apify profile contact form, and cooperate as needed.

The full Terms of Service V4.0 and the Actor-Specific Addendum are part of the listing and govern your use.

---

FAQ

Q: How is this different from your Facebook Pages Scraper? A: Different emphasis. The Pages Scraper foregrounds business contact and ad fields (email, phone, hours, ad library, ratings). This Profile Scraper foregrounds person fields (name, bio, followers, pictures) and is the right tool for people and creator research.

Q: Can it find people by name or keyword? A: No. It enriches known profile URLs; it does not search or discover profiles from a name or keyword. Look the person up on Facebook first and feed the URL.

Q: Does it work on private or friends-only profiles? A: No, by design. The Actor never authenticates and only reads public, logged-off data.

Q: How reliable are the follower and like counts? A: This is the field most Facebook scrapers get wrong. The Actor surfaces the counts cleanly, without mangling - that is the point of this listing.

Q: Why are address, phone, and business hours empty? A: Those are business-page fields. Personal profiles typically return null for them. They are preserved in the raw object so nothing is lost.

Q: Does the URL need a specific format? A: Both vanity (facebook.com/zuck) and numeric (facebook.com/profile.php?id=...) URLs are accepted, as long as the host is facebook.com or fb.com.

Q: What happens if one URL in my batch is bad? A: That URL becomes an error row; the rest of the batch completes normally. You can filter on error to reconcile what worked and what didn't.

Q: How long does a run take? A: A single profile typically completes in a fraction of a second. Batches scale roughly linearly; transient retries can extend a row's time by a few seconds.

Q: Does the cover photo URL stay valid forever? A: No. Facebook image URLs are signed and expire after some time. Download or cache the bytes if you need long-term access.

Q: Can I schedule this Actor? A: Yes. Use the Apify schedule feature to refresh a watchlist of profiles on any cadence you need.

Q: Can I trigger this from Make / Zapier / n8n / my own backend? A: Yes, via the Apify API. You can also configure a webhook on the Actor so finished runs push results into your downstream system automatically.

Q: Can I use this data to train AI? A: No. Meta's Terms prohibit AI training on Facebook data, and the Actor's Terms strictly forbid it.

Q: What about minors? A: You must not scrape or process data of users you know or suspect are minors. See the Compliance section above and the full Terms of Service for details.

Q: How do I report a bug or request a field? A: Use the Apify profile contact form at https://apify.com/UnseenUser.

---

Changelog

• 1.0 (May 2026) - Initial public release. Person-first Overview view, optional posts add-on, per-URL error isolation, free-plan cap of 50 results, OpenAPI-described live status view, dataset / output / key-value-store schemas.

Support

Use the Apify profile contact form at https://apify.com/UnseenUser for bug reports, schema requests, and legal correspondence. Include a sample input URL where applicable.

---

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: HarvestAPI (https://harvest-api.com) or Scrape Creators (https://scrapecreators.com). These are independent third-party companies that operate scraping infrastructure and return 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 Providers.

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)
• HarvestAPI Terms of Service and Scrape Creators 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 a third-party API operated by HarvestAPI or Scrape Creators
• (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 HarvestAPI / Scrape Creators
• (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 Providers' Role

HarvestAPI (https://harvest-api.com) and Scrape Creators (https://scrapecreators.com) are independent third-party companies. 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) Are themselves Apify publishers (HarvestAPI publishes 9+ actors directly; Scrape Creators publishes 10+)
• (d) Provide their own Terms of Service governing their operations
• (e) Are responsible for compliance obligations relating to the data collection itself

The Publisher is a customer of these providers. 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 Third-Party API Providers (HarvestAPI / Scrape Creators). 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 Providers, not the Publisher, bear 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
• HarvestAPI and Scrape Creators are the entities that collect 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) Underlying API providers (HarvestAPI, Scrape Creators)
• (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 Third-Party API Providers, or actions by Apify.

15.5 Third-Party Beneficiaries

Apify, HarvestAPI, and Scrape Creators 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 Addendum

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 Scrape Creators /v1/facebook/profile endpoint for each profile (and, only when you enable it, the /v1/facebook/profile/posts add-on endpoint), and returns the response data to you on the Apify platform. UnseenUser does not store, log, or substantively process the data returned. The data flows from Scrape Creators through Apify's runtime directly to you.

B. Nature of Data Returned

This Actor returns public Facebook profile data: name, profile ID and URL, bio/intro, inferred gender, follower and like counts, profile and cover pictures, and any publicly listed email, website or links. When the posts add-on is enabled it also returns the profile's public post timeline (text, author, engagement counts, video details, top comments).

A personal Facebook profile is, by definition, the personal data of an identified individual. Where the Actor's output includes a person's name, photos, contact details, or content authored by them, that data is 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. Profiles are higher-sensitivity than business pages precisely because they describe individuals.

C. Permitted Use Cases

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

• People prospecting - turn known profile URLs into structured data with a lawful basis
• Creator and influencer research - vet follower counts and bios
• Audience research - profile a defined set of public accounts
• Profile-to-ID resolution - resolve a URL to a stable Facebook ID
• CRM enrichment - fill in name, bio and audience fields for known accounts
• Content research - optionally pull a profile's public post timeline

D. Specifically Prohibited Uses

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

• Mass cold-DM or cold-email individuals without anti-spam compliance (GDPR, CAN-SPAM, CASL, Israeli Anti-Spam Law)
• Build or sell a "people search" website or profile-list product without consent infrastructure and transparency notices
• Authenticate, use cookies, or otherwise attempt to access private or friends-only profile data
• Harvest friend lists, connections, or social graph relationships
• Use the inferred gender field (or any inference) to make employment, lending, housing or insurance decisions
• Aggregate profiles across many individuals into a comprehensive identity database
• Train commercial AI/ML models on profile content or posts without separate licensing authority

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 profile data via Scrape Creators - Scrape Creators 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. Public Profiles Only - The Line vs Cookie-Based Scrapers

This Actor reads only public, logged-off profile data. It never authenticates as a user, never sends session cookies, and never attempts private or friends-only data. This is both a product differentiator and a compliance line: cookie-based scrapers that impersonate a logged-in user take on materially greater legal and platform-enforcement risk. Do not attempt to extend this Actor's output with authenticated access - doing so changes the legal posture entirely and breaches Master ToS Section 4.6.

G. Personal Profiles Are Personal Data - Heightened Care

Because every output here describes an individual, treat the full record as personal data:

• Establish and document a lawful basis before processing (typically legitimate interest with a completed balancing test, or consent)
• Apply data minimization (GDPR Article 5(1)(c)) - store only the fields you actually need
• Set retention limits; do not retain profile records indefinitely
• The inferred gender field is sensitive-adjacent - do not rely on its accuracy and do not use it for decisions about a person

H. No Friend-List or Connection Harvesting

This Actor returns a single profile's public details, not its social graph. You may NOT use it (or pair it with other tools) to map who a person is connected to, build friend/follower networks of named individuals, or reconstruct relationship graphs. That pattern is surveillance, multiplies privacy risk, and is the kind of dataset Meta specifically targets in litigation.

I. Prospecting Compliance

If you use this Actor for people prospecting or outreach:

• Establish a documented lawful basis and complete the GDPR Article 6(1)(f) balancing test (would the individual reasonably expect their public profile to enable your outreach?)
• Honor the right to object under GDPR Article 21 (absolute for direct marketing)
• Comply with GDPR, CCPA, Israeli Anti-Spam Law (prior consent for marketing in Israel), CAN-SPAM, CASL and equivalents
• Issue Article 14 transparency notices when collecting personal data from a source other than the data subject
• Disclose, when asked, how you found the person

J. The Data Broker Question

Profile data across MANY individuals IS a data broker asset. California's data broker registration requirements (effective 2024+) apply if you collect personal data from a source that is not the consumer and sell or share it. Building or selling profile lists also triggers GDPR Article 14, the California Delete Act (effective 2026), and Israeli Privacy Law Amendment 13 (statutory damages of NIS 10,000 per data subject without proof of harm). If your business model includes selling profile lists or derived insights, consult an attorney about data broker registration.

K. AI Training - Special Notice

Meta's Terms of Service prohibit using Facebook data to train AI/ML models without authorization. Profile content and posts are no exception. The Publisher (UnseenUser) does NOT authorize, and has no ability to authorize, AI training use. Recent litigation (NYT v. OpenAI, Andersen v. Stability AI, multiple class actions) shows AI training on platform data is contested. Get proper licensing or do not train on this data. Your AI training use is your own legal exposure.

L. Minor Protection - CRITICAL

Facebook has a significant under-18 user population, and personal profiles may belong to minors. You MUST:

• NOT use this Actor to scrape profiles 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 profile's metadata or content suggests the subject is under 18 (school references, age-related content), treat it as belonging to a minor by default. This restriction is non-negotiable.

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

Individuals whose profile 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, Scrape Creators, 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.

---

Related scrapers

Complete the people-research stack:

• Facebook Pages Scraper - the business-page sibling (email, phone, ad status)
• Facebook Comments Scraper - see what a profile says on others' posts
• Instagram Profile Scraper - the same person on Instagram

See all 21 scrapers by unseenuser ->

---

Keywords: facebook profile scraper, scrape facebook profile, facebook follower count, facebook profile data, facebook profile to json, facebook creator research, facebook people prospecting, facebook profile id lookup, facebook bio scraper