Our baseline
- Validate and constrain inputs at the server boundary.
- Use protected environment variables and never commit secrets.
- Apply least-privilege access to administration and data stores.
- Keep dependencies and deployment systems reviewed and updated.
- Use security headers, HTTPS and safe error responses in production.
Responsible disclosure
If you believe you have found a security issue in this website, please report it privately through the contact address on the contact page. Include a clear description, affected URL, steps to reproduce and any relevant proof of concept. Please do not access, change or delete other people's data.
Important note
This page describes a security baseline, not a guarantee of risk-free software. The final production environment should have an owner, an incident response process, backups and periodic security review.
Last reviewed: 7 October 2026.

