INGEK S.A.S. · Android and iOS
SISMOX Privacy Policy
Updated November 4, 2026. INGEK S.A.S. operates SISMOX. For privacy questions, write to gerencia@ingeksas.com.
What the app does
SISMOX lets you view seismic information and contribute motion measurements from your phone. On Android, you choose whether to enable the Guardian mini-node. In the Android update that adds the nearby channel, access to its public or private radio and message mesh requires Guardian to be enabled with its background permissions prepared. Movement does not block that access; stillness only determines which Guardian measurements are valid. In iOS builds that include the public channel, you can enter it without granting location access, adding an emergency contact, or enabling Guardian. If you complete operational activation on iOS, Auto Guardian arms automatically while the app is open; its background operation depends on permissions and iOS limits. Rescue offers status features, help, and manual SOS; compatible builds also offer nearby communication. Rescue is free at this stage. SISMOX does not predict earthquakes, does not issue official alerts, and sending an SOS does not confirm that a rescue agency has received it.
Rescue's nearby public channel, where available
When you open the nearby public channel in a compatible build, SISMOX automatically searches for nearby compatible phones using Bluetooth and Wi-Fi. Any compatible device may join the public channel; SISMOX does not verify participants' identities or locations. Messages you choose to send may be relayed through nearby phones, while voice sent by holding Talk is attempted to only one direct neighbor per turn. Delivery is not guaranteed.
The public channel uses nearby-device or local-network permissions to discover and connect phones; it requests microphone access to talk. It does not send your GPS location or an SOS, contact emergency services, or automatically send voice or message content to the SISMOX API. In compatible versions, a voluntary report can send only the content you expressly select, as described in this policy’s reporting section. Messages and relay queues are handled temporarily in memory; each message expires for relaying after 60 seconds. SISMOX does not create a voice recording file for this channel. Other participants may copy or retain what they receive, and SISMOX cannot remove it from their devices. Guardian and manual SOS are separate features that may send data to the API when active.
In Android builds with the nearby channel, Google Play services Nearby Connections may collect technical discovery, connection, and transfer metrics, as well as the device model, country, device version, and app package, according to its documentation. Users can control this collection under Google Settings > Usage & diagnostics.
Voluntary nearby-communication reports in compatible versions
In versions that offer Report, this action is optional and separate from SOS and ordinary public or private channel traffic. After reviewing the preview, expressly choosing what to share, and consenting, you can send the SISMOX service a text excerpt of up to 500 characters, a note of up to 500 characters, the category, content type, channel mode, report identifiers, and dates. A key fingerprint is included only if one exists; a public session does not verify a person’s identity or authorship, and its fingerprint may be null. Audio, GPS location, photos, contacts, and conversation history are not attached. A report about voice contains only the note you write, without a recording or audio excerpt. Review the excerpt and note: they may contain personal information you choose to include.
The app stores at most 50 pending reports, encrypted on the device, for up to 30 days; it keeps local receipts for up to 120 days. It may retry sending when a connection is available. A pending report, a prepared email, or an offline attempt does not mean receipt. Only a valid server confirmation that matches the report allows the app to show Received; that acknowledgment does not mean review, sanction, or remote blocking. Availability depends on a compatible version and service: this policy alone does not confirm that the reporting service is active. No response time in hours is promised.
If you already have an installation credential, the report uses that authorization. If you participate as a guest, a compatible service can issue, with your consent, a credential limited to your reports, without creating a personal account or seismic node. Credentials are held in the device’s protected storage. The server uses a pseudonymous HMAC-protected sender identifier; it does not treat a public session as a verified identity. Only authorized operators can access report content.
Open cases are retained until a review decision. After closure, the excerpt, note, and key fingerprint are deleted after 30 days; the decision record is deleted 120 days after closure. Authenticated deletion removes your reports from the active store: for a registered installation it is part of deleting that device, and guests have a separate deletion process limited to their own reports. The app claims remote deletion only after a valid server confirmation; clearing local pending reports or uninstalling does not prove remote deletion. After guest deletion, a revocation digest without report content may remain until the credential expires, at most 180 days after issuance, to prevent its reuse. Backups follow their separate cycle and are not immediately rewritten. Read the deletion steps.
Data we process
- Location: with permission, SISMOX may use precise or approximate location, including in the background when Guardian is active or while your manually activated Trapped SOS keeps tracking until you stop it, to place measurements, filter nearby information, and support emergency features. Some queries and saved places are rounded to 0.01 degrees; other emergency features may need greater precision. Location is not used for advertising.
- Measurements and device: motion and vibration summaries, time, signal quality, device type, battery, charging, and mini-node operational status.
- Identifiers and notifications: a pseudonymous installation identity, device credential, and notification token (Firebase Cloud Messaging on Android or APNs on iOS, depending on the platform) if you enable notifications. You do not need to create an account with a name or email to use the app.
- Rescue: the status or request you choose to send, associated location, report text, and photos you voluntarily attach. Contacts you add to prepare messages remain on your device; if you choose to share a message, the app passes its content to the app you select.
- Operations and diagnostics: technical logs, errors, and delivery results needed to protect, maintain, and evaluate the service.
Purposes and recipients
We use this data to operate the mini-node, evaluate seismic signals, show nearby information, deliver notifications, process reports and requests, prevent duplicates, and resolve failures. Linkable node, report, and SOS data is restricted to authorized services and personnel. Public network summaries are aggregated. SISMOX infrastructure and technical providers, including Firebase Cloud Messaging on Android and APNs on iOS for notifications, process data needed for these functions. A messaging app or external contact receives only the content you choose to share. We do not sell personal data or display ads.
Permissions and control
On Android, you choose whether to enable or pause the Guardian mini-node in the app. In the update that adds nearby radio and messages, those functions check Guardian consent and readiness: precise and background location, notifications, unrestricted battery, and the manufacturer-setting confirmation where applicable. Pausing Guardian or revoking a required permission closes those radio and message sessions until setup is restored. The radio channel itself does not use your GPS; those location permissions support Guardian and separate features such as SOS. Granting all permissions cannot guarantee continuous measurement: Android or the device maker may suspend the service. Movement does not block the nearby channel.
In iOS builds with the nearby public channel, you may enter it without completing operational activation, granting location access, or adding an emergency contact. To use SOS, private rooms, and connected services on iOS, you must complete setup and the corresponding permissions; once you accept, Auto Guardian remains enabled in the app without a separate pause control. On both platforms you can change location, Bluetooth or nearby-device, local-network, microphone, and notification permissions in your phone's Settings, as applicable. The app explains background location use before requesting it. Where available, the nearby public channel does not require the mini-node to be measuring; manual SOS requires its own setup but may remain available when the mini-node is not measuring, subject to permissions and connectivity. Other Rescue actions may depend on mini-node setup and validation. Delivery of requests to the server depends on connectivity and server confirmation.
Retention and deletion
Operational data has different retention periods. In the server configuration verified on October 6, 2026, node and vibration records were purged after 2 days, statuses after 30 days, location contexts after 14 days, and audit records after 90 days, also subject to count limits. Rescue reports and photos, installation identifiers, and certain security logs have no confirmed general automatic deletion. Voluntary nearby-communication reports have the separate retention periods described in their section. Recovery copies follow operational rules and are not immediately rewritten after a deletion. These periods may change with configuration and applicable law; we revise this page when practices change.
From the app, you can request authenticated deletion of data attributable to your installation. Records covered by that process are removed from the primary store. After confirmation, the app starts local cleanup. If the operating system does not complete it, some data may remain on the device until removed through system controls or with support assistance. This does not immediately delete backups, derived seismic data, shared records, de-identified audit records, or messages already delivered to third parties. See how to request deletion.
Security and changes
Communication with the server uses HTTPS; access to linkable data is controlled by an installation credential or administrative authorization. No measure guarantees zero risk. If our data practices change, we will update this policy and its date. Contact: gerencia@ingeksas.com.