THE SAFETY FLOW · EXPLAINED
From a short signal to a clear next step.
A safety system is only trustworthy when its decisions can be followed. Here is the complete path from user consent to a possible SOS.
FIVE STAGES
Protection with a human in the loop.
Each stage has a narrow job. The app checks system health, limits stored data, and keeps escalation visible.
START
You choose when protection begins.
Monitoring starts only after setup, permissions, and consent. The dashboard shows whether audio, motion, location, and background coverage are ready or degraded.SENSE
The phone checks short-lived signals.
Bundled audio intelligence, motion features, and optional voice triggers work locally. Ordinary audio windows and fusion state expire instead of becoming a remote activity log.VERIFY
Independent evidence must agree.
SafeCity looks for audio–motion agreement across time and retrieves reviewed suppressors such as media playback, transport vibration, or a dropped phone.CHECK IN
You get a visible chance to respond.
A tiered state can surface a check-in or a cancelable SOS countdown. The interface explains factors and keeps emergency action within reach.ACT
A confirmed SOS prepares help, not promises.
The app may encrypt limited incident evidence and open the system message composer. You review recipients and content, then press Send.WHY FUSION MATTERS
A shout is not always danger. A dropped phone is not always a fall.
SafeCity deliberately asks independent signals to agree. It also looks for evidence that lowers risk—like television audio or routine transport vibration—before escalating.
Read the model card summaryDECISION BOUNDARIES
What can—and cannot—escalate.
This simplified matrix describes the current policy intent. Pilot thresholds are not field-certified accuracy claims.
Cannot ordinarily auto-SOS by itself
A fall alone cannot ordinarily auto-SOS
Supporting evidence only
Requires agreement across windows
Exceptional configured path
AFTER SOS CONFIRMATION
A small encrypted record. Nothing continuous.
Evidence capture is a separate, confirmed workflow. Mobile operating systems prevent background apps from silently opening cameras.
RAM tail
The latest 15 seconds of audio exists only in volatile memory before confirmation.
Protected capture
While the capture screen is visible, the app can collect front/rear photos and post-SOS audio.
Local encryption
Evidence is AES-GCM encrypted and temporary plaintext capture files are deleted.
Your action
You choose whether to open a message, share evidence, or delete the incident.
TRUST THROUGH TRANSPARENCY
Know the limits before you rely on a tool.
The architecture is private by design, but no phone can promise detection or response. See the constraints SafeCity makes visible.