Skoog Rescue — QuakeRescue LifeLink

Privacy Policy for QuakeRescue LifeLink

Effective date: 19 August 2026

1. Summary

QuakeRescue LifeLink does not use advertising, analytics, tracking SDKs, crash-reporting services, or a developer-operated cloud account or backend. The developer does not receive or store the user’s motion data, emergency contacts, rescue-event information, or SMS content.

Most app information is processed and stored locally on the user’s device. Information leaves the device only when required for a user-enabled or user-requested function, as described below. In particular:

• an optional emergency SMS may be sent to contacts selected by the user;
• a rescue-event identifier is broadcast to nearby devices through Bluetooth Low Energy while rescue mode is active;
• location coordinates may be included in a request to the EMSC earthquake service when the app requests earthquakes near the user’s available location; and
• the app retrieves earthquake information from the United States Geological Survey (USGS), the European-Mediterranean Seismological Centre (EMSC), and the Japan Meteorological Agency (JMA); when an earthquake meets the configured magnitude, distance, and age criteria, the five-minute safety countdown starts automatically.

2. Information processed locally on the device

Depending on the functions used and permissions granted, the app may process the following information locally:

Motion-sensor data

When monitoring is active, the app uses the phone’s motion sensors to analyse movement for earthquake-like patterns. Sensor analysis is performed locally on the device. The sensor measurements and analysis results are not sent to the developer.

The app also includes a safe verification function using stored earthquake recordings. This verification is processed locally and is isolated from the real rescue chain. It does not send an emergency SMS or activate the BLE rescue beacon or rescue siren.

Location information

If location permission is granted, the app may obtain and locally retain the last available device location. Location may be used to:

• include available location information in an optional emergency SMS;
• create a Google Maps link in that SMS;
• request recent earthquakes near the available location; and
• assess the relevance of earthquake information to the user’s location.

Location availability and accuracy depend on the device, system settings, permissions, and surrounding conditions.

Emergency contacts and SMS settings

Emergency contact details selected or entered by the user, together with the user’s SMS preference, are stored locally on the device. The app does not upload the user’s address book or emergency-contact list to the developer.

The optional emergency SMS function is disabled by default and requires the user to configure recipients and grant the required SMS permission.

App settings and operational state

The app stores settings and operational information locally, such as language, monitoring state, permission-related settings, reminder state, and other preferences required for the app to function.

Rescue-event identifier

When rescue mode is activated, the app creates a unique identifier for the current rescue event. This identifier is used to match the BLE rescue signal with the optional emergency SMS. It is not intended to identify the user’s civil identity.

3. Information that may leave the device

Optional emergency SMS

If the user has enabled and configured the emergency SMS function, the app may send a message through the device’s mobile network to the recipients selected by the user. Depending on available information, the message may contain:

• an emergency/rescue message;
• available location coordinates;
• a Google Maps link based on those coordinates; and
• the unique rescue-event identifier that matches the BLE beacon.

The message is transmitted by the user’s mobile network operator and received by the selected recipients. The developer does not receive or store the message. Mobile service, device support, permissions, operator conditions, and possible charges may apply.

Bluetooth Low Energy rescue signal

While rescue mode is active, the app broadcasts a named BLE rescue signal, ”SOS Quake”, together with the unique rescue-event identifier. Nearby compatible devices and scanning equipment may detect this signal. The BLE signal does not include the user’s GPS coordinates, emergency contacts, SMS content, or name.

The purpose of this public nearby broadcast is to make the rescue signal detectable. Anyone using compatible BLE scanning equipment within range may be able to observe the signal and identifier.

Nearby-earthquake requests

When the app requests recent earthquakes near the user’s available location, latitude and longitude may be included in the request sent to the European-Mediterranean Seismological Centre (EMSC) service. EMSC may also receive standard network information, such as the device’s IP address, as part of the internet connection. The developer does not receive or store this request.

Public earthquake-data services

The app retrieves earthquake information from public services operated by:

• the United States Geological Survey (USGS);
• the European-Mediterranean Seismological Centre (EMSC); and
• the Japan Meteorological Agency (JMA).

These services may receive standard technical network information, including the device’s IP address, when the app connects to them. Their handling of information is governed by their own terms and privacy practices.

Official earthquake-data alerts

When monitoring is active and internet access is available, QuakeRescue LifeLink retrieves recent earthquake information from the United States Geological Survey (USGS), the European-Mediterranean Seismological Centre (EMSC), and the Japan Meteorological Agency (JMA).

