01
Built for the first minutes
The app creates a draft and gives structured prompts before a user has to decide whether to report, refer, map, or escalate.
Our story
SafeRide grew from everyday transport risk into a local-first safety product.
The repository tells the story clearly: a mobile app built for public transport harassment, privacy-first evidence handling, Kenyan legal/support guidance, and route-level accountability that still needs careful field validation.
Nairobi-first, survivor-controlled, open for review.
The work is practical: make it easier to record facts, understand rights, find support, preserve agency, and create prevention signals without turning survivor experiences into marketing material.
SafeRide is strongest when the rider controls the pace: draft first, choose the path, review consent, then decide what leaves the phone.
02
Built for discretion
Stealth trigger setup, calculator decoy mode, quick exit, app masking, and local retention choices reflect real-world safety constraints.
03
Built for accountability
Route-level insights, case tracking, open-source docs, and a first-party API roadmap keep the product focused on measurable safety improvements.
Repo-backed detail
Evidence reviewers can inspect.
Origin
The story starts with daily transit risk.
The repo positions SafeRide around public transport harassment, evidence control, and practical support pathways for Nairobi riders.
Principle
The product should never mine trauma for growth.
Public claims, visuals, and metrics need to stay traceable to product behaviour or pilot evidence, not dramatic survivor storytelling.
Review
Open work invites challenge before scale.
The website, roadmap, content packs, mobile flows, and UNICEF Venture Fund presentation are presented as reviewable artifacts rather than a finished institutional promise.
UNICEF meet
SafeRide presented in the room.
The UNICEF Venture Fund meet is part of the SafeRide story: a review moment where the team explained a privacy-first transport safety workflow to funders and reviewers.
What guides the work
- 01Do not sensationalize survivor experience for visual design, metrics, or fundraising.
- 02Make safety, privacy, and route-accountability claims traceable to product behaviour or pilot evidence.
- 03Treat backend ownership, retention, encryption, and observability as safeguarding work.
- 04Use the repo as a living artifact for partners to challenge and improve.
Ready to help make the next route safer?
See the public-good stack