We take security seriously and welcome reports from independent researchers. If
you believe you have found a vulnerability in peekbell, please follow the
process below.
How to report
Submit a report through the
contact form
with the subject set to Security. Include:
- A clear description of the issue and its impact.
- Step-by-step reproduction.
- Affected URL or endpoint, and the time of testing.
- Your name or handle for credit, if you want it.
Please give us a reasonable window to investigate and fix the issue before
public disclosure. We aim to acknowledge reports within five business days.
In scope
- The peekbell web app and its public API.
- Authentication and session handling.
- Data exposure or access-control issues.
- Injection, XSS, SSRF, and other OWASP-style vulnerabilities.
Out of scope
- Denial-of-service or volumetric attacks.
- Social engineering against peekbell staff or users.
- Physical attacks on infrastructure.
- Vulnerabilities in third-party software outside our control.
- Reports generated solely by automated scanners with no proof of exploitability.
Safe harbor
We will not pursue legal action against researchers who act in good faith,
respect user privacy, give us a reasonable disclosure window, and stay
within the scope above. If in doubt, ask before testing.
security.txt
Machine-readable disclosure metadata lives at
/.well-known/security.txt.