Trust centre · current product controls
Boundaries before automation
Wasl is designed around data minimisation, consent-aware measurement, tenant separation and explicit human handoff. This page distinguishes implemented controls from deployment-specific obligations.
Human control
Approved information sources and authority boundaries define what the system may answer. Ambiguous, sensitive or judgement-based questions are routed to an authorised person.
Data controls
The application contains consent recording, tenant-scoped repositories, data export and deletion routes, origin checks and restricted public event submission. Production access, encryption keys and retention jobs remain deployment responsibilities.
Healthcare boundary
The system may collect administrative context; it must not diagnose, recommend treatment or decide clinical suitability. Clinical and sensitive questions require authorised healthcare staff.
Subprocessors and incidents
Before production launch, the operator must publish the exact hosting, database, analytics, AI and scheduling subprocessors, hosting regions, transfer basis and security contact. Suspected incidents should be reported through the contact page.