Privacy policy

To complete: the data controller’s identity and contact details, the appropriate contact for data questions and, where relevant, the data protection officer.

The form includes name, work email, organisation, subject and message; phone number and headcount are optional. Sending remains disabled until the server integration is configured. Purposes, legal basis, recipients and retention periods must be specified before activation.

The demonstration uses only fictional people, responses and situations. It does not request the visitor’s location, access contacts or send emergency notifications. Simulation responses are not operational data.

The website does not use advertising trackers or audience analytics. Contact details entered in the form are not saved in browser local storage or written to application logs. Any hosting logs and their retention periods still need to be documented.

The application’s processing will require separate documentation: work accounts, site assignments, acknowledgements, answers, reasons and any location during an alert. Permissions, recipients, retention periods, processors and security measures remain to be defined.

To complete according to the applicable framework: individual rights, how to exercise them, handling deadlines, the appropriate contact and possible recourse to the relevant authority. This preview does not invent a contact address.

If the site uses Cloudflare to handle web traffic, its security features may set technical cookies. When bot protection is enabled, __cf_bm helps identify automated traffic and expires after 30 minutes of inactivity. The cf_clearance cookie can record the outcome of a security check for the configured duration. Cloudflare states that cookie data may be processed in the United States, depending on the service configuration.

If Turnstile is enabled on the form, Cloudflare processes technical signals, including the IP address and browser information, to limit automated submissions. The website server validates the single-use token generated by the check. Turnstile pre-clearance is off by default. With that setting, the widget does not set a cf_clearance cookie.