👥 LinkedIn Groups Scraper — Get Group + Search + Posts (3-in-1, No Login)

The only LinkedIn Groups all-in-one scraper. Group profiles with admins, search by keyword, group post extraction. 2M+ groups untapped.

💡 Group members > generic search results — they self-select for niche interest, making them warmer leads.

LinkedIn Groups are the most underexploited B2B data source on the platform. 2M+ professional groups, niche industries gathered by topic, decision-makers concentrated in single-purpose communities — yet no other Apify actor covers all 3 group operations. This is your moat.

Built on a stable LinkedIn Group API (HarvestAPI) so you can scrape LinkedIn group data — group profiles, admin profiles, group posts, linkedin community data — without juggling cookies, captchas, or login sessions. A purpose-built professional networks scraper for niche B2B leads and B2B prospecting niche workflows.

---

⚡ Why This Actor?

• 3 modes in 1 — Group profile fetch, group search, group post extraction
• Admin profiles included — Group profile mode returns admin names, photos, headlines
• 2M+ groups accessible
• Niche-targeted intelligence — most professionals join 5-15 groups
• No login required
• Pay-per-result — only pay for what you actually fetch

---

🌟 Why Groups Matter

• 2M+ groups on LinkedIn — most professionals join between 5 and 15
• Niche audiences self-segmented by interest and industry
• Active groups have only 1-3% spam rate thanks to moderation
• Group admins = warm intro paths — they are influential community leaders

---

🎯 Use Cases

1. Community Intelligence — find groups in your niche, audit member counts and activity levels.
2. Targeted B2B Outreach — find decision-makers active in industry groups; warm intro paths via admins.
3. Content Distribution Research — discover which groups your competitors post in.
4. Group Admin Lead-Gen — admins are typically influential community leaders; pipe them into a profile-enrichment workflow.
5. Niche Market Sizing
6. Conference / Event Sourcing

🎯 Concrete example — RevOps

If you sell to RevOps leaders, scrape linkedin group members signals (admins + active posters) of the RevOps Co-op group instead of LinkedIn search for "RevOps" — 10x stronger signal. Self-selected community membership filters out the noise that a generic title search produces.

This same pattern works for any niche: "DevTools Founders Club" beats a search for "founder"; "FP&A Today" beats a search for "FP&A"; "PLG Collective" beats a search for "product-led growth".

---

🔗 Lead-Gen Pipeline

The Groups Scraper is the discovery layer of a 4-stage pipeline. Each stage hands off to the next:

┌──────────────────────┐    ┌────────────────────────┐    ┌──────────────────────┐    ┌──────────────────────┐
│  LinkedIn Groups     │ →  │  Profile Extractor     │ →  │  Email Enrichment    │ →  │  CRM / Outreach      │
│  Scraper (this Actor)│    │  & Enricher            │    │  (provider of choice)│    │  (HubSpot, Apollo,   │
│                      │    │                        │    │                      │    │   Salesforce, etc.)  │
│  • find groups       │    │  • full profile        │    │  • verified email    │    │  • sequenced send    │
│  • get admins        │    │  • work history        │    │  • deliverability    │    │  • reply detection   │
│  • surface posters   │    │  • skills, education   │    │                      │    │  • CRM sync          │
└──────────────────────┘    └────────────────────────┘    └──────────────────────┘    └──────────────────────┘

One workflow, four cheap layers — discovery is sub-cent per group, enrichment is per profile, email lookup is per profile, outreach is per send.

---

🚀 Quick Start

Mode: get_group — Group Profile + Admins

{
  "mode": "get_group",
  "groupInputs": [
    "https://www.linkedin.com/groups/1898033/",
    "1898033"
  ]
}

Mode: search_groups — Find Groups by Keyword

{
  "mode": "search_groups",
  "searchKeywords": "Sales Operations",
  "maxResults": 100
}

Mode: group_posts — Posts from Specific Groups

{
  "mode": "group_posts",
  "groups": ["1898033"],
  "postedLimit": "week",
  "sortBy": "relevance",
  "maxPostsPerGroup": 50
}

Mode: search_and_get — Search + Auto-Enrich Top Results

{
  "mode": "search_and_get",
  "searchKeywords": "fintech",
  "maxResults": 25
}

