RU-Alive Logo RU-Alive?

Privacy Policy

Last Updated: August 31, 2026
Entity: WhiteCap Associates, LLC
Application: RU-Alive?

WhiteCap Associates, LLC ("we," "us," or "our") respects your privacy and is committed to protecting it through our rigorous compliance with this policy. This Privacy Policy outlines how WhiteCap Associates, LLC handles information within the RU-Alive? application. Because our utility does not host accounts, logins, or process any data on the Cloud or on-premises servers, this policy specifically details how your device locally analyzes and calculates sensor data, and what limited information (pre-written text and optional GPS location) is dispatched to your designated contacts only if an automated SMS message is triggered by user-defined settings.

In addition, this policy is designed to comply with the Google Play User Data Policy, the Apple App Store Privacy Guidelines, and standard commercial telecommunications compliance frameworks.

1. Nature of the Application (Automated Inactivity Notification System & Utility)

Important Notice: RU-Alive? is an on-device Automated-Notification-System (ANS) based on user-set inactivity thresholds, or a prolonged stationary state of a user's smartphone. This app accesses and measures standard hardware device sensors to verify physical movement of the user's phone, or verifies their phone is stationary from the device's hardware. This app is explicitly NOT a personal safety device, a medical device, a rescue tool, or a replacement for a call to 911 (emergency services). This app cannot guarantee physical safety or initiate emergency services.

All sensor information is processed 100% on your device in order to facilitate the app's technical HW analysis, automated SMS messaging and location services. Our external servers exist strictly to send silent background (APNs) wake-ups to Apple devices, and never collect, transmit, or store any user data.

2. Information Evaluated On-Device and How It Is Used

We operate on a strict zero-server data collection architecture. We only request, access, and process the exact data necessary directly on your smartphone to perform the core functions of the App: evaluating device movement, checking battery status, and dispatching automated notifications.

A. Motion and Activity Data (Core Function)

  • Hardware Accessed On-Device: Accelerometer and Gyroscope data (movement activity).
  • Purpose: The App monitors this hardware data in the background strictly to determine if the device has remained still beyond your user-set time window.
  • Privacy Standard: This data is processed 100% on your physical device. We do not build profiles of your daily habits, we do not monitor fitness metrics, and we never transmit this data to external servers.
  • Retention: On-device motion records are evaluated and overwritten in real-time. We do not maintain or store a historical log of your movements.

B. Device Status Information (Low Battery Feature)

  • Status Accessed On-Device: Battery level percentage and device power state.
  • Purpose: To trigger an automated "Low Battery" SMS notification to your designated contacts if the device power crosses a critical threshold (e.g., below 5%).
  • Privacy Standard: This status is monitored directly on the device in the background. We do not track, collect, or store your battery usage history.

C. Designated Contact Information

  • Information Input On-Device: Names and telephone numbers of the specific individuals you choose as "designated contacts."
  • Purpose: To route automated SMS/Text message notifications if the App detects prolonged stillness or a critically low battery.
  • Privacy Standard: We absolutely do not collect, harvest, sell, or store your contacts' information on our servers. This data remains safely locked on your phone and is used strictly by your device's native SMS dispatcher.

D. Location Data

  • Hardware Accessed On-Device: Precise or Coarse Location (GPS/Network).
  • Purpose: To include a single, real-time location link within the outbound SMS notification sent to your designated contact, providing situational awareness.
  • Privacy Standard: Location data is accessed strictly on your physical phone only when an alert is actively triggered or during initial setup. We do not continuously track, map, collect, or log your geographical movements to our backend.

3. Device Permissions Requested

To function properly, the App requires the following native operating system permissions to process sensor data locally. You may revoke these at any time via your device settings, which will inherently prevent the App from functioning.

  • iOS: NSMotionUsageDescription (to detect physical movement natively) and NSLocationAlwaysAndWhenInUseUsageDescription (to append location coordinates to outgoing alerts). Note: Users must select "Allow Always" to successfully append location data if an SMS is triggered in the background.
  • Android: ACTIVITY_RECOGNITION (to detect physical movement natively), ACCESS_FINE_LOCATION (to append location coordinates to outgoing alerts), and SEND_SMS (to facilitate outbound text notifications via your cellular provider).

4. Data Sharing and Disclosure

Because we operate a zero-collection architecture, there is no personal data to sell, trade, or rent. Information is routed strictly in the following circumstances:

  • To Designated Contacts: Pre-written text messages and optional location links are dispatched directly from your device to the emergency contacts you configure.
  • iOS Background Maintenance: The only task our external servers execute is a generic, automated ping to wake the iOS app in the background every 6 hours. This connection transmits zero personal data and does not collect or store user information.
  • Legal Compliance: If strictly required by law or court order.

5. SMS Compliance

Automated alerts are generated and dispatched directly from your device using your native cellular plan, and standard message and data rates may apply. As the user, you are responsible for ensuring the individuals you add to your designated contacts list consent to receiving these critical check-in texts. To stop alerts, you must manually remove the contact from your in-app configuration.

6. Data Security

Your configuration data never leaves the device's local storage. Security is handled entirely natively by your smartphone's operating system (iOS or Android) sandbox, meaning your personal information cannot be breached via external server hacks.

7. Data Retention and Deletion

We do not maintain user accounts, require logins, or host cloud databases. Your designated contact numbers, stillness limits, and local motion logs are saved solely on your physical device.

  • Right to Delete: You maintain 100% control over your data. To permanently delete all App configurations and local logs, simply uninstall the RU-Alive? application from your smartphone.

8. Children's Privacy

Our App is explicitly not intended for children under 13 years of age. Because our utility functions entirely on-device and collects zero personal information, we inherently do not solicit, harvest, or store data from children under 13.

9. Changes to Our Privacy Policy

We may update our Privacy Policy periodically. We will clearly notify you of any structural changes by posting the new Privacy Policy on our website and updating the "Last Updated" date at the top of this document.

10. Contact Us

If you have questions or concerns about this Privacy Policy or our data practices, please contact us at:

Email: support@ru-alive.com
Mailing Address:
WhiteCap Associates, LLC
P.O. Box 4866
Ketchum, ID 83340
Phone: (208) 450-3250