Security Policy
Reporting a vulnerability
We welcome responsible disclosure of security issues. If you believe you have found a vulnerability in openvan.camp or any of our infrastructure, please report it privately using one of the contacts below.
Preferred contact:
- Email: [email protected]
- Telegram: @Kopaev
We will acknowledge your report within 7 days and aim to remediate validated issues within 90 days, depending on severity.
What is in scope
openvan.campand*.openvan.campsubdomains- Public APIs documented at
/en/developersand/.well-known/openapi.json - Our public source code
- Mobile/PWA installations of openvan.camp
What is NOT in scope
- Third-party services we rely on (Cloudflare, hosting providers, ad networks). Report directly to them.
- Social-engineering attacks against staff, contractors, or users.
- Physical attacks against infrastructure.
- Findings that require already-compromised credentials or root access.
- Volumetric DoS/DDoS — please do not test load capacity. Synthetic stress is destructive.
What we ask of you
- Do not access, modify, or delete data that is not your own.
- Do not publicly disclose details until we have had a reasonable chance to remediate.
- Do not exploit beyond what is necessary to demonstrate impact (no lateral movement, no persistent backdoors).
- Use a clearly identifiable user-agent containing the word
security-researchso we can distinguish your traffic from real attacks.
Safe harbor
If you act in good faith and follow this policy, we will not pursue legal action against you, nor ask law enforcement to. We treat such reports as authorized research.
Recognition
We do not currently run a paid bug-bounty program, but we publicly thank responsible researchers in our release notes when fixes ship (with your permission).