---

⚙️ Modes

Mode	Purpose
get_group	Full group profile + admins
search_groups	Find groups by keyword
group_posts	Posts from specific groups
search_and_get	Search + auto-enrich top results (combined)

---

🔄 Recommended Workflow

1. Search Groups by keyword (cheap discovery).
2. Get Group on each promising result (rich data, admin profiles).
3. For high-value groups, scrape posts (engagement signals).
4. (Optional) Pipe admin profiles to a Profile Extractor actor for full enrichment, or use a Sales Navigator actor to find members of specific groups.

---

🧪 Sample Output — Member-Like Profile List

Here's what you get from one Get Group call. Admins + active posters give you a real list of profile URLs you can hand straight to enrichment:

{
  "id": "1898033",
  "name": "Sales Best Practices",
  "linkedinUrl": "https://www.linkedin.com/groups/1898033/",
  "memberCount": 287430,
  "publicVisibility": true,
  "admins": {
    "totalCount": 6,
    "text": "Pat McAfee + 5 others",
    "profiles": [
      {
        "linkedinUrl": "https://www.linkedin.com/in/patmcafee",
        "firstName": "Pat",
        "lastName": "McAfee",
        "headline": "VP Revenue Operations · Acme Corp"
      },
      {
        "linkedinUrl": "https://www.linkedin.com/in/janedoe-revops",
        "firstName": "Jane",
        "lastName": "Doe",
        "headline": "Head of RevOps · Beta Inc"
      },
      {
        "linkedinUrl": "https://www.linkedin.com/in/john-smith-ops",
        "firstName": "John",
        "lastName": "Smith",
        "headline": "Director, Sales Operations · Gamma LLC"
      }
    ]
  }
}

Pair this with Group Posts mode and the post author.linkedinUrl field gives you another wave of high-engagement community members. Concatenate both lists, dedupe, and send to your enricher.

---

❓ FAQ

Q: Which groups are accessible? A: Any group whose listing page is publicly reachable on LinkedIn — that's effectively every group surfaced by LinkedIn's own search. Public groups return the richest payload (description, rules, hero image, full admin list, post stream). Closed/standard groups return the public-facing metadata that LinkedIn shows to non-members (name, summary, member count, admins, sometimes hero image).

Q: Can I get the full member list of a group? A: No. LinkedIn deliberately restricts member rosters even for joined members — no scraper, API, or login session can return them at scale. What the Actor does return is a usable proxy: (a) the group's admin profiles (always), (b) authors of group posts via group_posts mode, and (c) members surfaced in primary actions/featured profiles. In practice, admins + active posters cover the most-engaged 5-15% of any community — the slice that matters most for outreach.

Q: Public vs. private groups — what changes? A:

Field	Public group	Closed/standard group	Members-only group
Name, summary, member count	✅	✅	✅
Description / rules	✅	✅	partial
Logo / hero image	✅	✅	✅
Admin profiles	✅	✅	✅
Group posts (group_posts)	✅	partial	❌

Q: Member privacy considerations? A: Admin profiles and post-author profiles are personal data under GDPR / CCPA / Israel's PPL. Three rules of thumb:

