How it works

How to document and report harassment on a matatu — privately.

The workflow was tested in the supervised HURIA pilot in Mombasa. It was designed for a rider who may have low signal, low time, and high risk, so it started privately, recorded only what the user chose, and delayed sharing until the pathway was clear.

SafeRide Android incident draft, report steps, and case tracker screens
How it works

0

network required to begin a draft

Local

reports stay on the phone until the rider deletes them

Workflow

The rider journey

  1. 1Open SafeRide directly or through stealth/decoy entry points when safety requires discretion.
  2. 2Start or resume a local incident draft and add only the details the rider feels safe recording.
  3. 3Use legal framing and rights content to understand possible categories without treating the app as legal advice.
  4. 4Select a pathway and review the consent checklist before a referral or escalation is prepared.

A structured path from incident to next step.

The reporting flow covers what happened, where and when, evidence, legal framing, pathway choice, consent review, referral selection, escalation details, and case status.

Capture and clarify

The draft can hold patterns, narrative, impact, witness details, route context, timing accuracy, media files, annotations, transcripts, and legal tags.

Pick a pathway

Save privately, get help through a hotline or provider, or escalate for operator/regulator action. Anonymous route mapping remains a planned layer.

Confirm consent

The consent screen summarizes when, where, what happened, attachments, tags, identity, provider, contact method, statement, and redactions before a referral or escalation.

SafeRide Android incident draft, report steps, and case tracker screens

Supporting detail

How the reporting flow protects riders.

Draft state

Progress is saved as the rider moves.

Draft utilities persist incident details, evidence metadata, location context, legal tags, pathway choice, and completion state.

Offline queue

Network-dependent work waits until it can sync.

The pilot build was designed to keep local draft work available and queue share or case actions rather than blocking the rider at the first weak signal.

Consent review

Sharing is a deliberate screen, not a hidden side effect.

Before referral or escalation, the user reviews what will be sent, where it goes, and what redaction level is applied.

Testing the flow

Tried on real phones, with the team beside them.

The pilot ran in two stages: practice first, then live reporting with HURIA present.

This photograph shows a briefing, demonstration or event. Nothing here comes from a survivor’s report.

See the pilot in pictures
Three colleagues talk around a meeting table beside a screen headed Live demo with a QR code.
A live demo at the partner briefing: the screen shows the QR code for the app.

0

network required to begin a draft

Control 01

Local

reports stay on the phone until the rider deletes them

Control 02

3

redaction levels for escalation packets

Control 03

Questions people ask.

Do I need a connection to start?

No. A draft can be started with no network. Work that needs a connection waits in a queue rather than blocking you at the first weak signal.

What can a draft hold?

Patterns, a narrative, impact, witness details, route context, timing accuracy, media files, annotations, transcripts and legal tags, all optional.

Can I stop and come back later?

Yes. Progress is saved as you move, so a draft can be resumed, edited or deleted.

What does the consent screen show?

What will be sent, where it goes and what redaction level applies: when, where, what happened, attachments, tags, identity, provider, contact method, statement and redactions.

See what the Mombasa pilot has already delivered.

Read the pilot update