SafeStream Privacy Policy

Effective Date: September 19, 2026


Company / Developer: Redu LLC d/b/a SafeStream ("SafeStream," "we," "us," or "our")


Contact: support@redu.company | +1 (314) 252-8931



1. Scope

This Privacy Policy explains how SafeStream collects, uses, shares, stores, and protects information when you use our mobile application, website, and related services (the "Service").

2. What SafeStream Does

SafeStream is designed to help users document and respond to safety situations. Depending on the features you use, SafeStream may allow you to start a safety incident, capture or share video and audio, transmit precise location, notify emergency contacts, and share information with third-party safety, monitoring, or dispatch partners to support requested assistance.

3. Information We Collect

We collect information in the following ways.

A. Information You Provide Directly

This may include:


B. Safety Incident and Feature-Related Data

When you use SafeStream's core features, and depending on your permissions and device settings, we may collect:



If you turn on optional Bubble location sharing, precise location data collected on an ongoing basis (including in the background) while your sharing is turned on, together with related timestamps and status data. Bubble location sharing is off unless you join or create a Bubble and accept the sharing disclosure, and your location is shared only with the members of your Bubble you opt in with. You can choose to display your location to your Bubble at reduced ("approximate") precision; if you do, your Bubble sees only the approximate location. You can pause or stop sharing at any time, which immediately stops sharing your location. When you leave a Bubble or stop sharing, your location history for that Bubble is deleted; while sharing is active we retain only your most recent reported location, so that it can be shown on the map.



Apple Health data read on your Apple Watch is used to display your live workout stats during the jog and, with your permission, to save the completed jog back to Apple Health as a workout. SafeStream does not share Apple Health data with Noonlight or any other safety, monitoring, or dispatch partner, and we do not use Apple Health data for advertising. Aggregated, bucketed summary metrics about completed jog sessions (for example, total duration and bucketed distance ranges such as "1–2 km") may be sent to our analytics provider in pseudonymous form, as described in Section 3.G. We do not transmit raw Apple Health readings (such as individual heart-rate samples) to our servers or to third-party analytics, crash-reporting, or session-replay services.


Apple Health data is processed on your Apple Watch and is not transmitted to SafeStream's servers, to Noonlight, or to any other third party. SafeStream does not transmit Apple Health data to any third-party analytics, crash-reporting, or session-replay service. Our analytics provider (described in Section 3.G below) receives only event names, in-app actions, and pseudonymous identifiers — never Apple Health data.


If you enable the optional Monitor safe-word, listening and recognition happen entirely on your device using Apple's on-device speech recognition: the audio and the recognized text are never sent to SafeStream, Apple, Noonlight, or any other party. So that a spoken stand-down can be verified by our servers, we store a salted, irreversible cryptographic hash of the safe-word you choose — never the word itself, never a recording, and never a voiceprint. This is the same protection we use for your Safety PIN. The safe-word works only in monitor mode: it can stop a running monitor listener hands-free and stand down an alarm that monitor mode started, and nothing else — it is never used to identify you by voice, never shared with Noonlight or your emergency contacts, and never used for analytics.


If you record a custom sound to trigger monitor mode (such as an alarm or appliance beep), the audio you record is stored only on your device and is never uploaded. To let monitor mode recognize your chosen sound, we store a derived acoustic template of your active trigger sound in your account — a compact numeric summary of the sound's frequency pattern and timing; it is not an audio recording and cannot be turned back into one.

C. Device, Technical, and Usage Data

We may collect:


D. Purchase and Entitlement Data

If you make purchases through Apple's App Store, Google Play, or another authorized purchase channel, we may receive limited transaction-related information such as:



We do not receive your full payment card number from Apple or Google when purchases are made through their billing systems.

E. Information From Third Parties

We may receive information from third parties that support the Service, such as:


F. Recorded Calls, Chats, and AI-Assisted Processing

