Privacy and safety
Your kit.
Your data.
This page explains what Survive Link does with local information, device permissions, the public website, and communication features.
Effective October 7, 2026
Website contact forms and launch list
If you submit a contact form, we save your name, email, subject and message in a private support log accessible only to authorized administrators. If you join the launch list, we save your name and email in that same private log and send a welcome email with links to our social profiles; we’ll also notify you when the app is available. We also save our replies and their sending status. We use SendGrid for notifications and replies from info@survivelink.com. This operational log works even when you decline analytics and does not share data with the mobile app. Email replies you send afterward arrive in our mailbox; they are not automatically imported into the website log.
What stays on your device
Your profile, any medical details you choose to save, contacts, plans, checklists, downloaded maps, routes, pins, chats, Survive AI memory, Mesh signing keys, radio configuration, channel keys, and message history are stored locally on your device. Radio configuration and channel keys are not sent to the Survive Link service. The core kit does not depend on an online account or server.
Optional connections from the native app
When you use features that need a connection, place search sends the search text to Nominatim through the Survive Link API; Wikipedia search sends the search text to Wikipedia; route calculation sends the start and destination to OSRM; and weather-alert requests send the requested location to NOAA/NWS for public alerts. The app is not connected to FEMA’s public IPAWS feed. Alerts are supplemental and best-effort; neither NWS nor FEMA endorses Survive Link. Viewing an online map requests map tiles from OpenFreeMap. If you choose to download the optional AI model, the app retrieves its files from Hugging Face when the device has an unmetered internet connection. These requests may reveal connection data such as your IP address to the relevant services, in addition to the feature data listed above. They are made for that feature and do not transmit your private local profile or chats. Third-party services process requests under their own practices; we make no promises about their retention.
Push-to-talk calls
The optional Push-to-talk feature requests microphone access only when you join an active call. Call signaling is sent over WSS to our relay; signaling data is encrypted before it is forwarded. The relay processes channel and participant identifiers plus network metadata such as IP address and connection timing to coordinate calls. Hosting-provider logs and retention depend on the production deployment and provider policies. WebRTC audio uses DTLS-SRTP encryption and connects directly between participants when possible. If a TURN relay is configured and used, it forwards encrypted audio and can observe network metadata. The app does not record or store call audio, but another participant may record it separately.
Permissions and why they are requested
Location is used when you choose maps, navigation, position, or emergency context. Bluetooth and nearby-device access are used to discover nearby Survive Link phones and connect to compatible LoRa radios. The camera is used to scan Family Circle QR invites, by optional sun-orientation tools, and for Morse camera-torch signaling when permission is granted and the device supports it. Notifications are used for local updates you choose to enable. We do not request address-book contacts or background location. The optional Push-to-talk feature requests microphone access only when you join an active call; the app does not record or store call audio. On Android, Bluetooth scanning is declared as not used to infer location.
Nearby phones and LoRa radios
These are two distinct paths. The Nearby phones path exchanges signed messages between compatible Survive Link phones over Bluetooth; it requires the app to be open and does not place emergency calls or contact dispatch centers or our servers. The radio path requires compatible external LoRa hardware; Survive Link connects over Bluetooth and hands text to the radio. Radio configuration and channel keys stay on the device. Range and delivery depend on the devices and network and are not guaranteed. Neither path is an emergency service.
Survive AI and medical content
Survive AI uses the bundled knowledge kit, your local data, and, when installed, an on-device model. The app may provide general field and first-aid information, but it does not diagnose, treat, or replace medical professionals. In an emergency or serious uncertainty, call local emergency services and follow trained responder guidance.
Public website and analytics (web only)
The public website is separate from the native app and does not require an account. First-party website analytics run only if you choose to allow them in the privacy control and may record the viewed path, referrer, a random session identifier, and basic interaction events. To estimate country, the server checks the connection IP against a local MaxMind GeoLite2 database and retains only the two-letter country code; it does not store the IP. The estimate may be inaccurate and is not a precise location. These website records are not native-app analytics. Field AI examples are static, use public product FAQs, and do not accept questions or process visitor data.
Website contact messages
If you submit the form, your name, email, subject, and message are sent to info@survivelink.com through an email delivery provider. The message text is not saved in the website database. To limit abuse, the site temporarily stores a keyed hash of the network address and a request counter, and periodically removes old entries; it does not store the raw IP address in that table. The email provider processes the message to deliver it and applies its own retention practices. Social links take you to external platforms with their own policies.
Creator inquiries
If you submit the creator form, we store the information you provide —such as your name, email, channel, audience size, and proposal— in the website database so we can review your inquiry. Only authenticated administrators can view these inquiries; they are not shown publicly or included in website analytics. Email info@survivelink.com to request access, correction, or deletion.
Free app and external purchases
Every mobile app feature is free. Optional gear is purchased on third-party sites, which process payments under their own practices. Survive Link does not receive payment information for those purchases.
Cookies, storage, and your controls
The site uses browser storage to remember your language and privacy choice. We do not sell personal information. We share it only with providers that help operate the site or deliver messages you request, under their own practices. We do not use advertising cookies. The admin dashboard session cookie is necessary, HttpOnly, and not issued to public visitors. See the Cookie Policy and use Privacy settings to change your choice.
Rights and requests
Depending on your location, you may request access, correction, deletion, restriction, or objection to website data processing. You may also withdraw analytics consent. Email info@survivelink.com for a privacy request; we may ask for reasonable information to verify it.
Retention and deletion
Delete the app’s local account and personal data from Profile > Delete local account and personal data. See the account deletion page for what is erased and what remains. The account is not remote; clearing or uninstalling the app also removes its local app data. We do not state retention periods for third-party services or website records.
Changes and contact
We will post policy changes on this page. This page describes the current product behavior and is not legal advice. For product support or privacy questions, email info@survivelink.com.