Privacy Policy
Crisis Connect is an offline-first emergency communication platform designed to enable individuals and communities to stay connected during disasters and network outages. The App operates primarily through Bluetooth communication technologies, allowing users to exchange messages, location data, and status information without relying on cellular networks or the internet. Your privacy is extremely important to us. This Privacy Policy describes how Crisis Connect collects, uses, stores, and protects information. We encourage you to read this document carefully, especially if you intend to use the App during emergency scenarios. By installing or using Crisis Connect, you agree to the terms described in this Privacy Policy.
Contents
Offline Security
SOS signals are encrypted end-to-end. Your location is only shared when you trigger an emergency.
2. Information We Collect
Crisis Connect is built to function with minimal data collection, prioritizing user safety, device performance, and privacy. The App may collect the following categories of information:
2.1. Bluetooth Device Information
To enable peer-to-peer communication, the App may access: Device Bluetooth name, Device MAC address (hashed or masked when required by operating system rules), Signal strength (RSSI) for proximity estimation, Nearby Bluetooth device scan results, Custom identifiers exchanged between devices (temporary session IDs). This information is required for device discovery, message routing, and establishing connections between users.
2.2. Messages and Communication Data
The App allows users to send: Text messages, Emergency signals, Status updates, Optional location-based alerts. All messages are stored locally on the device and are never transmitted to external servers unless the user explicitly backs them up or connects to a cloud service. Messages may temporarily exist in Bluetooth buffers until delivered.
2.3. Device Information
For performance, debugging and security we may collect: Device model, Operating system version, App version, Crash logs and error diagnostics, Bluetooth capability status.
2.4. Location Information (Optional)
Crisis Connect may request access to location services because: Bluetooth scanning on Android requires “Location Permission”, Certain features (e.g., map view, emergency location sharing) depend on geolocation. Location is never collected or stored unless the user directly sends a location message to another device. We do not retain or transmit continuous GPS data.
2.5. Firebase Hosting (Website Only)
The official Crisis Connect website is hosted through Firebase Hosting, which may automatically log: IP address, Browser type, Basic analytics. These logs are used only to improve website performance. They are not linked to App usage.
3. How We Use Information
We use collected information solely to provide, maintain, and improve the App. This includes:
- Enabling Bluetooth-based communication
- Routing messages between devices
- Ensuring device compatibility and identifying technical issues
- Improving safety, reliability, and stability during disasters
- Providing optional features such as location-sharing or user profiles
- Conducting performance analysis on a strictly anonymous basis
Crisis Connect does not use personal data for advertising, commercial profiling, or sale to third parties.
4. Offline-First Design & No Server Dependency
Crisis Connect is intentionally designed so that: Communication occurs directly between devices, Messages do not pass through central servers, Offline mode functions independently of internet availability. This ensures safety, privacy, and resilience in disaster scenarios.
5. Data Storage & Retention
We prioritize local storage and user control.
5.1. Local Storage
All messages, logs, and settings are stored locally on the device. Data remains until the user deletes it manually, clears app storage, or uninstalls the App.
5.2. No Long-Term Server Storage
We do not store conversations, personal identity data, location history, contact lists, or Bluetooth connection logs. Unless explicitly added in future versions (and only with clear user consent).
7. Security Measures
We take privacy and security seriously. Crisis Connect uses:
- Encrypted data transfer (where supported by device hardware)
- Secure Bluetooth protocols
- Internal sandboxing of message history
- No internet-based tracking
- Randomized identifiers for communication sessions
- Best-practice Android/iOS permissions architecture
Despite these measures, users should be aware that Bluetooth communication may have inherent risks depending on device and OS limitations.
8. User Rights
You may: Access the data stored on your device, Delete your entire message history at any time, Disable Bluetooth scanning, Revoke permissions (Bluetooth, Location, Notifications), Uninstall the app to permanently erase all stored data. Because the app does not collect server-based profiles, we do not offer account deletion requests.
9. Children’s Privacy
Crisis Connect is not specifically designed for children under 13. However, because the App operates offline and does not create user accounts, it does not knowingly collect personal information from minors. Parents or guardians concerned about usage can delete the App from the device at any time.
10. Changes to This Privacy Policy
We may update this Privacy Policy to reflect improvements, new features, or legal requirements. If significant changes occur, we will notify users through: The App interface, Official website, or App store release notes. Continued use constitutes acceptance of updated terms.
11. Contact Information
For questions, feedback, or privacy concerns, you may contact us:
Auralis Inc., Privacy Office
Privacy Office
12. Summary (For Emergency Contexts)
We do not store your chats on servers. Your data stays on your device only. Bluetooth is used for direct device-to-device communication. Location is optional and not stored without your action. Privacy and resilience are core principles of Crisis Connect.
13. SOS Feature Security
The SOS system is designed specifically for real-world disaster scenarios with enhanced security protocols.
13.1. Purpose of the SOS System
Allows users to broadcast an emergency distress message, notify nearby devices, and request rescue. Strictly intended for disaster environments.
13.2. Encryption Protocols
Crisis Connect uses multi-level encryption: (a) Message-Level Encryption: AES-256 and ephemeral keys. (b) Identity Token Encryption: Hardware-backed key storage. (c) Signature Verification: Public-key signatures to prevent forgery.
13.3. Anti-Spoofing and Misuse Prevention
To prevent false alarms, we implement rate limiting, device fingerprint checks, and replay-attack protection.
13.4. Emergency Location Handling
If attached, location is encrypted and retained only until the rescue process ends. It is not stored continuously.
13.5. Offline Identity Verification
During disasters without internet, we rely on pre-generated offline cryptographic profiles and short-range authentication.
13.6. Data Retention for SOS
SOS messages are stored only on sender’s and receiver’s devices. No cloud upload. All data can be deleted.
13.7. Sharing of SOS Information
Shared only with nearby connected users and authorized responders. No commercial sharing.