Calls to and from customer support, monitoring agents, dispatch or emergency-response partners, and certain related online chats or communications may be recorded, monitored, transcribed, analyzed, or reviewed by us and our vendors or partners, including through AI-assisted tools, for safety operations, support, quality assurance, internal training, fraud prevention, and legal compliance.

G. Analytics and Product Usage Data

We use Firebase Analytics, a service provided by Google LLC, to understand how users interact with the Service. Firebase Analytics collects pseudonymous, app-level usage information, including:



We use this information to improve the Service, identify bugs, measure subscription performance, and decide what features to build next.


"Other Data" reflected in our App Store privacy label refers to free-text notes you choose to provide in your profile (such as safety notes for dispatchers) and free-text incident details, which don't fit neatly into Apple's defined data categories.


Firebase Analytics does not receive: your phone number, name, email, address, emergency contact details, medical information, video, audio, location coordinates, PIN, or Apple Health data.


We do not use this information for cross-app advertising or tracking. Firebase Analytics in SafeStream operates without the iOS Advertising Identifier (IDFA) and does not require Apple's App Tracking Transparency permission.


Google's privacy practices for Firebase Analytics are described at https://firebase.google.com/support/privacy.

4. Permissions We May Request

Depending on the features you use, SafeStream may request access to:



You can choose not to grant permissions, but some features may not work properly. You can also change permissions later in your device settings.

5. How We Use Information

We use information to:


6. How We Share Information

We do not sell your personal information, and we do not share it with third parties for cross-context behavioral advertising.


We may share information in the following circumstances.

A. With Service Providers and Processors

We use vendors and service providers to help us run the Service, such as hosting, storage, identity and authentication, messaging, analytics, customer support, media processing, transcription, and security providers. These parties may process information on our behalf to provide services to us.


If you use Bubble location sharing, the in-app Bubble map is rendered using the Google Maps SDK, a software component provided by Google LLC that runs inside the app to draw the map. To display the map, the Google Maps SDK receives the map area being viewed and the on-map positions of your Bubble's members at the precision each member has chosen to share (if a member shares approximate location, their exact position never reaches your device, and therefore never reaches the SDK), along with general device and technical information the SDK collects under Google's terms. The Google Maps SDK does not receive members' names, phone numbers, or other profile details, your location history, or any safety-incident data. Google's privacy practices are described at https://policies.google.com/privacy.

B. With Safety, Monitoring, Dispatch, and Emergency-Response Partners

If you initiate a safety incident or use related features, we may share relevant information — including video, audio, precise location, your name and phone number, profile details, emergency contact details, allergies, medical conditions, medications, mobility or disability-related information, and other medical or safety notes you have provided, and incident metadata — with third-party safety, monitoring, dispatch, and emergency-response partners, as well as with any recipients you direct us to notify, in order to provide the assistance or communication you requested.


Our primary safety and dispatch partner is Noonlight, Inc., which provides alarm verification, monitoring, and dispatch services on our behalf. Noonlight may, in turn, use its own service providers (including communications, transcription, hosting, and monitoring-agent vendors) to deliver those services. More information about Noonlight is available at https://www.noonlight.com.

C. With Emergency Contacts or People You Choose to Notify

If you add emergency contacts or choose to share a situation with another person, we may share relevant information with those recipients.


If you join a Bubble and turn on location sharing, we share your location (at the precision you choose) with the members of your Bubble you have opted in with. Nothing is shared with anyone until you opt in with them; a view-only member can see the members who opt in with them but does not share their own location back. While your sharing is paused or stopped, you also cannot view your Bubble's locations. Bubble membership does not add anyone to your emergency contacts, and does not share your information with our safety, monitoring, or dispatch partners; those disclosures happen only as described in Section 6.B when you use incident or dispatch features. When you pause or stop sharing, or leave a Bubble, your Bubble is shown that you stopped sharing; your last location is not displayed as if it were current. The in-app Bubble map is rendered using the Google Maps SDK, as described in Section 6.A.