The app compares the earthquake’s magnitude, location, and issue time with its configured magnitude, distance, and age criteria and the user’s available location. This relevance assessment is performed locally on the device.

When an earthquake meets the configured criteria, the app automatically starts the same five-minute safety countdown used by the local motion-detection system. The user can confirm that they are safe or activate rescue mode immediately.

If the user does not respond before the countdown reaches zero, rescue mode activates automatically. This starts the continuous SOS Quake BLE broadcast and the rescue siren. If the user has enabled and configured the optional emergency SMS function, the app also attempts to send an emergency SMS to the recipients selected by the user. SMS transmission and delivery depend on mobile service, permissions, device support, and operator conditions.

QuakeRescue LifeLink retrieves earthquake data from USGS, EMSC, and JMA. It does not intercept Android emergency alerts or national cell-broadcast warnings and does not contact authorities. This function complements official emergency warning systems and does not replace them.

4. Permissions and their purposes

The app may request Android permissions needed for the following functions:

• Motion sensors: local earthquake-motion analysis.
• Location: available-location functions, nearby-earthquake searches, relevance calculations, and optional location information in an emergency SMS.
• SMS: sending the optional emergency SMS to user-selected recipients.
• Bluetooth and nearby devices: broadcasting and scanning for SOS Quake rescue signals.
• Notifications and full-screen alerts: showing monitoring, countdown, rescue, and safety-related notifications or screens.
• Internet/network access: retrieving public earthquake information.
• Foreground service and device restart handling: supporting user-enabled monitoring and rescue-related operation in accordance with Android system rules.

The app can only use permission-dependent functions when the required permission has been granted. Permissions can be reviewed or withdrawn in Android system settings, although doing so may prevent the corresponding function from operating.

5. Storage, retention, and deletion

App settings, configured emergency contacts, the last available location, and operational state are stored locally for as long as they are needed for the configured functions or until they are changed or removed by the user.

Users can remove configured contacts or change settings within the app where those controls are available. Locally stored app data can also be deleted through Android’s app-data controls or by uninstalling the app.

Android cloud backup is disabled for QuakeRescue LifeLink. The developer does not maintain a cloud copy of the app’s locally stored information.

Information sent by SMS, observed through BLE, or transmitted to an external earthquake-data service is outside the developer’s storage and control after transmission. Retention by mobile operators, recipients, or external services is governed by their own practices and legal obligations.

6. Sharing, sale, advertising, and tracking

The developer does not sell personal information. The app does not share information with advertisers, advertising networks, data brokers, or analytics providers. It does not use personal information for targeted advertising or cross-app tracking.

The transmissions described in Section 3 occur only to provide the relevant app function: user-directed emergency messaging, public nearby BLE rescue signalling, and retrieval of earthquake information.

7. Security

The app is designed to minimise data transmission by processing motion analysis and core rescue logic locally. However, no device, wireless transmission, mobile network, or internet service can be guaranteed to be completely secure or continuously available.

Users should protect access to their device and keep Android security updates current. QuakeRescue LifeLink cannot guarantee earthquake detection, message delivery, BLE reception, location availability, or rescue.

8. Children’s privacy

QuakeRescue LifeLink is a general safety-support application and is not designed to collect personal information from children for advertising, profiling, or commercial purposes. The app does not knowingly collect personal information into a developer-operated service. A parent or guardian should supervise the configuration of permissions, emergency contacts, and optional SMS functions when the app is used by a child.

9. User choices

The user controls whether to:

• activate motion monitoring;
• grant or withdraw Android permissions;
• configure and enable the optional emergency SMS function;
• select the emergency-message recipients;
• use location-dependent features;
• activate rescue mode; and
• scan for nearby SOS Quake signals.

Withdrawing a permission or disabling a setting may make the related safety or rescue function unavailable.

10. Changes to this Privacy Policy

This Privacy Policy may be updated if the app’s functionality, data practices, legal requirements, or external services change. The effective date at the top of the policy will be revised when an updated version is published. Material changes will be communicated through an appropriate publication or app-update channel.

11. Contact

Questions about this Privacy Policy or QuakeRescue LifeLink’s privacy practices can be submitted through the official website:

The public support email shown on the QuakeRescue LifeLink Google Play listing (pending) may also be used for privacy enquiries.

12. Safety notice