Back to home

Privacy policy

Effective date: 6 July 2026. Applies to Emergency GPX for Android, package net.rygielski.emergencygpx.

1. Who is responsible for the app

Emergency GPX (the "App") is developed and published by Wojtek Rygielski (the "Developer"). Privacy questions may be sent to rygielski@gmail.com.

2. What the Developer collects

The Developer does not collect personal data through the App. There is no Emergency GPX account, registration system, developer-operated server, advertising SDK, analytics SDK, or crash-reporting SDK.

Specifically, the Developer does not receive:

• your name, email address, phone number, or contact list;
• your precise location from the App;
• your Opencaching username;
• your GPX files, downloaded cache data, filters, or app settings;
• analytics events, app-open events, click-stream data, advertising identifiers, or device identifiers.

3. Network requests to Opencaching OKAPI

The App's main function is to download nearby Opencaching caches as a GPX file. To do that, it sends requests from your device to the Opencaching OKAPI installation selected in the App.

When you tap Download GPX, the App sends:

• the search coordinates, taken from your GPS location, manually typed coordinates, or a point shared from Locus Map;
• the cache filters and result limit you selected;
• the phone's language preferences, so OKAPI can choose suitable cache-description languages;
• the App's OKAPI consumer credentials, which identify the App to OKAPI.

If you enter an Opencaching username for found-cache handling, the App also sends that username to OKAPI to look up the matching user UUID. The UUID is then used only to skip found caches or mark them as found in the generated GPX, depending on the option you selected.

OKAPI returns cache data and a GPX file response to your device. The Developer does not proxy, receive, or store this traffic. Each Opencaching installation's own privacy practices are governed by that installation and are outside this policy.

4. Location data

Emergency GPX asks Android for foreground location permission so it can find caches near you. The App uses location only while you are using it. It does not track your location in the background.

Your location remains on your device until you choose to download a GPX. At that point, the coordinates used for the search are sent to OKAPI as described above. If you type coordinates manually or share a point from Locus Map, those coordinates are used instead of your current GPS fix.

5. Files and app storage

The App writes the downloaded GPX file to its app cache directory, then opens or shares that file through Android, or imports it into Locus Map when the Locus handoff succeeds. The generated GPX contains geocache data returned by OKAPI.

The App stores settings locally on your device, including selected filters, result limit, manual coordinates, found-cache mode, and the optional username you entered. These settings are not sent to the Developer. They are sent to OKAPI only when needed for a download, as described in section 3.

Uninstalling the App removes app-private cached files and app-private settings according to Android's normal uninstall behavior. Files you open, share, import, or save into another app may remain under that other app's control.

6. Locus Map integration

Emergency GPX can receive a point shared from Locus Map and can ask Locus Map to import the generated GPX file. To support this, the Android build declares Locus-related package visibility and the com.asamm.locus.permission.READ_GEOCACHING_DATA permission used by the Locus integration.

Data exchanged with Locus stays between the App, Locus Map, and Android's local inter-app communication. The Developer does not receive it.

7. Permissions

The App may request or declare the following permissions and capabilities:

• Location while in use - to obtain your current position for nearby-cache search.
• Internet / network access - to contact the selected Opencaching OKAPI installation and download GPX data.
• Locus geocaching permission - to support Locus Map point handoff and GPX import.
• Package visibility for Locus Map variants - to find an installed Locus app that can import the generated GPX.

The App does not request contacts, calendar, camera, microphone, phone state, SMS, call log, advertising ID, or broad all-files management access.

8. Third parties

The App interacts with these third parties when you choose the related action:

• Selected Opencaching OKAPI installation receives download and username-lookup requests needed to generate GPX files.
• Locus Map may receive the generated GPX file if you use the Locus handoff/import flow.
• Other Android apps may receive the GPX file if you choose them from Android's open/share flow.
• Google Play distributes the App. Google's collection of Play Store install, update, crash, and device data is governed by Google's privacy policy, not this policy.

9. Children's privacy

The App is a utility and does not include ads, accounts, social features, or user-generated content. The Developer does not knowingly collect personal data from children or from any other users through the App.

10. Security

Requests to OKAPI use HTTPS URLs. Generated GPX files and local settings are stored on your device using the storage mechanisms provided by Android and the App runtime. No internet transmission can be made to the Developer because the Developer operates no backend for this App.

11. Your choices

• You can deny location permission and use manually typed coordinates or a Locus-shared point instead, where supported by the current app flow.
• You can leave the username field empty to avoid username lookup and found-cache personalization.
• You can reset settings inside the App.
• You can delete generated GPX files from any app or location where you saved or imported them.
• You can uninstall the App to remove app-private data from your device.

12. Changes to this policy

If the App's privacy behavior changes, this policy will be updated and the effective date above will be revised. Material changes may also be described in the app listing or release notes.

13. Contact

For privacy-related questions, requests, or concerns, write to rygielski@gmail.com.