Privacy, safety, and trust

Your report stays private until you decide otherwise.

SafeRide keeps drafts local, asks for consent before sharing, and gives riders retention, export, and delete choices.

SafeRide Android permissions and privacy settings screens
Privacy, safety, and trust

Consent

before referral, map update, or escalation

Redact

none, light, or heavy escalation options

Workflow

Launch safeguards

  1. 1Review all public claims for safety, privacy, medical, legal, and emergency-service overpromising.
  2. 2Approve retention, deletion, backup, analytics, evidence encryption, and support-provider language before public onboarding.
  3. 3Document the first-party API migration path before collecting sensitive production data.
  4. 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.

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.

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

Prototype documentation remains useful for review, while production planning moves toward Esheria-controlled services with stronger authentication, encryption, retention, and access controls.

SafeRide Android permissions and privacy settings screens

Supporting detail

How privacy is enforced in the product.

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 keeps local-first behaviour while moving sensitive services under Esheria-controlled production infrastructure.

Consent

before referral, map update, or escalation

Control 01

Redact

none, light, or heavy escalation options

Control 02

Owned

Esheria-controlled production services

Control 03

Review what stays private and what can be shared.

Read how it works