Raw audio stays on your device. It is never transmitted to SplitSec.
Raw microphone audio used for detection is processed locally and is not transmitted to SplitSec cloud services for detection.
Temporary sound input used by the device.
Local conversion into model-ready data.
Evaluates patterns associated with possible gunfire.
Connected features require some data, but raw microphone audio for detection or false-positive feedback is not the payload.
| Information | Sent to SplitSec? | Notes |
|---|---|---|
| Raw microphone audio used for detection | No | Detection runs on-device. |
| Raw audio used for false-positive feedback | No | The raw recording used to create feedback is not transmitted. |
| Derived numerical sound signature | Only when selected | Created on-device when the user chooses an applicable labeled feedback action. |
| Detection/event information | Yes, where needed | Used for connected SplitSec features and service operation. |
| Precise device location | When applicable | Requires applicable permission and a location-dependent feature. |
| Nearby nonparticipant phone information | No | SplitSec does not collect device or location information from nearby phones that are not participating. |
| Carrier or cell-tower location records | No | SplitSec does not obtain these records. |
A sound signature is a derived numerical representation created from the relevant sound on the user's device. It is not the raw audio recording.
If you choose a feedback action that submits a sound signature, your device creates a derived numerical representation on-device. SplitSec receives the sound signature, not the raw audio.
Declining automatic sharing does not affect otherwise eligible rewards. Turning it off stops future and pending uploads; previously submitted signatures follow the Privacy Policy’s retention rules.
The transformation occurs before transmission.
Signatures may be submitted through clearly labeled feedback or optional automatic sharing, which is off by default and requires a separate opt-in. Raw audio is never transmitted to SplitSec.
See the Privacy Policy for exceptions and backup retention.
Location can support nearby awareness and coordinated detection when permission is granted. It is not used to build profiles of individual users' movements or travel patterns.
SplitSec does not obtain carrier or cell-tower location records.
We do not collect location or device information from nearby nonparticipating phones.
Location is not used to build profiles of individual users' movements or travel patterns.
We publish specific retention expectations rather than saying data is kept only "as long as needed."
Limited exceptions, including legal holds and certain security or legal requirements, and temporary backup retention are described in the Privacy Policy.
Pilot partners generally receive aggregated or de-identified pilot information. SplitSec does not provide ongoing or bulk access to individual users' precise location histories, sound signatures, or identifiable account information.
SplitSec does not automatically report detections to 911 and does not provide law enforcement with an ongoing feed of users' locations, sound signatures, or account activity. The Privacy Policy describes circumstances where disclosure may be permitted or required.
App permissions can be managed through your device. You can delete your SplitSec account through the in-app deletion flow or by contacting support.
Executable app updates use authorized distribution channels. This is different from separately updating a detection-model file.
SplitSec does not use an in-app over-the-air mechanism to remotely replace or modify executable application code outside authorized app-store or operating-system distribution channels.
The app may separately check for and download updated detection-model files. A model download does not cause raw microphone audio to be uploaded to SplitSec.