How it works

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

SafeRide assumes a rider may have low signal, low time, and high risk. The workflow therefore starts privately, records only what the user chooses, and delays sharing until the pathway is clear.

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

0

network required to begin a draft

90

day default retention note in consent flow

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, anonymous map update, 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, share an anonymous map update, get help through a hotline or provider, or escalate for operator/regulator action.

Confirm consent

The consent screen summarizes when, where, what happened, attachments, tags, identity, provider, contact method, statement, and redactions.

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 mobile app keeps local draft work available and queues 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.

0

network required to begin a draft

Control 01

90

day default retention note in consent flow

Control 02

3

redaction levels for escalation packets

Control 03

Review the pilot before using it in the field.

Download the pilot