Liability Shield

Hardware utilization terms. Dhiig-Baaq is a pure, unlicenced technical routing matrix, not a sovereign medical provider.

1. Medical Verification Burden

Aesthetics of the Interface do not equate to Medical Endorsement.

Dhiig-Baaq operates exclusively as an automated communication pipeline bridging critical data (a hospital SOS) to verified mobile nodes (civilians). We explicitly do not test, screen, verify, or guarantee the cellular purity of any blood unit sourced through this platform.

The receiving Tier-1 Facility (the hospital) assumes **100% of the medical and legal liability** for the screening, drawing, storage, and transfusion of the blood. If a donor sourced via our WhatsApp API carries an infectious disease or provides medically unusable material, Dhiig-Baaq holds absolutely zero legal culpability. Medical verification remains the ultimate and un-transferable burden of the surgical team.

2. Immunity from Clinical Outcomes

You agree that Dhiig-Baaq is a software routing layer. Therefore, the platform and its engineers cannot be held liable for any clinical injuries, fatalities, or adverse medical events stemming from operations sourced through the network. We do not provide medical advice. We provide algorithms.

3. Network Failures & SLA Limitations

The Dhiig-Baaq engine relies heavily on external infrastructure—including the Meta WAHA (WhatsApp) container, PostgreSQL cloud compute, and local Banadir ISP cell towers.

Consequently, we do not issue any Service Level Agreements (SLAs) regarding 100% uptime. If a network outage, API timeout, or hardware routing failure results in an SOS pulse flatlining before reaching civilians—leading to a delayed surgical deployment—Dhiig-Baaq is structurally immune from liability. Hospitals must maintain secondary analog fallback systems for securing blood.

Execution of these terms is absolute upon usage of the routing matrix.