Legal Document Center

Crash Detection & SOS Policy

Effective: June 1, 2026Last updated: May 30, 2026

This Crash Detection & SOS Policy ("Safety Policy") governs LifeHub's Crash Detection features, SOS features, emergency notifications, safety alerts, and related functionality.

This Policy forms part of the LifeHub Terms of Service, Privacy Policy, Family Location Sharing & Consent Policy, and all other applicable LifeHub policies.

1. Purpose

LifeHub provides certain safety-related features designed to help users notify members of their Circle when specific events occur.

These features are intended to facilitate communication among family members and trusted contacts.

LifeHub's safety-related features are supplemental convenience tools only and are not emergency response services.

2. Definitions

Crash Detection

"Crash Detection" refers to any LifeHub feature that attempts to identify a possible vehicle collision, impact event, or accident using information such as:

  • Device sensors;
  • Motion data;
  • Speed data;
  • Location information;
  • Accelerometer readings;
  • Gyroscope readings;
  • User interactions; or
  • Other available information.

SOS Feature

"SOS Feature" refers to any feature that allows a user to manually initiate an emergency alert or safety notification to Circle members or designated contacts.

Safety Alert

"Safety Alert" refers to any notification generated by LifeHub relating to a possible emergency, crash, SOS activation, or other safety-related event.

Circle Member

A Circle Member is an authorized member of a LifeHub Circle who may receive notifications, alerts, or communications generated through the Services.

3. How Crash Detection Works

Crash Detection relies upon automated systems and available device information.

Crash Detection may analyze:

  • Motion patterns;
  • Changes in speed;
  • Impact events;
  • Device movement;
  • Travel behavior; and
  • Other available signals.

Crash Detection is inherently imperfect and should not be relied upon as a guaranteed method of detecting accidents.

LifeHub does not guarantee that:

  • Every crash will be detected;
  • Actual crashes will be identified correctly;
  • False alerts will not occur;
  • Alerts will be transmitted successfully; or
  • Alerts will be received by intended recipients.

4. How SOS Features Work

SOS Features allow users to manually initiate alerts to members of their Circle.

When activated, LifeHub may attempt to transmit information such as:

  • User identity;
  • Location information;
  • Time of activation;
  • Device information;
  • Alert status; and
  • Other available safety-related information.

Transmission of an SOS alert depends upon factors including:

  • Internet connectivity;
  • Cellular coverage;
  • Device status;
  • Operating system permissions;
  • Application settings;
  • Battery availability; and
  • Third-party service availability.

LifeHub cannot guarantee successful delivery of any SOS alert.

5. What LifeHub Does Not Do

LifeHub is not:

  • A 911 service;
  • An emergency dispatch center;
  • A public safety agency;
  • A law enforcement agency;
  • A medical provider;
  • An ambulance service;
  • A roadside assistance provider;
  • A security provider;
  • A travel assistance provider;
  • A monitoring center; or
  • An emergency response organization.

LifeHub does not:

  • Monitor emergencies in real time;
  • Contact 911 on behalf of users;
  • Dispatch police officers;
  • Dispatch firefighters;
  • Dispatch emergency medical services;
  • Dispatch roadside assistance providers;
  • Dispatch security personnel;
  • Monitor user safety twenty-four hours per day; or
  • Guarantee emergency assistance.

Users should always contact local emergency services directly when emergency assistance is required.

6. Alert Delivery Limitations

Safety Alerts may fail to function properly for many reasons, including:

  • Poor cellular coverage;
  • Internet outages;
  • GPS failures;
  • Device malfunctions;
  • Application crashes;
  • Battery depletion;
  • User settings;
  • Operating system restrictions;
  • Notification permissions being disabled;
  • Third-party service interruptions;
  • Hardware failures; or
  • Other circumstances beyond LifeHub's control.

Accordingly, LifeHub makes no guarantee that:

  • Alerts will be generated;
  • Alerts will be transmitted;
  • Alerts will be received;
  • Alerts will be viewed;
  • Alerts will be acted upon; or
  • Assistance will be provided.

7. Circle Member Responsibilities

Circle Members are independent users and are not agents, employees, contractors, representatives, or emergency responders acting on behalf of LifeHub.

LifeHub does not control:

  • Whether a Circle Member receives an alert;
  • Whether a Circle Member views an alert;
  • Whether a Circle Member responds to an alert;
  • How a Circle Member responds; or
  • Whether assistance is ultimately provided.

Users acknowledge that Circle Members may:

  • Be unavailable;
  • Ignore notifications;
  • Fail to receive notifications;
  • Misinterpret notifications; or
  • Be unable to provide assistance.

8. User Responsibilities

Users remain responsible for:

  • Maintaining device functionality;
  • Keeping applications updated;
  • Maintaining battery charge;
  • Enabling necessary permissions;
  • Configuring Circle memberships appropriately;
  • Reviewing safety settings;
  • Contacting emergency services directly when needed; and
  • Exercising independent judgment during emergencies.

Users should never rely exclusively upon LifeHub when responding to emergencies.

9. Location Information During Emergencies

Safety-related alerts may include location information.

Location information may be:

  • Delayed;
  • Inaccurate;
  • Incomplete;
  • Unavailable; or
  • Incorrectly reported.

Location information should be treated as informational only.

LifeHub does not guarantee the accuracy of any location information associated with Safety Alerts.

10. False Positives and False Negatives

Crash Detection and SOS systems may generate:

False Positives

Events reported as emergencies that are not actual emergencies.

Examples may include:

  • Dropped devices;
  • Sudden stops;
  • Sports activities;
  • Device mishandling;
  • Sensor errors; or
  • Software errors.

False Negatives

Actual emergencies that are not detected or reported.

LifeHub makes no representation that false positives or false negatives can be eliminated.

11. Future Safety Features

LifeHub may introduce additional safety-related features in future releases.

Examples may include:

  • Emergency contact management;
  • Medical information sharing;
  • Enhanced crash detection;
  • Family safety dashboards;
  • Additional emergency notifications; or
  • Other safety-related functionality.

Nothing in this Policy obligates LifeHub to provide any specific safety feature.

Any future feature may be modified, suspended, limited, or discontinued at any time.

12. Limitation of Liability

To the fullest extent permitted by law, LifeHub shall not be liable for:

  • Failure to detect a crash;
  • False crash detections;
  • Failure to transmit alerts;
  • Delayed alerts;
  • Undelivered alerts;
  • Inaccurate location information;
  • Failure of Circle Members to respond;
  • Failure of emergency assistance to arrive;
  • User reliance upon Safety Alerts;
  • Injury;
  • Property damage;
  • Death;
  • Emotional distress;
  • Economic loss; or
  • Any consequences arising from use or non-use of Crash Detection or SOS Features.

Users assume all risks associated with use of LifeHub's safety-related features.

13. Changes to This Policy

LifeHub may modify this Policy from time to time.

Updated versions become effective upon posting unless otherwise stated.

Continued use of Crash Detection, SOS Features, or other safety-related functionality constitutes acceptance of the revised Policy.

14. Contact Information

Questions regarding this Policy may be directed to:

ProOps Technologies LLC

7901 Blacktail TrailMcKinney, Texas 75070

Email: support@golifehub.app

Phone: (888) 912-9103