Privacy Policy

Last updated: March 6th, 2026

Soapbox Software, LLC (“Soapbox Software”, “we”, or “us”) provides a number of “Incidents” applications (“Applications”, “Apps”, or “our Apps”) which display emergency incident information plotted on a map (such as traffic accidents, fires, medical emergencies, etc.). This Privacy Policy covers the following Apps:

This Privacy Policy explains what information is collected by Soapbox Software and any third-party services when users interact with our Apps.

We may change this Privacy Policy from time to time. If we make changes, we will revise the date at the top of the policy and provide a brief summary of the changes at the bottom of the policy, along with all other past changes. Feel free to review the Privacy Policy periodically to stay informed about our information practices and your options related to them. A link to the policy is available in our Apps, as well as in the store where the App was downloaded.

Data Collection

Soapbox Software has no business interest in collecting data associated with individual users. We do, however, use a few third-party services to collect data for the purposes of improving the experience and performance of our Apps. The information collected is listed below, along with how to opt out. Instructions for opting out may be device or OS version specific.

Analytics and Usage

We use platform-provided analytics to gather aggregated, anonymized information about how many users are using our apps.

On iOS, we use Apple App Analytics. To opt out, visit the Analytics Privacy section of the iOS Settings app (described here: https://support.apple.com/en-us/HT202100) and disable “Share With App Developers”. Note that this setting is not app-specific.

On Android, Google Play automatically collects crash reports, performance data, and usage statistics (Android Vitals). To opt out, visit the Usage & diagnostics section of your Android device’s Settings app.

Incident Locations

To show emergency incidents on a map, our Apps determine the location of an incident using the incident’s address. The location of the incident is in no way associated with your current location, which we do not collect.

On iOS, geocoded results are shared using an Apple CloudKit database to improve performance for all users. To share this information, you must be signed into Apple’s iCloud service. This information is only associated with a unique identifier that is not associated with you or your Apple ID. To opt out, revoke access to iCloud from our Apps in the iCloud section of the iOS Settings app.

On Android, incident locations are geocoded server-side before being delivered to the app. No user data is sent during this process.

Maps

On iOS, our Apps use Apple Maps to display incident locations.

On Android, our Apps use the Google Maps SDK to display incident locations. The Google Maps SDK may collect device identifiers, diagnostics data, and crash logs.

Advertising

Most of our Apps are supported through the use of advertisements provided by either Google AdMob or AppLovin. These services may collect information about app interactions (such as ad views and clicks), approximate location (inferred from IP address), and device identifiers to serve and measure ads.

Feedback and Support Email

All feedback and support requests are sent using email. The email address you use will be exposed to us during this interaction.

To opt out, do not send us email.

Other Services

The following services are used for data retrieval and we do not explicitly send any information to them. When retrieving data, these services may collect, process, and store information about the request being made, including but not limited to your IP address. Please refer to their privacy policies for details.

Incident Data

Incident data is loaded from a number of different websites for our Apps.

Incident Location Geocoding

On iOS, our Apps use Apple’s Geocoder service to determine an incident’s location from its address.

On Android, incident locations are geocoded server-side before being delivered to the app. No user data is transmitted during this process.

Security

We use HTTPS to secure the communication between our Apps and the third-party services we use. However, some of our Apps load incident data from public websites using HTTP. No information is explicitly sent to these websites.

Third-Party Links and Content

Interacting with advertisements in our Apps may navigate you to third-party websites. These have their own independent privacy policies, and we have no responsibility or liability for their content or activities.

By using our Apps, you consent to this Privacy Policy.

Third-Party Privacy Policies

For more information about how third-party services used by our Apps collect and handle data, please refer to their privacy policies:

Contact Us

If you have questions regarding this Privacy Policy, please contact us at: [email protected]

Changes to This Policy