Back to HAANHAAN • Information & policies

Security

HAAN is designed so dismissal speed remains separate from the safety decision to release a student.

Last updated: 4 October 2026

Clear authorization

Sensitive school actions are limited to authorized workspace users, while guardian identity and experience remain separated from school administration.

Independent release verification

Arrival changes operational state; it does not approve release. Verification and handoff are separate actions performed by authorized school staff.

Operational history

HAAN uses explicit states for important events so schools can review a request path instead of relying on memory or scattered messages.

Report a security concern

If you notice unexpected security behavior, send details to support@wessaal.com. Never send passwords or verification codes in the report.