Aviso de privacidad

Política de privacidad

Esta Política de privacidad explica cómo gestiona Crisis Connect la información cuando usas la aplicación móvil, el sitio web público y las funciones relacionadas de coordinación de rescate. Distingue dos contextos principales: el uso habitual por parte de usuarios de funciones de comunicación local cercana y los flujos opcionales en línea o de coordinación de rescate autorizada. Esta distinción importa porque la mensajería principal está diseñada para funcionar sin una cuenta de nube identificada, mientras que ciertas funciones de soporte, perfil, mapas, diagnósticos y rescate dependen de Firebase y servicios relacionados. Las personas con sesión iniciada y los usuarios institucionales también pueden usar mensajería por internet y llamadas de voz o video opcionales; esas funciones se describen por separado a continuación.

Última actualización: 16 de julio de 2026

Contenido

Primero sin conexión, no solo nube

Los chats cercanos principales permanecen en los dispositivos; la mensajería y llamadas por internet opcionales, el inicio de sesión, diagnósticos, sincronización de rescate y descargas de mapas pueden usar servicios en línea.

1. Información que procesamos

La información que procesamos depende de las funciones que uses. Algunos datos permanecen solo en tu dispositivo, otros se intercambian directamente con dispositivos cercanos y otros se envían a servicios en la nube cuando están activadas funciones en línea.

1.1. Anonymous Service Identity, Optional Sign-In, and Rescue Accounts

For ordinary civilian users, core nearby messaging does not require a named cloud profile, and civilian chat names or private contact identities are not saved to our servers as a public chat account. When online support is available, the app may create an anonymous Firebase identity in the background to initialize limited online capabilities. We do not treat every installation as a fully registered user account. Google or email-password sign-in is optional for most users and is mainly relevant when you choose profile-linked features or when an organization, field team, admin panel, or authorized rescue workflow requires authentication. In those cases, we may process your Firebase user ID, sign-in method, email address, display name or username, country, role, verification status, and related agency metadata.

1.2. Local App Data

Messages, contact entries, locally stored encryption material, profile photos, attachments, offline map regions, settings, and similar app content are primarily stored on your device. In ordinary civilian nearby messaging, message history and named chat profiles are not mirrored to a centralized message server.

1.3. Device, Connectivity, and Nearby Device Data

To operate Bluetooth and nearby communication features, the app may process device capabilities, Bluetooth and Wi-Fi Aware state, nearby device discoveries, signal strength, temporary session identifiers, device model, operating system version, app version, language, and country settings.

1.4. Media, Location, and Sensor Data

If you use optional features, the app may process voice recordings, photos, QR scans, shared location messages, live location for rescue coordination, and sensor-derived data used by tools such as compass, signal finder, or map-related features. Location is processed only when a feature requires it or when you choose to share it.

1.5. Diagnostics, Analytics, and Website Logs

We use Firebase and Google services for crash reporting, performance monitoring, analytics, app integrity checks, authentication, and website hosting. These services may process technical telemetry such as app instance identifiers, device and app metadata, error logs, performance traces, IP address, browser details, and related diagnostic events.

1.6. Rescue Coordination Data

If authorized rescue features such as Crisis Link are enabled, the app may sync responder identity and authorization metadata, device identifiers, agency details, active signal observations, optional GPS snapshots, and related operational metrics to Firestore or connected backend services so authorized teams can coordinate field activity.

1.7. Internet Messaging Data

If you use optional internet messaging features, such as institutional or cross-agency channels available to signed-in users, message content, voice messages, and attachments are end-to-end encrypted on your device before they are sent. Encrypted message payloads are relayed and stored through our servers and Firebase services, including Firestore and Firebase Storage, so they can reach offline recipients and stay in sync across authorized participants; we cannot read end-to-end encrypted content. To route and deliver these messages we also process conversation and delivery metadata such as sender and recipient identifiers, channel identifiers, timestamps, delivery state, encryption key-management and group-membership data, and device push tokens used for notifications.

