SafeStream Privacy Policy
Effective Date: November 15, 2026
Company / Developer: Redu LLC d/b/a SafeStream ("SafeStream," "we," "us," or "our")
Contact: support@safestream.company | +1 (314) 312-3016
1. Scope
This Privacy Policy explains how SafeStream collects, uses, shares, stores, and protects information when you use the SafeStream mobile app, the SafeStream Contacts mobile app, our website, and related services (the "Service"). Section 2A explains exactly what SafeStream Contacts collects and shares. Where Section 2A is more specific than the rest of this Policy for SafeStream Contacts, Section 2A governs.
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.
2A. SafeStream Contacts
SafeStream Contacts is a separate app, available in the countries listed in the Country Supplement below, that helps you reach the people you choose by text message. It never contacts emergency services, police, or a monitoring center, and it does not share any information with our safety, monitoring, or dispatch partners. The parts of this Policy about arming, dispatch, monitoring, live-streaming, Bubbles, emergency history, practice sessions, medical information, Apple Health, the Sound mode safe-word, trigger sounds, and purchases describe features SafeStream Contacts does not have.
What SafeStream Contacts collects
Your phone number, to sign you in. We verify it with a one-time code sent by text message through our authentication provider.
Your name, if your SafeStream account has one. SafeStream Contacts does not ask for a name. If your account already has one (for example, one you set in the SafeStream app), it appears in the alert text your contacts receive; otherwise the text says "A SafeStream Contacts user".
Your safety contacts: the name, phone number, and alert language of each person you add. You must have their permission before you add them.
Your PIN. When you set or change your PIN, it is sent to our servers over an encrypted connection, where we store it as a salted, irreversible cryptographic hash and also in encrypted form. We never show your PIN to anyone and never include it in an alert. When you enter your PIN during a countdown, your phone checks it against the stored hash; the PIN you type there is not sent to us.
Your location, only when an alert starts. When an alert starts, the app reads your phone's current location, or its last known location if the current one is not available, and sends it to our servers to create your location link. SafeStream Contacts does not track your location in the background and does not collect your location at any other time.
An alert record. Each time an alert starts, we store a record of when it started, what started it (Alert Now, a wrong PIN, or the countdown ending; leaving the countdown screen while the countdown is running is recorded as Alert Now), how many safety contacts it was prepared for, and a reference to its location link. The record does not contain your contacts' names or numbers or the text of the message.
Device, technical, and usage data, as described in Sections 3.C and 3.G.
What stays on your phone
Video recordings. Video you record in SafeStream Contacts is saved only on your phone. It is never uploaded to SafeStream and is never attached to your alert. It leaves your phone only if you choose to share it, for example with your phone's share sheet, and then it goes only to the app or person you choose. If your phone backs up app data (for example to iCloud or a computer), recordings may be included in that backup, under your backup provider's terms.
The alert text message. The app prepares the message on your phone and opens it in your phone's messaging screen, addressed to your active safety contacts. The message is sent from your own phone, as a text message through your own mobile carrier or as an iMessage if your phone sends it that way, only when Send is tapped. SafeStream never receives or stores the message itself.
Your battery level, which is read on your phone and placed in the alert text. It is not sent to us.
Who can see what
Your safety contacts see what is in the text message you send them: the name on your account (if it has one), the coordinates of your location, a map link, your location link, the time, and your phone's battery level. They can forward it to anyone.
Anyone who has your location link can see the location it shows, without signing in, until the link stops working. The link stops working about 24 hours after it is created, or sooner if a new alert replaces it. The link does not show your name, phone number, or contacts.
Map providers. The map link in the text opens in whatever map app or website the reader uses, and that provider receives the coordinates in the link when it is opened. When your location link is shown on our map page, the reader's browser loads map images from a third-party map tile service, which receives the map area being viewed but not your name or phone number.
Our service providers, such as hosting, storage, and authentication providers, process this information on our behalf as described in Section 6.A.
If you have no active safety contacts when an alert starts, no text message is prepared and no location link is created; only the alert record is stored.
How long we keep it
Safety contacts are kept until you remove them or delete your account.
Your PIN hash and encrypted PIN are kept until you change your PIN or delete your account.
Alert records are kept until you delete your account.
Location links stop working about 24 hours after they are created. The location a link showed is deleted from our records within about a day after the link stops working, and when you delete your account.
Video recordings stay on your phone until you delete them. Deleting your SafeStream Contacts account does not delete recordings on your phone or copies you have shared.
When you delete your account, we delete the information above that we hold within 30 days, as described in Section 7.
Permissions SafeStream Contacts may request
Location, while you are using the app, to include your location in an alert
Camera and microphone, to record video on your phone (with sound, if you allow the microphone)
Contacts, only if you choose to pick a safety contact from your phone's address book; the app reads your address book on your phone to show the list, and only the contact you pick is saved to your account
SafeStream Contacts does not currently send app notifications.
Where your information is processed
SafeStream is based in the United States. If you use SafeStream Contacts in any listed country, the information we hold about you is stored and processed in the United States and in other countries where our service providers operate. We protect it as described in this Policy wherever it is processed. If you use SafeStream Contacts in India, the Netherlands, Germany, or Australia, this means your information leaves your country and is hosted in the United States.
Your rights and the Country Supplement
You can ask to access or correct the personal information we hold about you by emailing support@safestream.company, and you can ask us to delete your account at any time by emailing the same address. If you are not satisfied with how we handle a privacy request or complaint, you can contact the regulator for your country listed below.
SafeStream Contacts is available in the countries listed in this Country Supplement. Where this Supplement conflicts with the rest of this document for a listed country, the Supplement governs for people in that country.
If you live in Germany, you can find the contact details for the data protection authority of your state (Land) in the Federal Commissioner for Data Protection and Freedom of Information's (BfDI) list of state authorities: https://www.bfdi.bund.de/DE/Service/Anschriften/Laender/Laender-node.html.
Country
Emergency numbers
Regulator
Your rights
India
112
Data Protection Board of India
Email support@safestream.company to access, correct or delete your data; you may also complain to Data Protection Board of India.
Netherlands
112
Autoriteit Persoonsgegevens
Email support@safestream.company to access, correct or delete your data; you may also complain to Autoriteit Persoonsgegevens.
Germany
112 (fire and ambulance), 110 (police)
the data protection authority of your German state (Land)
Email support@safestream.company to access, correct or delete your data; you may also complain to the data protection authority of your German state.
Australia
000 (Triple Zero), 112 also works from a mobile
Office of the Australian Information Commissioner (OAIC)
Email support@safestream.company to access, correct or delete your data; you may also complain to Office of the Australian Information Commissioner.
European Union and European Economic Area (including Liechtenstein, Norway, and Iceland)
Legal basis. Under the GDPR we process your information to provide SafeStream Contacts to you, which is the contract between us, and on the basis of your consent for the location you choose to share in an alert. You can withdraw consent at any time by stopping alerts or emailing us. You can also ask us to restrict or object to processing, ask for a copy of your information in a portable format, and complain to your national data protection authority listed below.
Transfers. Your phone number is processed by Google, our sign-in provider, and your information is held by us in the United States, since SafeStream is a United States company. We do not rely on the EU-U.S. Data Privacy Framework for this processing: the Framework covers transfers of data from an EU-based entity to a Framework-certified United States recipient, not information you send directly to a United States company like us. Where a transfer safeguard applies, we use the standard contractual clauses approved by the European Commission.
India
This section applies if you use SafeStream Contacts in India. It is our notice under the Digital Personal Data Protection Act, 2023 and its rules.
What we process and why. We process the personal data listed in Section 2A under "What SafeStream Contacts collects": your phone number, the name on your account if it has one, your safety contacts' names, phone numbers and alert languages, your PIN in hashed and encrypted form, your location when an alert starts, your alert records, and device and technical data. We use it for one purpose: to sign you in and to let you alert the people you choose, with your location, when you ask. We do not sell your personal data.
Your consent. Before you create an account, the app shows you this information and asks for your agreement. Your consent covers only the purpose above. Before you add a safety contact, you must have their permission.
Withdrawing consent. You can withdraw your consent at any time, as easily as you gave it: tap Delete account on the app's home screen, or email support@safestream.company. We then stop processing your personal data and delete it as described in Section 7, unless a law requires us to keep it. Withdrawing does not affect processing that happened before.
Keeping a registration record after you delete your account. If you delete your SafeStream Contacts account, we keep your phone number, the date your account was created and the date it was deleted for 180 days after deletion, because the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021 require it. We use this record only for that legal duty and then delete it.
Your rights. You can ask us for a summary of the personal data we hold about you and how we process it, ask us to correct, complete, update or erase it, and nominate another person to exercise these rights for you if you die or become unable to. Email support@safestream.company.
Grievance Officer. Cullen Harris, Founder, Redu LLC d/b/a SafeStream. Email support@safestream.company with the subject "Grievance", or use the contact details in Section 13. We acknowledge every grievance within 24 hours and resolve it within 7 days of receiving it.
Data breaches. If a personal data breach affects you, we will tell you without delay and report it to the Data Protection Board of India within 72 hours of becoming aware of it.
Children. SafeStream Contacts is not for anyone under 18, as described in Section 10.
Complaints to the Board. If you are not satisfied with how we resolve your grievance, you can complain to the Data Protection Board of India.
Where your data goes. Your personal data is stored and processed in the United States, as described under "Where your information is processed" above.
3. Information We Collect
We collect information in the following ways.
A. Information You Provide Directly
This may include:
Account and contact information, such as your phone number and sign-in details
Profile information, such as your first and last name, home address, city, date of birth, profile photo, and other profile fields you choose to add
Emergency contact information, such as names, phone numbers, and relationship details for people you choose to add
Medical and safety information, such as allergies, conditions, medications, notes, mobility or disability-related information, or other safety details you choose to provide
Communications, including support messages, feedback, survey responses, and other communications you send us
User content, such as notes, recordings, images, video, audio, or other materials you upload or transmit through the Service
Your Safety PIN. When you set or change your PIN, we store it two ways: as a salted, irreversible cryptographic hash, and as an encrypted copy. We keep the encrypted copy so that we can send your PIN to Noonlight with an alarm and use it to cancel an alarm with Noonlight on your behalf.
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:
Video, photos, and live-streamed or uploaded media
Video from an armed Camera or Live Stream session that you stand down with no alarm, kept for 30 days (see Section 7)
Audio recordings or live audio
Precise location data, including GPS or other location signals, while a safety incident or related session is active
Alarm, monitoring, session, and status data, such as timestamps, session state, countdowns, check-ins, camera or monitoring events, and related incident metadata
Verification and security-event data, such as PIN-related confirmations or cancellation requests associated with incident features
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.
Bubble members can save places (such as "Home" or "School") that are visible to your whole Bubble. If you share your location with a member, they are notified when you arrive at or leave a saved place, and when you said you would be there by a set time and are not there (a no-show). These alerts are notifications only and do not contact emergency services. We do not check your arrival, leave, or no-show at saved places while you share at approximate precision. If you share your location with members of your Bubble, we also share your phone's battery level with those members along with each location update, and it is shown on the map.
When you invite a phone number that has no SafeStream account, we keep a hashed form of that number, and the invite, for 90 days so the invite can be shown if the person signs up. We send that number nothing. If the person does not sign up within 90 days, we delete the invite.
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. 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 Sound mode 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. Your safe-word is stored only on your phone and does one thing: it stops a running Sound mode listener hands-free. Sound mode also offers an optional safe-phrase, a separate codeword that can stand down an alarm that Sound mode started. You enter it in a text field in the app, by typing or by dictating with your phone's own tools such as iOS Voice Control; SafeStream never records audio for this. So that the stand-down can be verified by our servers, the words you entered are sent to SafeStream over an encrypted connection and checked against a salted, irreversible cryptographic hash of the safe-phrase you chose. We store that hash, never the phrase itself, never a recording, and never a voiceprint. Unlike your Safety PIN, we keep no encrypted copy of your safe-phrase. The safe-word and safe-phrase work only in Sound mode and nothing else. They are 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 Sound mode (such as an alarm or appliance beep), the audio you record is stored only on your device and is never uploaded. To let Sound 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.
If you use Siri or Shortcuts to start a session, Apple handles your voice request; SafeStream receives only the command. When you start a livestream this way while your phone is locked, SafeStream sends your location and your sign-in token to our servers to start the session and keeps sending your location while the session runs.
C. Device, Technical, and Usage Data
We may collect:
Device identifiers and technical details
Device model and operating system version
App version and language settings
Time zone and IP address
Information about your interactions with the Service
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:
Subscription status
Entitlement status
Transaction identifiers or receipt status
Product identifiers
Optional one-time tip purchase status
We do not receive your full payment card number from Apple or Google when purchases are made through their billing systems.
If you buy a SafeStream membership on our website, our payment processor, Stripe, handles your payment and collects your card details and the email address you enter for your receipt. We receive your membership status, plan, renewal and end dates, whether a charge was refunded or disputed, and that email address, which we use only to send you emails about your membership, such as renewal reminders, yearly notices, and notices of price changes. We keep a copy of each of those emails in our support mailbox. We do not receive your full payment card number. Stripe's privacy practices are described at https://stripe.com/privacy.
If someone else pays for your SafeStream membership on our website, Stripe collects the payer's card details and email address, and we receive the payer's email address, the plan, the membership status, renewal and end dates, and whether a charge was refunded or disputed. The payer sees only your first name, which you choose to show when you create the payment link; the payer never sees your phone number, email, or location. You never see the payer's email address or card details. We use the payer's email address only for the receipt, renewal reminders, price-change notices, cancellation and refund messages, and the notice that the membership ended.
E. Information From Third Parties
We may receive information from third parties that support the Service, such as:
Noonlight, Inc. (our safety, monitoring, and dispatch partner)
Authentication providers
App store platforms
Payment processors
Cloud and storage providers
Safety, monitoring, or dispatch partners
Analytics, communications, and support vendors
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:
Events such as feature opens, mode tests, paywall views, subscription purchases, and similar in-app actions
Summary metrics for completed safety sessions, such as jog duration and bucketed distance ranges (for example, "1–2 km" rather than precise meter-level distance), used to understand product usage without revealing precise routes
General device and app information (model, OS version, app version, language)
General region (country or calling code), taken from your sign-in phone number prefix or your app store country
A pseudonymous identifier we set after sign-in (your Firebase user ID), so we can analyze user journeys without tying events to your name, phone number, or email
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.
H. Our Website
This section covers our website only. Section 3.J covers how the SafeStream app measures installs from our ads.
When you open our ad landing page (the page our social media ads link to, which forwards you to the App Store), the page loads the Meta Pixel, a small piece of code provided by Meta Platforms, Inc. It sends Meta a record that the page was viewed, together with information your browser sends with any web request: your IP address, your browser and device type (user agent), the time of the visit, the website address the visit came from, and any Meta cookies your browser allows to be sent. Meta may connect this with the ad it showed you and with information it already holds, for example if you are logged in to Facebook or Instagram. We use it only to count how many people who tap our ads actually reach the page and to help Meta show our ads to people likely to be interested. Through the pixel, we do not send Meta your name, phone number, email, location, or anything from the SafeStream app. Apart from the ad click cookie described under "Buying on our website" below, our landing page does not set its own cookies. Meta's use of this information is governed by Meta's Privacy Policy at https://www.facebook.com/privacy/policy.
The same landing page also loads the Reddit Pixel, a small image provided by Reddit, Inc. It sends Reddit a record that the page was visited, together with information your browser sends with any web request: your IP address, your browser and device type (user agent), the time of the visit, and any Reddit cookies your browser allows to be sent. Reddit may connect this with the ad it showed you and with information it already holds, for example if you are logged in to Reddit. We use it only to count how many people who tap our Reddit ads actually reach the page and to help Reddit show our ads to people likely to be interested. Through the pixel, we do not send Reddit your name, phone number, email, location, or anything from the SafeStream app. Reddit's use of this information is governed by Reddit's Privacy Policy at https://www.reddit.com/policies/privacy-policy.
The landing page also passes a short campaign tag (the name of the ad you tapped) to the App Store, so Apple can tell us how many downloads each ad produced. Apple reports these counts to us only in aggregate; we cannot see who downloaded.
Other pages of our website, including our main site, our checkout pages, and the page used to watch a live stream you have been sent, do not use the Meta Pixel or the Reddit Pixel.
When someone watches a live stream you have been sent, their browser loads map images from a third-party map tile service, which receives the map area being viewed but not your name or phone number.
Buying on our website. When our website sells SafeStream memberships, the following also applies.
Ad click cookie. If you arrive on our website from one of our ads, our server sets one cookie that holds the ad click identifier Meta adds to the ad's link. Scripts on our pages cannot read this cookie, and it expires 7 days after the click. We do not set it if your browser sends a Global Privacy Control or Do Not Track signal.
Purchase report to Meta. If you then buy a membership on our website, our server tells Meta that a purchase was completed, with the price and currency, the ad click identifier, your IP address, your browser and device type (user agent), the time, and the checkout page's web address without any added details. We do this once, for your first purchase only, so we can measure which ads lead to memberships. We do not send Meta your name, email, phone number, payment card details, or SafeStream account ID, and we do not report renewals. We delete the ad click identifier as soon as the report is sent, and in any case 7 days after the click.
When we send nothing. We send Meta nothing about your purchase if your browser sends a Global Privacy Control or Do Not Track signal, if there is no ad click identifier, or if the checkout was opened from inside the SafeStream app.
Phone sign-in on the checkout page. Our checkout page asks for your US phone number and sends a code by text message, using the same Google Firebase sign-in the SafeStream app uses, so the membership is tied to your SafeStream account. To do this, that page loads Google's sign-in and bot-check (reCAPTCHA) scripts. Google receives your phone number, IP address, and browser information to send the code and to block automated abuse, and its scripts may set their own cookies. Google's privacy practices for Firebase are described at https://firebase.google.com/support/privacy.
Payment. Your payment is handled by Stripe, as described in Section 3.D. Meta never receives your payment details.
Your choices: if your browser sends a Global Privacy Control or Do Not Track signal, our landing page does not load the Meta Pixel or the Reddit Pixel, and our website does not set the ad click cookie or report a purchase to Meta. You can also limit how Meta uses information from websites for ads in your Facebook or Instagram settings under Accounts Center, Ad preferences. You can block third-party cookies in your browser settings, which Safari does by default. You can also opt out of interest-based advertising from participating companies at https://optout.aboutads.info.
I. Sensitive Data
Some information described above is considered sensitive under state privacy laws: precise location, health and medical information (including allergies, conditions, medications, and mobility or disability-related information), and consumer health data. We process sensitive data only to provide the safety features you choose to use, such as sending your location and medical notes to dispatch during an incident you start, and to protect life and physical safety. You give permission through your device's permission prompts and by choosing to enter this information or turn on these features in the app, and you can withdraw it at any time by turning off the permission or feature or deleting the information. We do not sell sensitive data and do not use it for advertising. Our Consumer Health Data Privacy Policy at https://sites.google.com/view/safestreamhq/consumer-health-data-privacy gives more detail.
J. App Install Measurement
The SafeStream app uses AppsFlyer, a mobile measurement service, to learn which of our ads lead people to install the app and subscribe.
What the app reports. The app tells AppsFlyer about four things only: that the app was installed, that it was opened for the first time, that you signed up, and that you started a subscription. The install and the first open are reported together, after you create your account and accept this Privacy Policy. If you created your account before we added AppsFlyer, the app sends AppsFlyer nothing. The sign-up and subscription reports carry no details, such as your plan or the price. A report can be sent later than the moment it describes, because the app holds reports as described below.
What AppsFlyer receives. With each report, AppsFlyer receives information your phone sends with any internet connection, such as your IP address, which AppsFlyer also uses to estimate your general area, such as your city or region. It receives basic device and app details, such as your device model, operating system version, language, and app version, and the time the app was opened. It also receives two identifiers: one that AppsFlyer creates for this installation of the app, and one that Apple or Google gives our apps on your device (on iPhone, the identifier for vendor, called IDFV; on Android, the app set ID). These are not advertising IDs, and apps from other companies cannot read them.
What it does not receive. We do not send AppsFlyer your SafeStream account ID, name, phone number, or email. The app is built to hold these reports while Sound mode or any other safety session is running, and while a safety screen is open, and to send them afterward. The reports carry nothing from your safety sessions, such as video, audio, the location the app collects for safety features, your PIN, your emergency contacts, or your medical information.
No tracking prompt and no advertising ID. The app does not ask for permission to track you. On iPhone, the app does not use the iOS Advertising Identifier (IDFA). Results of our iPhone ads are measured in two ways: through Apple's SKAdNetwork, which reports ad results to advertising networks without identifying you, and by AppsFlyer, which uses statistical methods to estimate how many installs followed our ads and gives the advertising networks campaign totals. On Android, the app does not use your device's advertising ID; AppsFlyer reads the Google Play install referrer, a tag Google Play gives the app at install that shows which ad, if any, led to the install.
Who AppsFlyer tells. AppsFlyer may tell the advertising networks we run app install ads on, which today are Meta and Reddit, whether an install, or one of the other reports above, came from one of their ads. A network may connect this with the ad it showed you and with information it already holds, for example if you are logged in to its app. We use this to count which ads lead to installs and subscriptions, and to help the networks show our ads to people likely to be interested. For Meta, AppsFlyer sends this information with Meta's Limited Data Use option turned on, which asks Meta to limit how it uses information about people in the states that Meta's Limited Data Use terms cover. We will update this list before we add a network.
How long AppsFlyer keeps it. AppsFlyer keeps these records for up to 24 months. They are not linked to your SafeStream account, so deleting your account does not delete them. Section 9 explains how to ask.
Sharing under state law. Some state laws, including California's, treat this as "sharing" personal information for cross-context behavioral advertising, or as targeted advertising. Section 9 explains how to opt out.
Apps that do not use it. The SafeStream Contacts app and the SafeStream Apple Watch app do not use AppsFlyer.
AppsFlyer's privacy practices are described at https://www.appsflyer.com/legal/privacy-policy/.
4. Permissions We May Request
Depending on the features you use, SafeStream may request access to:
Camera: to capture, stream, or upload video or photos
Microphone: to capture, stream, or upload audio
Location: to provide your location during an incident or related safety feature, and, if you turn on Bubble location sharing, to share your location with the members of your Bubble you opt in with on an ongoing basis, including in the background ("Always" location access)
Photos / Media / Storage: to save or upload media you choose to share
Notifications: to deliver alerts, reminders, or status updates
Speech Recognition: to detect your chosen safe-word on your device for hands-free control of Sound mode (processed entirely on-device)
Contacts: only if you choose to pick an emergency contact from your phone's address book; the app reads your address book on your phone to show the list, and only the contact you pick is saved to your account
Face ID or fingerprint: to confirm it is you when you reset your Safety PIN; your phone performs the check, and SafeStream learns only whether it passed
You can choose not to grant permissions, but some features may not work properly. You can also change permissions later in your device settings.
Livestreaming with your screen off. A livestream you start keeps running until the session ends, even if your screen turns off or you switch apps.
On Android, your camera, microphone and location may keep running while your screen is off or SafeStream is in the background. Android shows a notification while this is happening. If your phone limits it, SafeStream keeps what it can (audio and location, or location only, or nothing if you have not allowed location) and tells you afterward what kept running. If you swipe that notification away, SafeStream stops keeping your camera and microphone running in the background for that session; your location may keep updating.
On iPhone, your camera and microphone pause while SafeStream is in the background and resume when you come back to the app. Your location keeps updating.
5. How We Use Information
We use information to:
Provide, operate, and maintain the Service
Authenticate users and secure accounts
Run safety features, incidents, monitoring, or dispatch-related workflows you initiate
Stream, upload, store, or share media and location in connection with incidents or other requested features
Communicate with emergency contacts, support channels, or third-party safety partners as needed to deliver the Service
Provide customer support and respond to questions or requests
Improve reliability, performance, quality assurance, and product development
Detect, investigate, and prevent fraud, abuse, misuse, or security issues
Comply with legal obligations and enforce our agreements
Measure and improve our advertising, as described in Section 3.H (our website) and Section 3.J (app installs)
Ask you for optional feedback about the Service, including if you cancel a membership
We do not collect, use, or sell personal data to train large language models.
6. How We Share Information
We do not sell your personal information for money. We do give limited information to advertising partners to measure and improve our ads. Some state laws, including California's, call this "sharing" personal information for advertising, and some may call it a "sale". The SafeStream app uses AppsFlyer to tell the advertising networks we run app install ads on, which today are Meta and Reddit, which of their ads led to app installs, sign-ups, and subscriptions, as described in Section 3.J. Our ad landing page uses the Meta Pixel and the Reddit Pixel, which let Meta and Reddit receive information about your visit to that page to measure and improve our ads. When our website sells memberships, our server also reports a first website purchase to Meta, as described in Section 3.H. See Sections 3.H and 3.J for what is sent, and Section 9 for how to opt out.
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, payment processing, 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 also receives the name shown on each member's map pin and, to show where you are on the map, your own current location from your device. It does not receive members' 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.
To record the county you were in when you open the app or start a safety mode, your phone turns your coordinates into an address using your phone's own geocoding service (Apple's or Google's). For sessions started from an Apple Watch, our server instead sends the watch's coordinates to the United States Census Bureau's public geocoding service. These services receive only the coordinates.
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, your Safety PIN, date of birth, home address, and profile photo, other 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 you stood down before an alarm was created, are not shared. This sharing is user-to-user only, is off by default, and requires your separate consent for each person. 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, 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 the practice alarm goes to our dispatch partner's test system, not to its live dispatch service. 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:
Comply with law, regulation, legal process, or governmental request
Protect the rights, property, or safety of users, third parties, or the public
Investigate or prevent fraud, abuse, or security issues
Enforce our Terms or other agreements
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 for money.
7. Data Retention
We retain information only for as long as reasonably necessary for the purposes described in this Policy, including to:
Provide and support the Service
Maintain safety and operational records
Comply with legal, tax, accounting, audit, and regulatory obligations
Investigate fraud or misuse
Resolve disputes and enforce agreements
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 invite a phone number that has no SafeStream account, we keep a hashed form of that number, and the invite, for 90 days so the invite can be shown if the person signs up. We send that number nothing. If the person does not sign up within 90 days, we delete the invite.
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.
If you arm a Camera or Live Stream session and stand it down with no alarm, the recording is kept for 30 days so you can review it in the app, then deleted. You can delete it sooner in the app. It is not shared with your Bubble or with our dispatch partner.
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 you bought a membership on our website, or someone else pays for it, deleting your account cancels it, and we remove the link between your SafeStream account and your billing records. If someone else pays, we email that person once to say the membership ended because the account was closed. Your billing records, the payer's billing records, and the record of the terms accepted at checkout stay with our payment processor, Stripe, for as long as tax and consumer protection laws require.
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.
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:
Access and update certain profile information in the app
Manage permissions in your device settings
Pause or stop Bubble location sharing, choose per person who sees you, or leave a Bubble, at any time in the app; leaving or being removed deletes your location history for that Bubble
Turn emergency history sharing on or off for each member of your Bubble at any time in the app; turning it off removes your incidents from the listings shown in their app
Request deletion of your account and associated data through the app or by contacting us at support@safestream.company
Manage or cancel subscriptions through the applicable app store account settings
Your privacy rights. Wherever you live in the United States, you can ask us to:
Confirm whether we process your personal data, and give you access to it, including a copy in a portable format
Correct inaccurate personal data
Delete your personal data
Opt out of the sale or sharing of your personal data, targeted advertising, and profiling that produces legal or similarly significant effects
To make a request, email support@safestream.company and include the phone number on your SafeStream account so we can verify the request. We respond within 45 days. If we need more time, we will tell you why within that period and take no more than 45 additional days. Requests are free, and we will not treat you differently for making one. Where the law allows, an authorized agent may make a request for you.
Appeals. If we decline your request, in whole or in part, we will tell you why. You can appeal by emailing support@safestream.company with the subject line "Privacy appeal". We will respond in writing within 60 days and explain what we decided and why. If we deny your appeal, you can contact your state Attorney General. Connecticut residents can submit a complaint at https://portal.ct.gov/AG/Common/Complaint-Form-Landing-page.
We do not sell personal information for money, and we do not use or disclose sensitive personal information for purposes other than those permitted by applicable law.
Sharing for advertising. We "share" personal information, as California law uses that word, for cross-context behavioral advertising. Other state laws may treat it as targeted advertising or as a sale. We do it in two places:
In the app: the AppsFlyer reports described in Section 3.J. The categories are identifiers (your IP address, the identifier AppsFlyer creates for your installation of the app, and the identifier Apple or Google gives our apps on your device), device information, and app activity (install, first open, sign-up, and subscription start). They go to AppsFlyer and, through AppsFlyer, to the advertising networks we run app install ads on, which today are Meta and Reddit.
On our website: the Meta Pixel, the Reddit Pixel, and the first-purchase report to Meta described in Section 3.H. The categories are identifiers (your IP address, cookies, and the ad click identifier), browser and device information, and website activity (a visit to our ad landing page, and a first website purchase with its price and currency). They go to Meta and Reddit.
How to opt out of this sharing.
On our website: turn on Global Privacy Control or Do Not Track in your browser. Our website then does not load the Meta Pixel or the Reddit Pixel, does not set the ad click cookie, and does not report a purchase to Meta. Section 3.H lists other choices.
In the app: open Settings and turn on "Do not share for advertising". The app then stops sending reports to AppsFlyer from that phone. The same screen shows your AppsFlyer install identifier. To ask us to delete reports already sent, email support@safestream.company with the subject "Do not share" and include that identifier. We will reply within 45 days.
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@safestream.company
+1 (314) 312-3016