CSRF
A session-bound token prevents another website from submitting a form on the visitor’s behalf.
This page explains what the forms collect, how the server processes submissions and what information should never be sent.

A session-bound token prevents another website from submitting a form on the visitor’s behalf.
The token has a limited lifetime, includes a minimum fill time and is consumed after successful submission.
Repeated submissions from the same pseudonymous client identity are limited within a time window.
Required fields, lengths, formats, allowed values and consent are checked again on the server.
Applications and enquiries are encrypted at rest with a 256-bit key using sodium secretbox or AES-256-GCM fallback.
When enabled, email contains only the reference number, category and time — no personal data.
AEMB_FORM_KEYA base64-encoded 32-byte encryption key stored in the server environment, not in source control.
AEMB_STORAGE_PATHAn absolute path outside the public web root for encrypted submissions and audit records.
AEMB_RECRUITING_EMAILOptional address for non-sensitive notifications that a new encrypted submission exists.
HTTPSTLS must be enabled for all public pages and forms.