If you turn on emergency history sharing for a member of your Bubble, we share your emergency incidents with that person, including incidents from before you turned sharing on and incidents that are in progress. The information shared may include the incident video and audio, the live stream while an incident is in progress, your location during the incident, and the time, mode, and status of the incident. Practice sessions and sessions that were stood down are not shared. This sharing is user-to-user only, is off by default, and requires your separate consent for each person. We may notify that person when one of your incidents starts. If you turn sharing off for someone, or they are removed from your Bubble, your incidents are removed from the listings shown in their app; video or other media already delivered to their device, or saved, downloaded, or exported outside the Service, may remain accessible to them. Emergency history sharing does not change what we share with our safety, monitoring, or dispatch partners.


If you turn on practice session sharing, a free feature, we share your practice sessions with the people you choose. A practice session is a non-emergency practice recording: no emergency services are contacted, and practice sessions are not shared with our safety, monitoring, or dispatch partners. This sharing is user-to-user only, is off by default, and requires your separate consent for each person; turning it on for someone includes practice sessions you have already recorded. The information shared may include the practice session video and audio, the time and status of the session, and, if a live practice session is in progress, the live stream. Practice session recordings and their video are automatically deleted 30 days after they are made. If you turn sharing off for someone, or they are removed, your practice sessions are removed from the listings shown in their app; content they already saved or exported outside the Service may remain accessible to them until the underlying recording is deleted. 

D. For Legal, Safety, and Security Reasons

We may disclose information if we believe it is reasonably necessary to:


E. Business Transfers

If we are involved in a merger, acquisition, financing, reorganization, bankruptcy, or sale of assets, information may be transferred as part of that transaction, subject to applicable law. Any successor will be bound by the commitments in this Privacy Policy with respect to previously collected information, including our commitment not to sell personal information.

7. Data Retention

We retain information only for as long as reasonably necessary for the purposes described in this Policy, including to:



Retention periods can vary depending on the type of information and whether it relates to an incident, uploaded content, customer support, security activity, or a legal obligation.


For Bubble location sharing, we retain only your most recent reported location, transiently, while your sharing is active, so that it can be shown on the map; it is deleted when you pause sharing, leave or are removed from a Bubble, or delete your account. We do not retain a breadcrumb or route history of Bubble location sharing.


When you request deletion of your account, we delete the associated personal information we hold within 30 days of verifying your request, except where the law requires or permits longer retention (for example, records of a safety incident subject to a legal hold).


If information has already been shared with third-party safety, monitoring, dispatch, emergency-response, insurance, storage, or other service providers, those parties may retain certain information under their own legal obligations and retention practices.


Practice session recordings (non-emergency practice sessions) and their video are retained for 30 days from the time they are made, then the listing and the underlying recording are deleted. 

8. Security

We use reasonable administrative, technical, and physical safeguards designed to protect information. However, no method of transmission or storage is completely secure, and we cannot guarantee absolute security.

9. Your Choices and Controls

You may be able to:



California residents may exercise rights to access, delete, or correct their personal information by emailing support@redu.company. We do not sell personal information, we do not share it for cross-context behavioral advertising, and we do not use or disclose sensitive personal information for purposes other than those permitted by applicable law.


Deleting your SafeStream account does not automatically cancel an App Store or Google Play subscription. Those subscriptions must be managed separately through the applicable platform.

10. Age Requirement

SafeStream is not intended for individuals under 18, and we do not knowingly collect personal information from anyone under 18. If you believe someone under 18 has provided personal information to us, contact us and we will take appropriate steps to review and delete the information where required.

11. International Transfers

Although certain SafeStream features may be intended primarily for use in the United States, your information may be processed or stored in jurisdictions where our vendors or partners operate. We take steps designed to protect information consistent with this Policy and applicable law.

12. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. We will update the Effective Date above and may provide additional notice in the app or on our website when required.

13. Contact Us

Redu LLC d/b/a SafeStream


2600 Delmar Blvd, St. Louis, MO 63103


support@redu.company


+1 (314) 252-8931