Decisions and disputes

Who decides what, by when, and what if you disagree.

Exploity never receives a report, so we do not judge whether a bug is real. Here is what we do judge, the dates a company works to, and what happens when the two sides disagree.

Deadlines

A date for every step.

Both sides see the next step and its date in the app. The clock stops while a request is waiting for our team.

StepWhoTime allowed
Open the reportCompany3 days after it is sent
Decide whether the finding is validCompany10 days after opening it
Propose the bountyCompany5 days after deciding
Pay the bountyCompany7 days after we approve it

If a date passes, the company gets a reminder and our team is told. We talk to the company first. A company that needs more time can simply say so in the conversation.

A researcher's deadline cannot be extended. If time runs out, the job goes to another researcher and counts against their completion rate, so accept an offer only if you can finish it.

Payment

Who promises the bounty?

The bounty is the company's promise, made in its own published table before the researcher accepts. It is not a promise by Exploity, and we cannot pay a bounty a company has not paid us.

The $50 from Exploity is ours, and is added when the company's bounty is $250 or more and has been paid.

  • The table is fixed. A company cannot change what a level pays after a researcher has accepted the job.
  • No paying under the table. We do not approve a bounty below the lowest amount the company published for the level it chose.
  • Unpaid means paused. A company with an approved bounty past its payment date cannot request new tests until it pays.
  • On the record. How a company treats levels and how long it takes is shown to researchers on every offer, once it has decided five reports.
  • Repeated non-payment ends the account. Our team can suspend or ban a company that does not pay.

Disputes

How we handle a disagreement without reading the report.

When a company asks to close a report as not applicable, a person on our team confirms it before anything is closed. That person works from facts we can see, not from the finding.

What we check

Was the job inside the published scope? Is the reason one from the list? Were the deadlines met? Does the bounty match the company's table? What does each side's record look like?

What we do not decide

Whether a bug is real, or how serious it is. Only the company has the report, and its systems are its own. We say this plainly so nobody expects otherwise.

Review by consent

If both sides agree, they can show the report to a member of our team on a call, for that one disagreement. Nothing is uploaded or kept. Without both agreeing, the company's decision stands and counts on its record.

Proof of what was sent

A fingerprint, not a copy.

When a researcher writes the report in the app, it goes from their device to the company: by email from their own account, or into the company's own page. Exploity keeps a fingerprint of the text, a short code that cannot be turned back into the report.

The researcher then slides to submit. The slide stays locked until the report has been written and handed to their email app or the company's page, so a job cannot be marked as sent with nothing behind it.

The company's first step is to confirm the report arrived. If it says nothing arrived, the researcher is asked to send it again and receives no new offers until they do. Either side can check a report against the fingerprint, which settles "no report reached us" without us ever holding the report.

Already known

What "one researcher per job" does and does not prevent.

One job goes to one researcher, so nobody races anyone else on that job, and we do not run two tests of the same type for a company at once.

A finding can still be something the company already knew, from its own team or another platform. A researcher can ask first, naming only the place and type. If it still turns out to be known, it is closed as "already known": recorded as a real finding, and never counted against the researcher.

Questions

Frequently asked questions

How does a researcher raise a disagreement?

From the conversation on the job, with "Ask Exploity to step in". A person on our team replies in the same conversation, where both sides can read it.

Can Exploity force a company to pay?

No. We can refuse a bounty below the company's own table, pause its new tests while a bounty is unpaid, show its record to researchers, and remove it from Exploity.

What if a company closes a report and then quietly fixes the bug?

That is a breach of the company rules and can lead to a ban. The fingerprint and the dates on the job give the researcher something solid to point to.

Can a researcher mark a job as sent without sending anything?

The slide to submit only unlocks once a report is written and sent from the app, and the company then confirms whether it arrived. A researcher whose report did not arrive gets no new offers until they send it again, and doing this on purpose leads to a ban. We cannot see the email itself, so the company's confirmation is the check.

Is a company punished for being a few days late?

No. It gets a reminder and a conversation. Only an unpaid, approved bounty pauses new tests.

Clear rules for both sides.