Current implementation aligned

SOS for the person in danger. SAR for the team coordinating response.

REDP!NG is a two-part emergency coordination platform built around the product that exists now: manual SOS activation, emergency contact alerting, live emergency-session location and status, and verified SAR workflows for authorized responders and organizations.

Manual SOS is the core product path. Optional crash and fall detection remains experimental, device dependent, and secondary to direct user activation.

Official website www.redpingsafety.com

See What Ships Today Privacy Policy Delete Account

SOS core

Manual activation with countdown and cancel

Delivery

Network first, offline queue, carrier SMS fallback

SAR surface

Verification-gated dashboard, lifecycle, and org tools

REDP!NG SOS

Manual SOS with countdown, cancel flow, and active session lifecycle.
Emergency contact management and SMS-based emergency outreach.
Live GPS tracking during active emergencies.
Manual call shortcuts and user-controlled escalation actions.

REDP!NG SAR

Separate SAR app flavor and role-gated experience.
Registration and verification workflows for responders.
Responder actions including acknowledge, assign, en route, and resolve.
Organization dashboard, roster, operations, and area-alert tools.

Website role

Public product explanation grounded in the live app.
Legal and privacy surfaces.
Emergency share-card entrypoints.
No change to SOS or SAR app logic required.

2 app variants SOS and SAR are delivered through separate entrypoints and role-specific routing.

1 primary emergency path Manual SOS remains the main reliable activation method in current production positioning.

Role-gated SAR Responder tools depend on verification state, permissions, and organization context.

Official web domain The public website is aligned for www.redpingsafety.com alongside privacy, account, and emergency-card pages.

What the product actually ships

This site is now aligned to the current app implementation, not speculative product claims. The sections below reflect live user flows, role gating, and feature boundaries present in the repo.

Consumer safety app

REDP!NG SOS

Manual SOS activation One-touch SOS flow with a countdown and cancellation path to reduce false alarms.
Emergency contact coordination Contacts are managed in-app and receive emergency outreach during active SOS workflows.
Live emergency session data Active incidents carry location, timing, status, and responder updates where available.
Offline resilience Delivery is network first, with buffered queueing and carrier SMS fallback when supported.
Android emergency wake behavior Supported Android paths can wake the device, surface the emergency UI, and continue workflow handling subject to OS limits.
Optional experimental ACFD Crash and fall detection exists as an experimental add-on, not the core subscription promise.

Responder coordination app

REDP!NG SAR

Separate SAR app flavor SAR runs through its own entrypoint and routing surface instead of sharing the SOS consumer path.
Registration and verification Responders and organizations move through identity and verification workflows before full operational access.
Live dashboard workflows Authorized teams can monitor active incidents and progress them through acknowledge, assign, en route, and resolve states.
Mission and report surfaces The web/report layer already supports SOS and help-request reporting from live records.
Organization tooling Organization registration, roster management, operations, and area-alert mapping are present in the current build.
Read-only access before full authority Current SAR UX supports monitoring even before all write actions are unlocked by verification.

Operational model

The website needs to describe the handoff correctly. REDP!NG coordinates data and status between users, emergency contacts, and authorized SAR participants. It does not own or operate emergency services.

Emergency flow

Primary trigger Manual SOS is the primary and reliable emergency activation path.
Delivery behavior The app prefers network delivery, then uses carrier SMS fallback and queue replay where conditions allow.
No auto-dial REDP!NG does not automatically call emergency numbers. Users and contacts must call local services manually when possible.
Shared data Active sessions can include location, timestamps, status history, user messaging, and responder metadata.

Responder flow

Visibility Authorized SAR users can monitor active SOS sessions and related help requests from live data collections.
Status lifecycle Current responder flows are based on status changes such as acknowledged, assigned, en route, in progress, and resolved.
Organization context Membership, role, authority, and organization verification determine what a responder can do.
Area control Organization area alerts support hazard, lockdown, restricted access, road closure, and related map workflows.

What this website does not claim

The old website draft included unsupported marketing numbers and certifications. Those are intentionally removed here.

Claims removed

No fabricated performance metrics No 99.7% detection accuracy, sub-200ms dispatch, or user/organization totals are claimed here.
No unsupported compliance badges No FDA, FCC, NIST, Privacy Shield, or emergency-service approvals are claimed unless separately verified and documented.
No ownership of rescue outcomes REDP!NG facilitates emergency coordination; third-party emergency response remains outside product control.

Current platform note

Android is the primary production path Background handling, wake behavior, and experimental ACFD references are centered on supported Android paths.
Feature parity varies iOS and other environments may differ because the current implementation is constrained by platform rules.
Experimental means experimental ACFD and Last Ping are supplementary paths and should not be positioned as guaranteed life-safety automation.

Website role in the current repo

The site layer should stay focused on public explanation, legal pages, account management, and emergency share surfaces. App logic, SOS activation code, and SAR workflow code remain in the mobile codebase.

Public web surfaces

Main website This page explains the current SOS and SAR offering in grounded product language.
Privacy and account support Existing privacy-policy and delete-account pages remain part of the hosted website surface.
Emergency share card The hosted emergency card supports shared incident links and app deep-link handoff.

Protected app surface

No website-driven changes to SOS activation logic Public website work should not alter sensor, SOS, headless activation, or Android foreground-service behavior.
No website-driven changes to SAR authority rules Verification, organization membership, and incident status transitions stay in app and backend workflow code.
Read-only integration preferred If the website consumes live incident data, it should do so through read-only report/dashboard surfaces instead of mutating core emergency flows.

Grounded public presence

Website rebuilt around the current SOS + SAR implementation.

The public story now matches the shipped app: manual SOS, emergency contact alerting, live emergency status, role-gated SAR coordination, and careful language around experimental detection features.

In a life-threatening emergency, contact your local emergency services directly whenever possible. REDP!NG is a communication and coordination platform, not an emergency dispatch operator.