Open source

The repo is the evidence: mobile app, content packs, prototype backend, and launch site.

SafeRide is built so safeguarding reviewers, engineers, funders, and civic partners can inspect the implementation, challenge the claims, and improve the safety model before scale.

Brief

Public-interest technology needs public accountability.

The public surface points to the accountability trail: Android screens, local storage utilities, offline sync helpers, data export logic, local assistant configuration, legal content data, Supabase prototype docs, sitemap, and the production API path.

Apache-2.0

code license for public-good reuse

CC-BY-4.0

open content license posture

Gemma

on-device assistant roadmap

Open-source SafeRide review desk with repository, Android device, and architecture notes

Repo-backed detail

Evidence reviewers can inspect.

Client

The Android client shows the product contract.

Screens, navigation, draft persistence, case tracking, privacy controls, and content packs can be reviewed directly in the repository.

Backend

Supabase is documented as prototype infrastructure.

Migrations, seeds, storage assumptions, and Edge Function notes remain useful while the launch direction moves to a first-party API.

Assistant

The local model path is scoped, not magical.

Gemma support is framed around guidance, transcription, and tagging, with survivor-centred prompts and offline-first constraints.

Launch site

The website is part of the audit surface.

Routes, metadata, sitemap, robots policy, contact inbox, and public copy are treated as launch artifacts that reviewers can test, not marketing afterthoughts.

Useful links

Inspect the work directly.

Source

GitHub repository

Review the Android app, website, content packs, prototype backend notes, and launch implementation.

Model

Gemma model card

Inspect the planned on-device assistant posture before it is used for guidance, transcription, or tagging.

Install

Android pilot download

Use the pilot carefully, with the safety boundaries and APK handling notes made explicit.

Safety

Privacy and trust model

Read the local-first, consent-gate, redaction, retention, deletion, and backend ownership commitments.

Public guides

Safety and legal notes

Share public-facing explanations of privacy, referral boundaries, and route-safety data with reviewers.

Contact

Review inbox

Send security, safeguarding, legal-content, API, or pilot-review questions to the SafeRide team.

Android client

Expo and React Native power the app screens, navigation, offline draft storage, privacy controls, decoy mode, quick exit, and case workflows.

Local assistant

The Gemma-3n registry defines files, checksums, storage directory, survivor-centred system prompt, and capabilities for guidance, transcription, and offence tagging.

Backend transition

Supabase remains documented as the prototype stack. The next backend phase is a first-party API, documented here without changing implementation in this branch.

Launch transparency

The website publishes canonical routes, sitemap coverage, contact paths, open-source links, and public-facing safety language so launch readiness can be reviewed in the open.

What contributors can audit now

1Review privacy claims against draft storage, consent screens, data export, decoy PIN, and quick-exit utilities.
2Improve TypeScript and CI debt documented in the Supabase handoff before production hardening.
3Help design the first-party API contract that replaces Supabase while preserving local-first behaviour.
4Validate legal and support content with Kenyan GBV, medical, legal, and safeguarding experts.

Ready to help make the next route safer?

Read pilot updates