Skip to main content
SafeRide
Download
What We Do
How It WorksFor SurvivorsPrivacy & TrustRoute Safety IndexImpact
Open Source
Our Story
Partners
Blog
Download App
What We Do
How It WorksFor SurvivorsPrivacy & TrustRoute Safety IndexImpact
Open Source
Our Story
Partners
Blog
Download App

Impact and transparency

The impact question is whether SafeRide changes workflows without creating new risk.

The repo shows product readiness, but impact still depends on field evidence: completion, comprehension, privacy confidence, referral usefulness, route action, and backend safety.

Measure behaviour, not hype.

A responsible pilot should track whether women can safely start reports, understand consent, use legal/support content, preserve evidence, and whether partners act on aggregate route signals.

Completion

draft-to-pathway conversion and abandonment

Trust

user confidence in consent and data controls

Action

operator or support response to route patterns

Transport safety review session focused on route action and accountability

Repo-backed detail

Evidence reviewers can inspect.

Usability

Measure whether the flow works under stress.

Completion, abandonment, comprehension, and recovery from offline states matter more than broad claims about safety outcomes.

Safeguarding

Measure whether guidance stays within boundaries.

Tips, referrals, and assistant responses should be reviewed for overpromising, unsafe escalation, and unclear data-sharing language.

Accountability

Measure whether partners actually change routes.

The Route Safety Index should be judged by partner response and corrective action, not only by data collection.

Product evidence

Measure whether the draft, evidence, legal framing, pathway, consent, and case tracker screens are usable under low-signal and high-stress conditions.

Safeguarding evidence

Review whether tips, provider choices, referral briefs, and AI guidance avoid overpromising and point users toward qualified human support.

Infrastructure evidence

Publish what changed as SafeRide moves from Supabase prototype infrastructure to a first-party API with production-grade controls.

Transparency commitments

  1. 01Separate repo-complete features from field-validated outcomes.
  2. 02Report unresolved risks around evidence encryption, backend migration, CI debt, and content review.
  3. 03Use privacy-safe analytics only when approved and never capture incident details in analytics.
  4. 04Publish non-sensitive pilot learnings, methodology limits, and corrective actions.

Ready to help make the next route safer?

Review the safety model
SafeRide

Safer journeys. Open by design.

Product

  • What We Do
  • How It Works
  • For Survivors
  • Route Safety Index
  • Privacy & Trust

Open Source

  • Open Source Overview
  • GitHub
  • HuggingFace Model
  • License Posture
  • Security Roadmap

Partners

  • Pilot Partners
  • Support Organizations
  • Transport Operators
  • Engineering Reviewers
  • Partner with Us

Organisation

  • Our Story
  • Impact
  • About Esheria
  • Privacy Guide
  • Contact

© 2026 Esheria Ventures Limited

Apache 2.0 CC-BY 4.0 Built in Nairobi, Kenya 🇰🇪