1.8. Internet Voice and Video Call Data

If you use internet voice or video calls, including screen sharing, call audio and video streams are encrypted in transit and are not recorded or stored by us. To establish and maintain calls we process signaling and session metadata such as caller and callee identifiers, call state, timestamps, and duration, together with the network information, including IP addresses, needed to connect devices. When a direct connection is not possible, encrypted call media may be relayed through TURN relay infrastructure operated by our service providers, which processes IP addresses and transport metadata to provide the relay.

2. Permisos del dispositivo

Crisis Connect solicita permisos que corresponden a las funciones que eliges usar:

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.

3. Cómo usamos la información

Usamos la información únicamente para operar, proteger, brindar soporte y mejorar Crisis Connect y los servicios relacionados. El uso exacto depende de si utilizas funciones locales estándar o funciones restringidas en línea o de rescate. Los usos adicionales incluyen:

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.

No vendemos contenido de mensajes ni información personal, y no usamos el contenido de chat para publicidad.

4. Diseño sin conexión como prioridad y funciones conectadas a la nube

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.

5. Almacenamiento y conservación

La conservación depende de dónde residen los datos y de las funciones que uses.

5.1. Local Retention

Messages, attachments, contacts, local keys, settings, profile images, and offline maps generally remain on your device until you delete them, clear app storage, replace them, or uninstall the app.

5.2. Cloud and Service-Provider Retention

Account records, end-to-end encrypted message payloads and attachments stored for delivery and sync, call and delivery metadata, rescue-authorization metadata, responder coordination data, crash reports, analytics events, performance traces, and website or server logs may be retained by us or our service providers for as long as needed to operate the service, investigate incidents, comply with law, or satisfy provider retention windows.

7. Medidas de seguridad

Usamos salvaguardas técnicas y organizativas por capas apropiadas para un producto de comunicación de emergencia:

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.

Ningún sistema de transmisión o almacenamiento es absolutamente seguro. Bluetooth, Wi-Fi, la seguridad local del dispositivo y los servicios conectados a internet conllevan riesgos inherentes.

8. Tus opciones y derechos

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. To erase your account and the cloud data attached to it, open Profile in the app and use “Delete account and data”: it deletes your account, profile, contact-directory entries, encryption keys, notification tokens and undelivered messages, and wipes the chat history on that device. If you no longer have the app installed you can request the same erase at crisisconnect.network/delete-account. One category survives deletion by design: emergency (SOS) signals you sent are retained as a rescue record, because a field team may still be responding to one — deletion removes the account identifier from them, so what remains is an anonymous incident (location, time, status) that can no longer be traced back to you. In-app deletion is immediate; requests made on the web are completed within 30 days, and encrypted backups roll off within 90 days. For access or correction of cloud-held data, contact us.

9. Privacidad de menores

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.

10. Cambios en esta Política de privacidad

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.

11. Información de contacto

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

Auralis Privacy Team

Equipo de privacidad

privacy@crisisconnect.network

12. Resumen de uso en emergencias

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.

13. Tratamiento de funciones SOS y rescate

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

13.1. Local Emergency Broadcasts

The SOS feature can broadcast distress information to nearby devices so other users or responders can detect an emergency event even when normal infrastructure is unavailable.

13.2. Location and Status Data

If you attach location or status information to an SOS event, that information is processed to support response and may be displayed to nearby devices or authorized rescue systems involved in that workflow.

13.3. Responder Authentication

Restricted rescue tools may rely on signed role credentials, token claims, or related authorization checks before giving access to protected coordination functions.

13.4. Operational Retention

Local SOS content remains on participating devices unless a connected rescue workflow uploads related observations. Authorized rescue sync records may remain in backend systems for incident coordination, audit, or legal purposes.

13.5. Misuse Prevention

We may use technical controls such as authorization checks, rate limits, integrity checks, and incident logging to reduce false alerts, abuse, or unauthorized rescue access.