KEA NETWORK PBC
Security
Last updated 13 October 2026
This page covers keanetwork.com and keafoundation.org: how we protect them, and how to tell us about a security issue.
Report a vulnerability
Email contact@keanetwork.com with "[Security]" in the subject line. Describe the issue, the affected pages and the steps to reproduce it. We will acknowledge your report and keep you informed while we investigate. The same contact is published in machine-readable form at /.well-known/security.txt.
We don't currently run a bug bounty program.
Testing in good faith
When you look for vulnerabilities, please:
- Don't access, change or delete information that isn't yours.
- Don't degrade the websites for others, for example through denial-of-service or high-volume automated testing.
- Don't use social engineering, phishing or physical attacks.
- Give us reasonable time to fix an issue before disclosing it publicly.
How we protect the websites
- Every page is served over HTTPS, with HTTP Strict Transport Security.
- Security headers prevent other sites from framing our pages and browsers from guessing content types, and restrict which sources pages may load.
- Forms and the chat are screened for automated traffic, and every submission is validated and escaped on the server.
- Forms collect only what we need to respond, and service credentials stay on the server.
- Dependencies are monitored and updated through reviewed pull requests, and every change passes automated checks before it is published.
The websites are hosted on Vercel. For how we handle personal information, see our Privacy Policy.