Usalama Voice

The problem

In Kenya, a survivor may have to repeat their story to several services in the same week. Each one keeps its own record, so nobody holds the full picture. The survivor pays for that every time they have to start again.

What I built

Usalama Voice gives each case one shared timeline. A survivor can raise an alarm or simply read about their options. Each responder works from a dashboard built for their role and sees only what that role allows. Partner organisations are verified before they get any access at all.

What it does

• An emergency flow with a panic button built to work on a poor connection.
• Live emergency consoles and timelines for police and responders.
• Nine role-based workspaces, from survivor and counsellor through to shelter operator and administrator.
• Partner onboarding, with verification before any access is granted.
• A learning hub with plain-language guides to Kenyan law and to safety planning.
• Directories of hotlines and legal aid organisations.
• English and Kiswahili throughout.
• Installable as an app that keeps working offline.

Under the hood

• Next.js and TypeScript, with Supabase and PostgreSQL underneath.
• Row-level security keeps each role away from data it should not see.
• A service worker for offline use, since someone in crisis often has poor signal.
• SMS through Africa’s Talking and email through Resend.

Where it stands

It is not in the hands of survivors yet. The platform is being prepared for a pilot, and most of the remaining work is testing and partner agreements.

Why it might matter to you

This is the project to look at if your organisation shares sensitive information between different kinds of staff or partners.