Last updated:
How we protect data
Security is part of how we build, not an add-on. In plain terms:
- Encryption in transit. Our website and services are served over HTTPS.
- Least-privilege access. People and systems get only the access they need.
- No passwords to store. Sign-in uses Google, so we never ask for or store your password.
- Keeping software current. We update dependencies regularly and review security advisories.
No system is perfectly secure. If a breach affects your personal information, we’ll notify you as required by law. See our Privacy Policy.
Vulnerability Disclosure Policy
We welcome reports from security researchers and anyone who finds a problem. If you think you’ve found a vulnerability, please tell us so we can fix it.
Scope
In scope:
- Our website at www.vornbuilt.com and its subdomains operated by VORN;
- Accounts on our website and our APIs; and
- Our games and playtest builds.
Out of scope:
- Services run by others, such as Google or Vercel. Please report those to the provider.
- Denial-of-service, spam, or social engineering of our staff or users.
- Physical attacks on our offices or equipment.
- Low-impact findings without a demonstrated risk, such as missing headers alone or self-XSS.
How to report
Email justice@vornbuilt.com with the subject line “Security report”. Please include:
- what you found and where (URL, feature, or build);
- steps to reproduce it, and a proof of concept if you have one;
- the potential impact; and
- how we can reach you.
We’ll acknowledge your report within 5 business days, keep you updated, and let you know when it’s fixed. We’re glad to credit you publicly if you’d like. We don’t currently offer paid bug bounties.
Our machine-readable contact details are in /.well-known/security.txt.
Please don't
- access, change, or delete data that isn’t yours, beyond the minimum needed to show the issue;
- keep or share any personal data you come across. Stop and tell us right away;
- degrade our services, run denial-of-service tests, or use automated scanners at high volume;
- make changes to anyone else’s account;
- use social engineering, phishing, or physical attacks; or
- publicly disclose the issue before we’ve had a reasonable time to fix it (we ask for 90 days, or sooner by agreement).
Safe harbor
If you make a good-faith effort to follow this policy, we consider your research authorized. We won’t pursue or support legal action against you for it, including under anti-hacking laws such as the Computer Fraud and Abuse Act or anti-circumvention laws, and we’ll treat it as an exception to our Acceptable Use Policy and Terms of Service for that research.
If a third party takes legal action over research you did under this policy, we’ll make it known that your actions were authorized by us. This safe harbor doesn’t cover research on third-party services or activity that breaks the law in ways unrelated to good-faith security research. If you’re unsure whether something is allowed, ask us first.