Sensitive drafts
Drafts can include media, transcripts, checksums, legal tags, location accuracy, and pathway choices, so the product must keep review and deletion controls prominent.
Privacy, safety, and trust
Trust starts before anything leaves the phone.
SafeRide keeps drafts local, asks for consent before sharing, and gives riders retention, export, and delete choices.
Privacy, safety, and trust
Consent
before referral, map update, or escalation
Redact
none, light, or heavy escalation options
Workflow
Launch safeguards
- 1Review all public claims for safety, privacy, medical, legal, and emergency-service overpromising.
- 2Approve retention, deletion, backup, analytics, evidence encryption, and support-provider language before public onboarding.
- 3Document the first-party API migration path before collecting sensitive production data.
- 4Never publish survivor stories, exact route details, or evidence screenshots without explicit safeguarding review.
Local first. Shared by choice.
Before referral, map update, or escalation, the app summarizes what leaves the device and what stays private.
Referral boundaries
The app can route a sanitized brief to hotline, GBV centre, legal aid, counselling, or fallback number flows, but it must not impersonate these services.
Backend ownership
Supabase docs remain useful for schema and prototype context, while the launch documentation now records the move toward an owned API with stronger production controls.
Repo-backed detail
Evidence reviewers can inspect.
Consent
The consent gate is the privacy contract.
The app is structured so referral, map update, and escalation paths require a review step before data leaves the device.
Retention
Longer storage is treated as higher risk.
Retention choices, backup, export, and deletion copy explain control without hiding the safety tradeoffs.
Infrastructure
Backend restraint is part of user trust.
The public roadmap names the move beyond Supabase prototype infrastructure while preserving local-first behaviour.
Consent
before referral, map update, or escalation
Control 01
Redact
none, light, or heavy escalation options
Control 02
Own API
documented direction beyond Supabase prototype
Control 03
Ready to help make the next route safer?
Read how it works