Marketplace Terms

1. The two paths

The marketplace has a buyer path and a contributor path. A buyer describes an audience, reviews an editable typed plan, approves a bounded quantity and maximum price, and receives fresh, deduplicated People or standalone Account records as they settle. A contributor opts in through the Chrome extension, uses a Sales Navigator tab to apply the typed search and capture assigned records, and can earn internal credits for accepted work. One app account can use both paths.

Results are not a promise of verified email addresses, phone numbers, employment, availability, accuracy, or a particular delivery time. “All” means the approved cap or exhaustion of the bounded launch cohort's search sweeps. It never means every LinkedIn member.

2. Buyer approval, price, and Checkout

• The Assistant turns natural-language audience text into a typed People or standalone Account search plan. It must show approximations and missing inputs. A typed filter or browser readback mismatch stops the order.
• Before approval, we show result type, explicit cap, maximum charge, eligible node count, preliminary lead estimate, and the filter summary. A quote remains valid for 15 minutes. Queued orders are not periodically re-verified.
• Checkout does not require an extension. A buyer does not need LinkedIn, Sales Navigator, or the Chrome extension to approve an order or complete Stripe-hosted Checkout. Contributors need Sales Navigator and the extension to do browser-local capture work.
• People orders reserve five times the approved lead cap and charge 5 credits per accepted unique lead. Standalone Account orders reserve two times the approved Account cap and charge 2 credits per accepted unique Account. An accepted record is charged once; an export of a record already bought in that order does not create a second marketplace delivery charge.
• Cancellation stops new leases. Accepted results and valid in-flight results settle, and the unused hold releases exactly once. A failed Account enrichment does not invalidate its lead; after two attempts coverage is settled as inaccessible or unresolvable.

3. Employment Account capture

A captured Person can reference current and past employment Accounts in its captured employment history. The marketplace may make one shared Account capture per order and attach its coverage to matching leads. Account capture and reward are separate from the lead: an Account failure does not cancel the accepted lead. We do not promise that an employment Account is accessible, current, or resolvable.

4. Credits and contributor rewards

• The contributor onboarding/node flow issues the one-time 100-credit signup grant lazily when an eligible contributor node is first started or subsequently read; the grant does not expire. Plan sizes are 2,500 credits for Solo, 7,500 for Growth, and 20,000 for Scale.
• During the network bootstrapping stage, an opted-in node may receive streamed credits only while it is demonstrably online: 10 credits per hour in 6-minute ticks, capped at 200 credits per UTC day. Streamed credits do not expire. Time that cannot be proved online does not accrue, and the stream may end with advance notice.
• Accepted contributor work may receive earned credits when the server accepts the bounded result under the reward rules. Earned credits do not expire. Rewards are conditional on accepted, valid work and do not promise a particular amount for a page, sweep, or capture.
• Signup, streamed, and earned credits are internal, non-cash, non-transferable, non-resalable, and non-redeemable account balances. They are not wages, payment instruments, equity, or a promise of withdrawal. A credit source's eligibility is determined by the product surface that grants or uses it; these Terms do not state a product-wide spend order or promise that a signup grant funds a Marketplace order.
• For a People order, the platform may award a contributor 1 platform-funded credit for an accepted lead and 1 for each successfully captured unique employment Account. For a standalone Account order, it may award 1 platform-funded credit per accepted unique Account.
• A captain may receive 1 credit for an accepted server-issued search verification request. A node may receive 1 page-discovery credit only when its valid page introduces a candidate that is ultimately delivered. A valid duplicate across search segments may still earn a contributor reward, but the buyer is never charged twice for the same canonical record.
• If the buyer and contributor are the same app account, accepted work can count toward delivery but every contributor reward is zero. Rewards require accepted, valid work; there is no promise that a page, sweep, or capture earns a particular amount.

5. Contributor participation and browser custody

A contributor opts in, binds the app account and extension installation, and supplies only the bounded LinkedIn identity observation allowed by the extension. Contributor node states are Off, Ready, Working, Stopping after current page, Paused, and Offline. The active task shows progress, expected reward, and stop-after-page; it does not show the buyer's identity or prompt. The extension uses one dedicated Sales Navigator window. Keep Sales Navigator selected in its own visible window while earning. Do not minimize the window or hide the tab. You can use other windows normally. The extension must not disturb unrelated tabs.

All LinkedIn navigation, DOM parsing, extraction, retries, and local backups happen in the extension. Prospector does not fetch LinkedIn. No LinkedIn credentials, cookies, authenticated HTML, MHTML, raw page snapshot, or browser session reaches Prospector. The extension submits bounded parsed records and client metadata using a Prospector application bearer token; that bearer is application authentication, not a LinkedIn credential. The Privacy Notice explains the data and retention details.

6. LinkedIn automation risk

Ubiquity Prospector is independent from LinkedIn and is not LinkedIn-approved. LinkedIn's rules may prohibit third-party browser extensions that capture, change, or automate LinkedIn. Automation can lead to warnings, challenges, temporary restriction, permanent account restriction, loss of access, or other action by LinkedIn. You are responsible for deciding whether to participate and for complying with LinkedIn's terms and applicable law. We do not promise that a LinkedIn account will remain available or that selectors will remain compatible.

The extension pauses on login or access loss, warnings, challenges, selector failure, incompatible builds, or unsafe browser state. Do not bypass a challenge, CAPTCHA, identity check, or account restriction. We do not use anti-detection behaviour. See LinkedIn prohibited software and account restriction guidance.

7. Payments, cancellation, and acceptable use

Stripe-hosted Checkout processes a buyer payment and existing webhook settlement rules apply. Do not submit a payment for another person without authority. A refund, dispute, reversal, or fraud warning can freeze an account, set aside unused credits, and require support review. Do not use the service to violate law, third-party rights, LinkedIn access controls, privacy obligations, or contractual restrictions; collect sensitive data without a lawful basis; impersonate a person; or interfere with the service.

8. Privacy and changes

The Marketplace Privacy Notice describes platform-wide Example results, raw prompts and answers, exact server-observed IP addresses, security fingerprints, observational clusters, and the 13-month retention period. We may update these Terms as the prototype or legal requirements change and will update the effective date.