Vulnerability Disclosure
How to report a security issue in threerf.com.
Last updated: November 17, 2026 (preview draft)
Three Ventures Technology, Inc. ("Three Ventures") is committed to the security of our systems. This policy, modeled on the U.S. Cybersecurity and Infrastructure Security Agency's guidance for vulnerability disclosure policies, explains what is covered, how to send us reports, and how long we ask you to wait before disclosing publicly. We welcome reports from anyone. This is not a paid bug-bounty program.
1. Authorization
If you make a good-faith effort to comply with this policy during your security research, we will consider your research authorized, we will work with you to understand and resolve the issue quickly, and Three Ventures will not recommend or pursue legal action related to your research. This authorization covers only systems we own and operate that are in scope below. It cannot authorize testing of systems owned by others.
2. Guidelines
- Notify us as soon as possible after you discover a real or potential security issue.
- Avoid privacy violations, degradation of user experience, disruption of production systems, and destruction or manipulation of data.
- Use exploits only to the extent necessary to confirm a vulnerability. Do not use one to compromise or exfiltrate data, establish persistent access, or pivot to other systems.
- Give us a reasonable amount of time to resolve the issue before you disclose it publicly.
- Do not demand payment or make disclosure conditional on payment.
If you encounter sensitive data, stop your test, notify us immediately, do not disclose the data to anyone else, and securely delete any copies once you have reported it.
3. Test methods not authorized
- Denial-of-service tests or other tests that impair access to a system or data.
- Physical testing and social engineering.
- High-volume or unthrottled automated scanning and brute-force attempts.
- Testing of third-party services, even if they appear on our pages.
Automated security controls may challenge or temporarily block traffic, including traffic from researchers. This is not legal action. If you are blocked, contact us.
4. Scope
| In scope | Notes |
|---|---|
| threerf.com and www.threerf.com | Public website |
Out of scope: any system not listed above, including other hostnames that appear to belong to us; our service providers' infrastructure (report directly to them); and any government system. If you believe a vulnerability affects a government system, report it under that agency's policy or to CISA.
5. Reporting a vulnerability
Send reports to security@threeventures.com. Reports may be submitted anonymously. Please include where the vulnerability was found and its impact, steps to reproduce it, and whether you would like to be credited. Please do not include personal information, credentials, or other people's data in your report.
6. What you can expect from us
- We will acknowledge your report within 3 business days.
- We will confirm whether the vulnerability exists and keep you informed of progress.
- We ask for 90 days from your report before public disclosure, unless we agree on another date. We will work to fix confirmed issues sooner based on severity.
- With your permission, we will credit you.
7. Open-source releases
Security issues in ThreeRF open-source releases may also be reported to the address above. Releases are subject to the Open Source Notice.