Brief
Operational partnerships, not extractive pilots.
We need partners who can test language, referral boundaries, route data methods, escalation workflows, and first-party API design without asking survivors to carry platform risk.
Partners
SafeRide needs reviewers and operators who can turn app workflows into safe field practice.
The repo has enough product surface for serious review. The next step is not symbolic logos; it is safeguarding, privacy, legal, transport, backend, and evaluation work with organizations that understand Kenya.
GBV
safeguarding and referral review
SACCO
route and operator workflow validation
API
backend migration and security review
Repo-backed detail
Evidence reviewers can inspect.
Support orgs
Referral language needs expert review.
Crisis copy, 1195 guidance, PEP/EC content, P3 explanations, and referral briefs should be reviewed by qualified Kenyan support and legal-aid partners.
Transport
Operators need action routines, not dashboards alone.
Redacted route signals should connect to route changes, training, escalation handling, and follow-up accountability.
Engineering
Backend hardening is safeguarding work.
Authentication, retention, encrypted evidence handling, access controls, moderation, and observability need partner-level scrutiny before scale.
Current ecosystem
UNICEF plus Kenya-rooted partner references.
The carousel keeps the visible set practical: funder/support signal, survivor support, legal aid, justice access, and community delivery.
Support organizations
Review crisis language, 1195 guidance, PEP/EC content, P3 explanations, referral briefs, and boundaries around legal and psychosocial support.
Transport operators
Validate whether redacted route signals, escalation packets, and follow-up timelines can create safer operational routines.
Engineering partners
Help move from the Supabase prototype to an owned API with authentication, moderation, retention, encrypted evidence, observability, and RLS-equivalent access controls.
Partnership criteria
- 1No partner receives raw survivor evidence or exact journeys without explicit user choice and safeguarding approval.
- 2Every pilot must define referral escalation boundaries, data retention, deletion, and incident response before launch.
- 3Transport partners must commit to action loops, not just dashboards.
- 4Technical partners must preserve offline-first behaviour while reducing backend and secret-management risk.
Ready to help make the next route safer?
Start a partner inquiry