Panic Inc.
Vulnerability disclosure program on security.txt panic.com
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 5
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report through their form
- panic.com/.well-known/security.txt
- Full safe harbor
- Good-faith research is authorised; no legal action.
- 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
We are not currently offering bug bounties or rewards for vulnerability discoveries.
- 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
5 assets you may test, 7 excluded.
Domains 2
- panic.com
- play.date
Products and areas 3
- Panic Products and Software
- Product Documentation
- Services and Infrastructure
Out of scope (7)
- Assets or other equipment not owned by parties participating in this policy.
- Findings derived primarily from social engineering (e.g. phishing, vishing);
- Findings from applications or systems not listed in the Systems in Scope section;
- Findings from physical testing of facilities such as office access (e.g. open doors, tailgating);
- Network level Denial of Service (DoS/DDoS) vulnerabilities; and
- Spelling mistakes;
- UI and UX bugs with no security implication;
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Panic Inc.'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 Channels to discuss vulnerability information with us;
-
Provide us a reasonable amount of time to resolve the issue before you disclose it publicly;
-
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;
-
You should only interact with test accounts you own or with explicit permission from the account holder; and
-
Do not engage in extortion.
Not accepted
-
UI and UX bugs with no security implication
-
Spelling mistakes
-
Network level Denial of Service (DoS/DDoS) vulnerabilities
-
Findings derived primarily from social engineering (e.g. phishing, vishing)
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 12 Nov 2026. Last checked 2 hours ago.
-
Scope +
Added to scope: play.date
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.