Deputy
Vulnerability disclosure program on Self-hosted deputy.com
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 2
- 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
- https://www.deputy.com/security/report-a-vulnerability
- Full safe harbor
- Good-faith research is authorised; no legal action.
- No public write-ups
- Keep findings private.
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Safe harbor
-
Full
authorized concerning any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good-faith violations of this policy;
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
2 assets you may test, 1 excluded.
Domains 1
- deputy.com
Products and areas 1
- any digital assets owned, operated, or maintained by Deputy
Out of scope (1)
- any assets or other equipment not owned by Deputy
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Deputy's policy. "We" in these lines means the program, not this site.
While testing
-
report any vulnerability you’ve discovered promptly;
-
avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience;
-
use only the official channel listed below to discuss vulnerability information with us;
-
provide us a reasonable amount of time to resolve the issue;
-
perform testing only on in-scope systems, and respect systems and activities which are out-of-scope;
-
limit the amount of data you access to the minimum required for effectively demonstrating a proof of concept;
-
cease testing and submit a report immediately if you encounter any user data during testing, such as personally identifiable information, personal healthcare information, credit card data, or proprietary information;
-
you should only interact with test accounts you own or with explicit permission from the account holder;
-
do not engage in extortion; and
-
do not disclose the issue publicly.
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.