Operations · guest safety
Protection policy
How Neon Vector Arena approaches on-site safety, hosting hygiene, HTTPS delivery, and practical security expectations for our venue website.
Threat model, honestly
We are not a bank, a payment processor, or an on-site medical provider. Our goal is proportionate hygiene: ship over HTTPS, keep dependencies current, and respond in good faith if someone reports a flaw.
Your device, ISP, and third-party apps remain outside our perimeter—phishing awareness and OS updates still beat anything we can promise on a venue information website.
Last updated: May 8, 2026
This Protection Policy describes how Neon Vector Arena addresses security and guest safety while operating an indoor laser tag venue website in Serrekunda.
No website can promise perfect safety. What we can do is keep our stack patched, monitored, and clear about operational limits.
1. Transport security (HTTPS)
We intend to deliver all pages over HTTPS with TLS versions supported by mainstream browsers. HTTPS protects the connection between your device and our host against casual eavesdropping on public Wi‑Fi. It does not by itself prove that every sentence on the page is accurate—you should still verify booking details with our crew.
If you see certificate warnings, stop and verify the domain spelling before entering passwords anywhere.
2. Dependency and supply-chain hygiene
We load some assets from well-known CDNs (fonts, icons, animation libraries). We prefer pinned versions and subresource integrity where feasible to reduce “typosquat” package surprises. When upstream vendors publish security advisories, we aim to upgrade during scheduled maintenance windows.
3. Data minimization as a security strategy
We rarely collect accounts, which shrinks the database attack surface. Our contact demo currently avoids server round-trips; if we add real messaging, we will document encryption at rest, access controls, log redaction, and retention caps in the Privacy Policy.
4. Application security expectations
If we ship interactive features (comments, profiles, API keys for tools), we will apply baseline web hygiene: CSRF protections on mutating requests, rate limits where affordable, output encoding against XSS, and spam filtering tuned for fraud-related keywords.
5. Incident response and responsible disclosure
If you discover a vulnerability (for example, stored XSS on a form), email [email protected] with reproducible steps, affected URLs, and suggested severity. We review reports in good faith.
Please do not mass-scrape production, do not perform destructive tests, and do not access accounts that are not yours.
6. Phishing and social engineering risks
Bad actors may impersonate venue staff to harvest credentials. Neon Vector Arena will never ask for passwords, one-time verification codes, or payment card numbers through unsolicited direct messages.
Offers of unauthorized discounts, fake payment links, or account-reset scams are fraudulent. Verify all support communication through official contact channels.
7. User-side responsibilities
- Keep your OS, browser, and security tools updated.
- Use unique passwords and a password manager; do not reuse credentials across sites.
- Verify links before logging in; homoglyph domains (rnexus vs nexus) are a classic trick.
- Teach younger squadmates that voice chat “coaches” asking for account swaps are almost always scammers.
8. Device and network perimeter
We cannot patch your router, remove parental spyware you installed, or stop a compromised device keylogger from stealing credentials you type after leaving our site. Endpoint security remains your responsibility.
9. Content safety and moderation (future)
If we add public comments, we will publish community guidelines prohibiting harassment, doxxing, hate speech, and sexual content involving minors. Moderators may remove posts and ban accounts that endanger guests.
10. Advertising security
Malvertising occasionally slips through reputable networks. Use blockers if you need aggressive protection, and report malicious redirects to the ad vendor. We prohibit creatives that promote cheating or account theft.
11. Scope limits and official channels
Payment platforms and external providers remain responsible for their own billing disputes and account enforcement decisions. In such cases, only official support channels can explain enforcement actions.
12. Contact
Security questions may be sent to [email protected] with “Protection Policy” in the subject line.