- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 0
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report by email
- [email protected]
- Partial safe harbor
- Some legal protection; read the terms.
- Replies within 5 days
- As the policy promises.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Pays cash
-
No
However, we do not offer monetary rewards for vulnerability disclosures.
- Response
-
Within 5 days
After you have submitted your report, we will respond to your report within 5 working days and aim to triage your report within 10 working days.
- Safe harbor
-
Partial
This policy is designed to be compatible with common vulnerability disclosure good practice. It does not give you permission to act in any manner that is inconsistent with the law
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
0 assets you may test.
Self-hosted does not list the scope of this program publicly. Check its policy.
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Speakeasy's policy.
While testing
-
Access unnecessary, excessive or significant amounts of data.
-
Modify data in the Organisation’s systems or services.
-
Use high-intensity invasive or destructive scanning tools to find vulnerabilities.
-
Disrupt the Organisation’s services or systems.
-
Social engineer, ‘phish’ or physically attack the Organisation’s staff or infrastructure.
-
Demand financial compensation in order to disclose any vulnerabilities.
-
Securely delete all data retrieved during your research as soon as it is no longer required or within 1 month of the vulnerability being resolved, whichever occurs first
Not accepted
-
Submit reports detailing TLS configuration weaknesses, for example “weak” cipher suite support or the presence of TLS1.0 support.
-
Attempt or report any form of denial of service, e.g. overwhelming a service with a high volume of requests.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 5 hours ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.