How SafeRide keeps a report private until you choose a path

SafeRide begins with a draft on the rider’s phone. A rider can record what happened in their own words, add only the details they feel safe keeping, and pause without choosing a reporting or support route. The pilot is designed so creating a draft is not the same as sending a report.

That distinction matters on public transport, where signal may be unreliable and someone may be watching the screen. The first task is to preserve the rider’s control, not to force an upload or require an immediate decision. If recording details would create more risk, the rider can leave the draft and return later.

When a rider is ready, SafeRide presents separate choices: keep the record private, contribute a minimized route signal, prepare information for a support provider, or prepare a more formal report. These choices are not interchangeable, and none should happen silently in the background.

Before sharing, the product should show the information included, the information removed, the destination, and the selected redaction level. The rider should be able to go back, remove an attachment, change the destination, or stop. Consent is useful only when the person can understand and change the decision.

A private statement, audio clip, photograph, or support brief can contain details that identify a person. A route-safety signal serves a different purpose: it should describe a broad pattern without carrying names, raw audio, private evidence, or an exact journey.

SafeRide treats those data types as separate records with separate sharing decisions. This reduces the risk that a community-safety feature becomes another way to expose a survivor. It also makes it clearer to transport and civic partners that route trends are not a substitute for consented case information.

Privacy is not complete at the moment of collection. A rider also needs a clear way to review, export, retain, or delete a draft. The pilot surfaces those controls so the person can decide whether keeping information on the device remains useful and safe.

Anyone testing SafeRide should use synthetic reports until the field configuration, encryption, backup, retention, and support-provider settings have completed safeguarding review. Do not enter real survivor evidence into an unsupervised pilot build.