Welcome to Collective2

Follow these tips for a better experience

Ok, let's start

Close
Add to Watch List Create new Watch List
Add
Enter a name for your Watch List.
Watch List name must be less than 60 characters.
You have reached the maximum number of custom Watch Lists.
You have reached the maximum number of strategies in this Watch List.
Strategy added to Watch List. Go to Watch List

Sim is unavailable for this strategy, because you've recently "Simmed" it.

You already have a live, full-featured subscription to this strategy.

Okay, no problem

Reach out to us when you are ready. You can schedule your free training session at any time by clicking the button.

Remember, this training is free, low pressure, and (we hope!) fun.

Got it

Later

You can find it here.

Got it

Video Saved for Later

You can watch this video later. Just click this button at the top of the screen whenever you're ready to watch it.

Got it

How we work with security researchers

We try to engage with helpful researchers, penetration testers, and security professionals. We take security reports seriously. We fix what you find quickly. We pay modest, discretionary rewards for reports that matter. We're a small company, and our bounties are limited, but we'd like to grow our bounty program and increase our rewards as our company grows. Here's how it works.

How to report

Email [email protected] with a subject line that starts with "Security:". Include the steps to reproduce, the raw requests and responses, and the pages or endpoints involved. We read every report and will acknowledge yours, usually within a few business days.

Rules of engagement

  • Test only against accounts you own.
  • Don't access, change or keep other customers' data. If you stumble into doing so, stop and tell us.
  • Don't run scans or tests that degrade service for other people.
  • Don't publish details of an issue before we've fixed it.
  • Stop at proof. You don't need to complete a payment, or execute a transaction to show us a problem.

Rewards

Rewards are discretionary and modest. We set the amount after the issue is confirmed and fixed, based on an evolving rubric which measures real impact to customers and to the platform. We don't quote amounts or ranges before a report, and the amount we offer is final. The first complete report of an issue earns the reward; later reports of the same issue, and reports that split one issue into several, earn nothing extra. (i.e. Please don't split a report about a single vulnerability into multiple reports describing different potential impacts, etc., in an attempt to earn multiple bounties.)

Getting paid

To receive a reward, sign in or create a Collective2 account using the same email address you use for your support tickets. Verify that email, accept the researcher terms, save your PayPal or Payoneer payment email, and complete identity verification through Veriff. We match your tickets automatically. Each ticket is evaluated and paid separately.