1. Lawful basis: have one (legitimate interest with a balancing test, or contract). Cold B2B outreach in line with your jurisdiction's anti-spam law usually qualifies; mass marketing without consent does not.
2. Transparency: include a clear notice on first contact (where you got their info, why you're reaching out, how to opt out).
3. DSR-ready: be able to delete a person's record on request within statutory deadlines (GDPR: 1 month; CCPA: 45 days; Israel Amendment 13: 30 days). The full data-protection clause is in the Master ToS § 6 below — read it before pushing data into a CRM.

Q: GDPR — am I clear to use this for EU prospects? A: GDPR doesn't ban scraping public data, but it governs what you do next. Acceptable: time-limited research, account-based marketing with documented legitimate interest, journalism. Not acceptable: building a sellable database of EU contacts, mass-mailing without an opt-out, processing children's data, profiling on sensitive attributes (health, politics, religion). When in doubt, treat the LinkedIn URL as you would a phone number — public, but regulated in how you use it.

Q: What's the difference between numeric and alphanumeric group IDs? A: LinkedIn uses numeric group IDs in URLs (e.g. /groups/1898033/). Some legacy URN formats exist but the numeric ID is the canonical identifier. The Actor auto-detects both.

Q: Why do you use the post-search endpoint for group posts? A: Architectural quirk on the API provider side — group posts are exposed as a filter on the post-search endpoint rather than a dedicated /group-posts endpoint. The Actor handles this transparently.

Q: Is this Actor affiliated with LinkedIn? A: No. Not affiliated, endorsed, sponsored, or authorized by LinkedIn.

---

🛠️ Troubleshooting — Diagnostic Codes

The Actor never fails the run on a user-fixable issue. Instead, it writes a structured diagnostic item to the dataset and prints a banner in the log. Look for an item with _type: "diagnostic" — it contains code, message, and a fix field.

Code	What it means	What to do
MISSING_API_KEY	HARVEST_API_KEY env var isn't set	Apify Console → Source → Environment variables → add HARVEST_API_KEY (mark as Secret) from harvest-api.com
INVALID_API_KEY	HarvestAPI returned 401/403	Re-check or rotate the key in the same place
QUOTA_EXCEEDED	HarvestAPI returned 402 — out of credits	Top up at harvest-api.com/dashboard
RATE_LIMITED	429 even after retries	Lower maxResults/maxPostsPerGroup or upgrade your HarvestAPI plan
NOT_FOUND	404 — group is private or the ID is wrong	Verify the URL/ID is correct; private groups expose limited data
BAD_REQUEST	400/422 — input rejected upstream	Check the URL/ID format and the keywords
UPSTREAM_DOWN	HarvestAPI 5xx	Wait a few minutes and re-run
NETWORK_ERROR	Couldn't reach HarvestAPI	Re-run; persistent failures = networking issue
MISSING_INPUT_GROUP_INPUTS	Mode get_group selected, but groupInputs empty	Fill groupInputs, or switch to search_groups / search_and_get
MISSING_INPUT_SEARCH_KEYWORDS	Mode search_groups/search_and_get selected, but searchKeywords empty	Fill searchKeywords, or switch to get_group if you have URLs/IDs
MISSING_INPUT_GROUPS	Mode group_posts selected, but groups empty	Add URLs/IDs to groups
INVALID_MODE	mode field is not one of the four allowed values	Pick a valid mode from the dropdown
NO_RESULTS (warning)	Run was clean but returned 0 items	Try broader keywords or a longer time window
UNEXPECTED_ERROR	Likely a bug in the Actor	Report it on the Actor page with the run ID

Common "wrong mode" patterns the Actor will auto-detect and warn about:

• Mode = get_group but you filled searchKeywords → it suggests switching to search_groups or search_and_get.
• Mode = search_groups but you filled groupInputs → it suggests switching to get_group.
• Mode = group_posts but you filled groupInputs (the wrong field) → it tells you to use groups instead.

---

🔧 Technical Details

• LinkedIn Group API provider: HarvestAPI (https://api.harvest-api.com) — the linkedin group api that powers this Actor
• Endpoints used:
  • GET /linkedin/group — full group profile + admins
  • GET /linkedin/group-search — keyword search across the linkedin groups scraper index
  • GET /linkedin/post-search (with group filter) — group posts
• Authentication: X-API-Key header → environment variable HARVEST_API_KEY
• Retry policy: 3 retries with exponential backoff (1s / 2s / 4s) on transient failures
• Concurrency: search_and_get enriches results with concurrency 3 to avoid rate limits
• No login required: stateless calls, no LinkedIn cookies, no session juggling

---

📦 Output — Where Your Data Lives

The Actor writes to three Apify storages. You can browse all of them from the run page.

1. Dataset (one row per item)

The dataset has three pre-built views so you don't have to wrangle JSON:

View	Best for	Key columns
Groups — Overview	Browsing groups by size, public/private, summary	id, name, linkedinUrl, memberCount, members, publicVisibility, summary
Group Admins	Lead-gen — flattened admin profiles per group	admins.totalCount, admins.text, admins.profiles
Group Posts	Engagement / content research	groupId, groupName, author, content, linkedinUrl, engagement

Switch views using the View dropdown above the dataset table on the run page. Export any view as CSV / Excel / JSON / API endpoint.

The output schema itself (full JSON Schema for each item shape) is published at .actor/dataset_schema.json and is what powers the Output tab on the Apify Store listing — so callers know exactly what fields to expect, with types, descriptions, and labels, before they run the Actor. Three shapes are documented via oneOf:

Mode	Output shape	Documented in definitions.
get_group, search_and_get	Group	Group
search_groups	GroupShort	GroupShort
group_posts	PostShort	PostShort

2. Key-Value Store (run-level artifacts)

Three named collections — each is a single JSON record per run:

Key	What's inside
RUN_SUMMARY	{ mode, groupsRequested, groupsFetched, groupsSearched, postsScraped, errorsCount, durationSeconds, startedAt, finishedAt }
INPUT_SNAPSHOT	A copy of the input you ran with — for audit & reproducibility
ERRORS	List of structured error entries (only present if at least one error occurred)

Open them from Run page → Storage → Key-value store.

3. Live-view HTTP endpoints (while the Actor runs)

The Actor's container exposes a small read-only HTTP API at https://<runId>.runs.apify.net:

Method & path	Returns
GET /health	{ status: "ok", uptimeSeconds } — for uptime checks
GET /status	Live counters: mode, phase, groupsScraped, postsScraped
GET /summary	Final-or-partial summary (same shape as RUN_SUMMARY)

The full spec is published as OpenAPI v3 at .actor/openapi.json — Apify renders it in the Live view → API tab so you can try requests right from the browser.

---

🧱 Output — Object Schemas

get_group → full Group object

{
  "id": "1898033",
  "linkedinUrl": "https://www.linkedin.com/groups/1898033/",
  "name": "Sales Best Practices",
  "memberCount": 1234567,
  "logo": { "url": "...", "width": 200, "height": 200, "expiresAt": 1759999999 },
  "heroImage": { "url": "...", "width": 1400, "height": 425, "expiresAt": 1759999999 },
  "description": "...",
  "rules": "...",
  "createdAt": { "date": "2010-01-01T00:00:00Z", "timestamp": 1262304000 },
  "groupPlusStatusActive": false,
  "postApprovalEnabled": true,
  "invitationLevel": "members_only",
  "welcomeNote": "...",
  "automatedWelcomeNoteEnabled": true,
  "publicVisibility": true,
  "admins": {
    "totalCount": 6,
    "text": "Pat McAfee + 5 others",
    "profiles": [
      { "id": "...", "linkedinUrl": "...", "firstName": "Pat", "lastName": "McAfee", "headline": "...", "picture": "..." }
    ]
  },
  "scrapedAt": "2026-05-05T12:00:00.000Z"
}

search_groups → GroupShort

{
  "id": "1898033",
  "linkedinUrl": "https://www.linkedin.com/groups/1898033/",
  "name": "Sales Best Practices",
  "members": "1,234,567 members",
  "membersCount": 1234567,
  "summary": "...",
  "picture": "...",
  "primaryActions": [{ "label": "Join", "value": "..." }],
  "scrapedAt": "2026-05-05T12:00:00.000Z"
}

group_posts → PostShort

Same schema as company-posts / search-posts / user-posts. Each post is augmented with groupId, groupName, and scrapedAt.

---

🔗 Related scrapers

Complete the lead-gen pipeline:

• LinkedIn Profile Scraper + Email Enrichment — enrich the group members with verified emails
• LinkedIn Company Scraper Pro — research the companies they work at
• LinkedIn Post Search Scraper — find what topics they care about

See all 16 scrapers by unseenuser →

---

📜 Apify Actor — Terms of Service

Version: 4.0 Effective Date: May 5, 2026

---

0. ACCEPTANCE BY USE — IMPORTANT

Read this section first.

These Terms of Service ("Terms") form a binding legal agreement between you ("User," "you," "your") and UnseenUser, the Publisher of this Apify actor ("UnseenUser," "the Publisher," "we," "us," "our").

0.1 How You Accept These Terms

You accept these Terms by any of the following actions, each of which constitutes a clear, affirmative act of acceptance:

• (a) Running the Actor — Initiating any execution of the Actor on the Apify platform
• (b) Using any output returned by the Actor for any purpose
• (c) Continuing to access the Actor's listing or documentation after these Terms are visible

0.2 Continuing Acceptance

Each time you run the Actor or use its outputs, you reaffirm your acceptance of the then-current Terms. If you do not agree to these Terms or any subsequent update, you must stop using the Actor immediately.

0.3 No Anonymous Acceptance

You cannot disclaim acceptance by:

• Failing to read these Terms before running the Actor
• Running the Actor through automated systems
• Sharing your Apify account with others who may not have read these Terms

By the act of running the Actor on Apify, you bind yourself, your organization (if applicable), and any individuals or systems acting on your behalf or under your authority.

0.4 If You Do Not Accept

If you do not agree to these Terms, you must not run the Actor. No use is authorized without acceptance.

---

PREAMBLE — UNDERSTANDING THE ARCHITECTURE

Before using the Actor, please understand the technical architecture of the service:

The Data Flow

You (User) → Apify Platform → Actor (software) → Third-Party API → Source Platform
                                                        ↓
You (User) ← Apify Platform ← Actor (software) ← Third-Party API

What Each Party Does

• You (the User): Run the Actor on the Apify platform with input parameters you choose
• Apify: Operates the cloud infrastructure that hosts and executes Actors. Apify is a Czech-incorporated company (Apify Technologies s.r.o.) governed by its own Terms of Service.
• The Publisher (us): Publishes software code (the Actor) on Apify's platform. The Actor is a thin wrapper that translates your input into requests to a third-party API and returns the API's responses to you. The Publisher does not operate scraping infrastructure. The Publisher does not store or retain data returned by the Actor. The Publisher does not see, log, or process the personal data of any individuals returned in the Actor's outputs beyond what is incidental to passing the data through.
• Third-Party API Provider: 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 (סעיף 30א לחוק התקשורת), 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.

---

🛡️ Actor-Specific ToS Addendum — LinkedIn Groups Bundle

This addendum supplements the Master Terms of Service V4.0 above. 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 HarvestAPI's /linkedin/group, /linkedin/group-search, and /linkedin/post-search endpoints (with group filter), and returns the response data to you on the Apify platform. The Publisher does not store, log, or substantively process the data returned.

B. Nature of Data Returned

Group profile data (name, description, member count, logo, hero image, rules), admin profiles (names, photos, headlines), group search results, and group posts. Group admins are personal data subjects. Group post authors are personal data subjects.

C. Permitted Use Cases

• Community intelligence and niche audience research
• Identifying communities relevant to your B2B product
• Audit of communities you moderate or participate in
• Academic research on professional community dynamics
• Journalism on industry trends
• Content marketing strategy

D. Specifically Prohibited Uses

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

• Mass-cold-DM group admins based on their data extracted from this Actor
• Republish group posts in commercial products without authorization from authors
• Aggregate group-membership databases for marketing or discrimination
• Use group descriptions or rules to profile members for discriminatory decisions
• Spam groups based on intelligence gathered about them
• Identify group membership of individuals for political, religious, or sensitive characteristic profiling

E. LinkedIn Platform ToS Considerations

LinkedIn Groups are LinkedIn's most actively-moderated section. Group moderators may ban users they detect as scraping or automating. LinkedIn's User Agreement explicitly addresses Groups data. Some groups have explicit "no marketing" rules in their description — your downstream marketing use should respect these. If LinkedIn issues a cease-and-desist, notify the Publisher within 48 hours.

F. Group Admins as Personal Data Subjects

Treat admin profiles as personal data under GDPR/CCPA/Israeli law in your downstream processing. Cold outreach must comply with applicable anti-spam laws. Admin role is publicly visible context — using their admin status against them (harassment, discrimination) is prohibited.

G. Sensitive Group Categories

LinkedIn Groups exist for sensitive categories: health and disability support, LGBTQ+ professional networks, religious professional communities, political affiliation, recovery and addiction support. Do not target advertising based on sensitive group membership. Do not "out" individuals by linking their participation in sensitive groups to other identities.

H. Group Posts and Author Personal Data

Post authors are personal data subjects. Post content reflects their professional views and may include personal information shared in trust with the group. Republishing group posts outside the group context may violate authors' reasonable expectations even though the group is publicly searchable.