responsible disclosure
Responsible disclosure policy
Last updated: .
Security researchers help keep NeoShield safe. If you find a vulnerability, please report it to us privately and give us a reasonable chance to fix it before disclosing it publicly. We appreciate good-faith research and will work with you.
How to report
Email security@neoshieldsecurity.com (the same address is published in our security.txt). Include a clear description, the steps to reproduce, the impact, and any proof-of-concept. Please report privately — don't post the issue publicly until we've had a chance to address it.
Scope
- neoshieldsecurity.com
- The public web application
- Public APIs, where applicable
Safe harbor
We consider good-faith security research conducted under this policy to be authorized. We won't pursue action against researchers who follow these rules, act in good faith, and avoid privacy violations, data destruction, or service disruption. If you're unsure whether something is allowed, ask us first.
Rules — allowed
- Good-faith testing intended to find and report vulnerabilities.
- Testing only against your own account and your own data.
- Detailed, private reporting that gives us time to remediate.
Rules — not allowed
- Denial-of-service or any test that degrades or disrupts the service.
- Social engineering of our staff, users, or vendors.
- Physical attacks against people or property.
- Accessing, modifying, or destroying other users' data.
- Data exfiltration.
- Automated scanning that disrupts the service or generates excessive load, and any load or stress testing.
- Using NeoShield's own scanner or tools against systems you do not own or are not authorised to test.
What to expect
- We aim to acknowledge your report within 7 business days.
- We aim to remediate validated issues within 90 days where reasonably possible, and we'll keep you updated on progress.
- With your permission, we're happy to credit you once an issue is resolved.
What qualifies
Any issue with a demonstrated security impact on NeoShield or its users. Weak or missing rate limits do qualify when you can show impact with a small, controlled number of requests, for example:
- Sign-in code (OTP) brute force, or bypassing the code-attempt limits.
- Account enumeration (learning whether an address has an account).
- Authentication or session bypass, session fixation, or a revoked session that keeps working.
- AI cost exhaustion — running metered AI features without an account or beyond plan limits.
- Payment or entitlement abuse — getting paid features, credits or longer access without paying.
- Scanner abuse — using our scanner against systems you do not control, reaching internal addresses (SSRF), or scheduling scans without domain verification.
- Cross-tenant effects — reading, changing or influencing another account's or workspace's data.
- Availability weaknesses demonstrated at low volume (for example one request that ties up a worker for minutes).
Please demonstrate rate-limit and availability issues with the minimum number of requests needed, against your own account, and stop as soon as the effect is shown. Describe how the attack would scale instead of scaling it.
Out of scope
Reports that typically won't qualify: missing best-practice headers with no demonstrated impact; volumetric denial-of-service or load testing of any kind; social-engineering findings; results from automated scanners without a verified impact; and vulnerabilities in third-party services (Stripe, Anthropic, Google, Hostinger) that we don't control — please report those to the relevant vendor.
This policy describes our intent for good-faith research; it is not a contract and may be updated as the platform evolves.