Privacy Policy

The information we process depends on which features you use. Some data stays only on your device, some data is exchanged directly with nearby devices, and some data is sent to cloud services when online features are enabled.

Crisis Connect requests permissions that match the features you choose to use:

• Bluetooth, Nearby Devices, and nearby Wi-Fi permissions are used for local discovery, pairing, messaging, and nearby device communication.
• Location permission is used for Android Bluetooth discovery requirements, optional map and location features, and authorized rescue coordination workflows.
• Camera access is used for QR scanning, taking photos to share in conversations, and video calls.
• Microphone access is used for voice notes, voice messages, and voice or video calls.
• Notification permission is used for incoming messages, incoming calls, SOS activity, ongoing communication services, and download or rescue-status updates.
• Internet and network-state access are used for sign-in, role verification, diagnostics, website delivery, map downloads, internet messaging and calls, and rescue synchronization when those features are available.

We use information only to operate, secure, support, and improve Crisis Connect and related services. The exact use depends on whether you are using standard local features or restricted online or rescue features. Additional uses include:

• Establishing nearby device connections and routing messages or SOS data.
• Storing local history, settings, attachments, and offline resources on your device.
• Authenticating users and determining eligibility for restricted rescue features.
• Syncing responder and signal data for authorized rescue coordination workflows.
• Relaying and storing end-to-end encrypted messages and attachments so internet messaging can reach offline or remote recipients.
• Establishing, connecting, and maintaining internet voice and video calls, including notifying you of incoming calls.
• Monitoring crashes, abuse, fraud, app integrity, and service performance.
• Delivering website pages, downloads, and support channels.

We do not sell message content or personal information, and we do not use chat content for advertising.

Core one-to-one and nearby communication features are designed to work directly between devices and to keep message history primarily on-device. Ordinary civilian users can complete local onboarding and use core nearby communication without creating a named online account, and their normal nearby chat profiles are not saved to our servers. Crisis Connect is not a purely serverless product, however. Anonymous background identity, optional profile sign-in, field-team and admin accounts, role verification, diagnostics, website hosting, offline map downloads, and authorized rescue coordination may use internet-connected services when available. Optional internet messaging and internet calls are online features by design: encrypted message payloads pass through our servers and call traffic may pass through relay infrastructure, while message content itself remains end-to-end encrypted.

Retention depends on where the data lives and which features you use.

We share information only in limited situations relevant to the service:

We use layered technical and organizational safeguards appropriate to an emergency communication product:

• Local encryption and protected storage for sensitive app data on supported devices.
• Cryptographic protections for supported message, identity, and rescue communication paths.
• End-to-end encryption for supported internet messaging channels, so relayed message content is not readable by our servers.
• Encrypted media transport for internet voice and video calls.
• Role-based authorization controls for restricted rescue workflows.
• Firebase App Check, authentication controls, and service-side access rules for supported online features.
• Operational monitoring through crash, performance, and security diagnostics.

No transmission or storage system is absolutely secure. Bluetooth, Wi-Fi, local device security, and internet-connected services each carry inherent risk.

You can manage much of your data directly in the product: review and delete local message history, revoke permissions, remove offline maps, sign out, clear local storage, or uninstall the app. Deleting the app removes local data stored on that device, but may not remove cloud records created for account, diagnostics, rescue coordination, or internet messaging delivery purposes. If you need access, correction, or deletion help for cloud-held data, contact us.

Crisis Connect is not directed to children under 13 and is not intended to be used by minors without appropriate permission where required by law. We do not knowingly design the service to solicit children's personal information for commercial purposes.

We may update this Privacy Policy to reflect product changes, legal requirements, or operational needs. Material changes may be communicated through the app, the website, release notes, or other appropriate notices. The version date above shows when this policy was last revised.

For privacy questions, data requests, or legal concerns about this policy, contact:

At a high level, Crisis Connect handles data differently depending on the workflow.

• Standard users can use core nearby messaging after local onboarding, without creating a named cloud profile.
• Online support features may still use anonymous app identity, map delivery, website hosting, and crash or performance diagnostics.
• Authorized rescue workflows may require authentication, role verification, and backend synchronization for operational coordination.
• Optional internet messaging and calls are end-to-end encrypted; our servers relay encrypted payloads and process delivery metadata, and calls may use relay servers.

Emergency workflows deserve separate notice because they may involve broader operational data handling than standard chat.