Back to Home
DocumentationPrivacy PolicyTerms & ConditionsSecurity PolicyAbout

REDP!NG Privacy Policy

Current public overview of REDP!NG privacy practices

Privacy Policy

REDP!NG Privacy Policy

Last Updated: May 8, 2026

This policy describes the current public privacy position for REDP!NG as reflected by the active website and the referenced redping_14v mobile application workspace. REDP!NG is a safety communication and coordination platform focused on mobile SOS workflows, emergency contacts, location-aware incident handling, and SAR coordination features.

REDP!NG is not an emergency service provider. In a life-threatening emergency, contact your local emergency number first.

1. Scope of this policy

This policy applies to the REDP!NG public website and the current mobile app workflows that are publicly described on the site.

The website currently reflects the iOS and Android mobile experience. Feature availability can vary by permission settings, subscription entitlements, deployment stage, organization onboarding, device support, and regional conditions.

2. Information REDP!NG may collect

REDP!NG may collect the following categories of information, depending on the feature you use and the permissions you grant:

  • Account details such as name, email address, phone number, and authentication identifiers.
  • Emergency profile information such as emergency contacts and optional safety or medical context you choose to provide.
  • Location data for supported workflows including current location, last-known location fallback, and active SOS session location updates.
  • Emergency session records such as SOS activations, timestamps, status changes, responder coordination events, and related logs.
  • Messaging and communication records for supported emergency and SAR messaging workflows.
  • Device, app, and diagnostic data such as device type, app version, crash logs, notification state, and service health information.
  • Sensor and motion data when advanced safety features such as crash or fall detection are enabled and supported by the device and operating system.
  • Payment or entitlement-related records when subscription and billing features are active in the environment you use.

3. How REDP!NG uses information

REDP!NG may use collected information to:

  • Create and manage user accounts.
  • Power SOS activation, countdown safeguards, alert delivery, and emergency session tracking.
  • Notify trusted contacts and support supported responder or SAR workflows.
  • Provide mapping, location sharing, and last-known-location fallback behavior where implemented.
  • Operate secure messaging, notification delivery, and offline-aware communication flows.
  • Enforce feature access, subscriptions, roles, and organization permissions.
  • Review service health, reliability, misuse, incidents, and platform quality.
  • Meet legal, safety, operational, and compliance obligations.

4. When REDP!NG may share information

REDP!NG may share relevant information in limited cases such as:

  • With your trusted contacts during an SOS or related safety workflow.
  • With participating SAR organizations, responders, or organization administrators when needed for supported incident coordination workflows.
  • With third-party infrastructure or service providers that help operate authentication, notifications, secure storage, mapping, payments, analytics, or platform delivery.
  • When required by law, lawful request, or urgent safety need.
  • During security review, abuse prevention, fraud investigation, or platform integrity work.

REDP!NG does not claim that all responders, agencies, or partner organizations operate under REDP!NG control. Independent responders and organizations may have their own policies and systems.

5. Permissions, consent, and device behavior

REDP!NG may request permissions such as:

  • Location access for SOS, mapping, responder visibility, and active incident workflows.
  • Motion or activity access for advanced crash and fall detection features.
  • Notification access for alerting, countdown prompts, status changes, and responder updates.
  • SMS or communication-related permissions where those flows are supported and explicitly enabled.

Some emergency behaviors only function correctly when permissions remain enabled and the operating system allows the app to continue running the required workflow.

6. Data retention

REDP!NG may retain information for as long as reasonably necessary to:

  • Operate emergency and responder workflows.
  • Preserve incident history, audit records, and security logs.
  • Support account management, billing, entitlement review, and organization administration.
  • Meet legal, compliance, or operational requirements.

Retention periods can vary by data type, environment, legal obligation, and safety context. Exact retention windows may change as the platform evolves.

7. Security and privacy protections

The current REDP!NG platform direction includes measures such as:

  • Secure authentication and role-aware access control.
  • Encrypted messaging architecture for supported emergency communication flows.
  • Secure local storage and protected backend data handling.
  • Restricted SOS and SAR visibility rather than broad public exposure.
  • Monitoring, logging, and review practices for platform integrity.

No mobile or web platform can guarantee absolute security, uninterrupted availability, or perfect delivery under all network, battery, or device conditions.

8. Your choices

Depending on the workflow and release stage, you may be able to:

  • Review or update profile and emergency contact information.
  • Control permissions such as location, notifications, and motion access at the device level.
  • Disable optional advanced features such as crash or fall detection.
  • Request support regarding privacy or account questions through REDP!NG support channels.

9. Children and sensitive use cases

REDP!NG may be used in sensitive emergency contexts. Users should only provide information that is necessary for safe operation of the requested workflow. Additional safeguards or account-holder responsibilities may apply in family, caregiving, or organization-managed scenarios.

10. Policy updates

REDP!NG may update this policy as the product, legal requirements, permissions model, or deployment architecture change. The latest public version published on the website controls.

11. Contact

For privacy questions, use the REDP!NG contact page or the current support channels published by the website.

This privacy policy is a public website summary and should be read together with the current REDP!NG security policy and terms and conditions.