Legal
Security
Last updated
This page describes how the nexolabs.ee website is built and protected, and how to report a vulnerability in any Nexo Labs OÜ property. Each of our products documents its own security on its own site, for example nexoboard.com and nexotalk.com.
1. Website architecture
- The site is plain static HTML, CSS and JavaScript, built ahead of time. There is no CMS, no database, no backend, no forms and no user accounts on nexolabs.ee. You reach us by email, so the site never receives anything you type.
- The site is hosted on Cloudflare’s network (Cloudflare Pages), which also provides DNS, TLS, DDoS mitigation and a web application firewall. We run no web server of our own and no server-side code for this site.
- We serve the site over HTTPS only, with HSTS. Plain HTTP requests are redirected.
- The browser is allowed to run scripts only from our own domain. Our Content Security Policy blocks inline scripts and third-party trackers, fonts and CDNs, lets scripts open no network connections and pages submit no forms, and stops other sites from framing this one (
frame-ancestors). We also send theX-Content-Type-Options,Referrer-PolicyandPermissions-Policyheaders. - Only
GETandHEADrequests are answered; anything else is refused by the firewall at Cloudflare’s edge. - The published site contains no API keys or passwords, and none are kept in the code.
2. Responsible disclosure
If you believe you have found a security vulnerability, please email security@nexolabs.ee with a description, steps to reproduce and the impact you observed. Our machine-readable contact is published at /.well-known/security.txt.
- We acknowledge reports within 3 business days and keep you informed while we fix the issue.
- Please give us reasonable time to fix the issue before disclosing it publicly.
- Act in good faith: do not access, modify or delete other people's data, do not degrade service availability (no DoS or volumetric testing), and do not use social engineering or physical attacks.
- We will not pursue legal action against researchers who follow these guidelines.
We do not currently run a paid bug bounty program, but we are happy to credit researchers who help us.
3. Out of scope
- Missing best-practice headers without a demonstrable impact.
- Reports from automated scanners without verification.
- Denial-of-service or rate-limit findings that rely on sending large numbers of requests.