Security Practices
This page explains the controls that protect forms and responses, the limits of those controls, and how to report a problem safely.
Effective November 11, 2026
At a glance
Application
The application validates requests, limits access, protects sessions, and sends only approved output.
Form owner
The owner limits collection, reviews access, monitors abuse, and deletes records on schedule.
Reporter
A reporter describes the affected route, impact, and safe reproduction steps without disrupting production.
Core controls
Production requires HTTPS, MySQL, a strong secret, secure cookies, host validation, content security policy, server-side validation, CSRF protection, bounded input, formula-safe CSV exports, and least-privilege deployment credentials.
Form abuse
Hosted forms use a honeypot and minimum completion time. Deployments should add rate limiting at the reverse proxy and monitor unusual submission volume without weakening accessibility for legitimate respondents.
Reporting
Do not test against production data or disrupt the service. Send a concise report with the affected route, impact, and reproduction steps. Allow time for validation and repair before public disclosure.
Related implementation guidance
Continue with the online form security guide and the broader form privacy and security hub.
