SplitSec AI - Privacy Policy

Version: 1.4


Effective: July 25, 2026


Company: SplitSec AI LLC (Illinois, USA)


Product: SplitSec.AI mobile application (Android and iOS)


Contact: support@splitsec.ai • www.splitsec.ai


Address: 2246 W Madison Ave, Suite 1 #1018, Chicago, IL 60612


Phone: (812) 509-5260

1. Overview


SplitSec AI LLC ("SplitSec," "we," "us") builds privacy-first safety technology. When gunfire detection is enabled, the App analyzes sound patterns on the device to identify possible gunfire. Raw audio is not continuously streamed to our servers. This Privacy Policy explains the information we collect, how we use and disclose it, and the choices available to users.


"Pre-Release" includes alpha, beta, preview, early-access, test, community-pilot, ward-pilot, limited-release, and similar deployments, whether private, limited, invite-only, or public. This Policy applies to Pre-Release and pilot use unless a feature-specific notice says otherwise.

2. Who Can Use SplitSec



  • Under 13: The App is not intended for children under 13. Do not register or use the App if you are under 13.

  • Ages 13–17: Use the App only with parent or legal-guardian consent where required by law.

  • Adults 18+: May use the App subject to this Policy and the Terms of Service.

3. Information We Collect and Process



  • Account and Registration Information: Name or display name, phone number, optional email address, one-time-passcode and login metadata, account status, and settings. We do not collect an account password when login is handled through one-time codes.

  • Age and Consent Information: Date of birth or age eligibility information, age band, adult/teen status, parent or guardian consent status where applicable, policy versions accepted, consent selections, and acceptance timestamps. Where available, we may receive an age or supervision signal from an app store to provide an age-appropriate experience and comply with law.

  • Device and App Information: Device identifiers, device model, operating-system and app versions, language, notification token, security and integrity signals, permission status, battery or foreground-service status, crash logs, and performance diagnostics.

  • Location Information: Precise or approximate device location when enabled or required for a feature, along with derived or generalized locations such as a nearby road, intersection, approximate alert center, distance, radius, boundary, or potential gunfire area. Derived locations are estimates and may be inaccurate, delayed, shifted, snapped, generalized, or associated with the wrong street, address, property, or house.

  • Detection and Alert Information: Possible-gunfire detection events, timestamps, confidence or classification information, user confirmations or responses such as "Yes, I heard it," "No, I did not," "Not sure," or "Not gunfire," corroboration information, alert status, delivery status, and related operational metadata; whether Corroboration Mode is enabled; and corroboration-related matching results used to determine whether alert conditions are met. User responses are self-reported and may be inaccurate, incomplete, delayed, or related to a different sound or event.

  • AlertCrew Information: Names, phone numbers, email addresses, relationship labels, invitations, membership status, delivery information, and responses for people you select or who join an AlertCrew.

  • Optional Audio Clips: If you mark an event as "Not gunfire," "False alert," or similar, the App may ask whether you want to share a short audio clip. The clip is uploaded only if you affirmatively choose to share it for that event.

  • Support and Communications: Emails, chats, reports, feedback, survey responses, and other communications you send to us.

  • Analytics: Feature-use and performance events used to understand and improve the App. Where required, optional analytics are collected only after consent. We seek to aggregate, truncate, or de-identify analytics where practical.

  • Payments: If paid offerings are introduced later, payment processors or app stores may provide transaction identifiers, subscription status, and billing metadata. SplitSec does not store full payment-card numbers.

4. Information We Do Not Collect or Use in Certain Ways



  • We do not continuously stream raw microphone audio to our servers.

  • We do not upload a false-alert audio clip unless you choose to share it for that event.

  • We do not sell your personal information or share it for targeted advertising.

  • We do not display a reporting user's identity or exact report location to community or nearby-alert users.

5. How We Use Information



  • Create and secure accounts, verify phone numbers, provide one-time passcodes, and maintain user preferences.

  • Operate on-device detection, possible-gunfire alerts, drills, AlertCrew, nearby alerts, corroboration, approximate alert areas, and related safety features, including applying user-selected corroboration requirements and determining whether the conditions for an alert are met.

  • Determine which alerts are relevant based on location and protect privacy by reducing, snapping, obscuring, or generalizing locations shown to community users. These processing methods intentionally trade precision for privacy and may produce an area that differs from the actual source or incident location.

  • Deliver service communications through push notifications, SMS, email, or in-app messages.

  • Provide age-appropriate onboarding and comply with parental-consent or app-store age-signal requirements where applicable.

  • Investigate false alerts, abuse, security incidents, crashes, service failures, and performance problems.

  • Use optional audio clips and feedback to label data and develop, test, evaluate, and improve detection models and product features.

  • Provide customer support, communicate material policy or service changes, and administer pilots.

  • Comply with legal obligations and enforce the Terms of Service.

6. How Alerts and Location Information Are Shared



  • AlertCrew: Depending on the feature and your settings, selected AlertCrew members may receive your name, alert type, safety status, approximate or precise location, map link, timestamp, and related message content.

  • Nearby or Community Users: Eligible users may see an approximate alert area, approximate distance, time, alert status, and aggregated or individual community responses where the feature provides them. Map displays and user responses are unverified and may be inaccurate, incomplete, delayed, shifted, generalized, mistaken, or associated with a different sound, street, address, property, or house. A response does not verify that gunfire occurred or establish its source. SplitSec is designed not to show the reporting user's identity or exact report location to community users.

  • User and Third-Party Sharing: Users may independently show, describe, screenshot, forward, or report alert or map information to AlertCrew members, law enforcement, emergency services, or others. SplitSec does not control those independent disclosures or how recipients interpret or act on them.

  • Pilot Partners: Ward offices, municipalities, libraries, community organizations, sponsors, and event hosts may receive aggregated or de-identified participation, usage, performance, and pilot-result information. We do not provide them with identifiable account, AlertCrew, precise-location, or optional audio-clip information unless you direct us to do so, consent, or disclosure is legally required.

  • Emergency Services: SplitSec does not automatically guarantee reporting to 911 or law enforcement. Information is shared with emergency services only when a user initiates the communication, a feature expressly provides it, or disclosure is legally required.

7. Service Providers and Other Disclosures



  • Service Providers: We use providers for cloud hosting, databases, authentication and OTP, push notifications, SMS, email, analytics, crash reporting, support, security, and app distribution. They may process information only to provide services to us and subject to appropriate contractual restrictions.

  • Legal and Safety: We may disclose information when reasonably necessary to comply with law, legal process, or enforceable requests; protect users or others from harm; investigate fraud or abuse; or protect rights, security, and property.

  • Business Transactions: Information may be transferred as part of a merger, financing, acquisition, reorganization, bankruptcy, or sale of assets, subject to applicable law and this Policy.

8. Legal Bases Where Applicable



  • Consent, including device permissions, optional audio sharing, optional analytics, and marketing choices.

  • Performance of a contract, including providing the App under the Terms of Service.

  • Legitimate interests, including safety, service operation, model and product improvement, security, abuse prevention, and support, balanced against user rights.

  • Compliance with legal obligations.

9. Data Retention



  • Account and consent records are retained while the account is active and for a reasonable period afterward for security, audit, dispute, and legal purposes.

  • Detection, alert, delivery, location, and operational metadata are retained only as reasonably necessary to provide, secure, evaluate, and improve the service and administer pilots.

  • Optional audio clips may be retained for model evaluation, labeling, training, testing, quality control, and legal or security needs. We may de-identify, aggregate, shorten, or delete them when no longer reasonably necessary.

  • Crash, analytics, and support records are retained according to operational needs and provider retention settings.

  • Backups may retain information for a limited period after deletion before they cycle out. We may retain information longer when required by law, necessary for security, or needed to establish, exercise, or defend legal claims.

10. Your Choices and Rights



  • Device Permissions: Manage microphone, notifications, location, and contacts through device or App settings. Disabling a permission may prevent related features from working.

  • Optional Audio: Decline the per-event request to share a false-alert audio clip.

  • Analytics and Marketing: Use available App settings or unsubscribe mechanisms to withdraw optional choices.

  • SMS: Reply STOP to opt out or HELP for help. SMS-dependent features may stop working if you opt out.

  • Account Access, Correction, and Deletion: Use available in-app account controls or contact us to request access, correction, or deletion, subject to verification and legal exceptions.

  • US State Rights: Residents of states with applicable privacy laws may have additional rights, such as access, correction, deletion, portability, or appeal. We do not discriminate for exercising applicable rights.


Submit a privacy request to support@splitsec.ai with "Privacy Request" in the subject. We may verify your identity and authority before completing a request.

11. Security


We use reasonable administrative, technical, and physical safeguards designed to protect information, including access controls, encryption in transit where appropriate, device and app integrity measures, and security monitoring. No system is completely secure, and we cannot guarantee absolute security. Keep your device, operating system, and App updated and protect access to your phone and one-time passcodes.

12. Youth Privacy



  • We do not knowingly permit children under 13 to register or use the App. If we learn that we collected personal information from a child under 13, we will take reasonable steps to delete it.

  • Users ages 13–17 should use the App with parent or legal-guardian consent where required. Teen accounts do not receive marketing communications unless legally permitted and separately authorized.

  • A parent or legal guardian may contact us to request review, correction, restriction, or deletion of a teen's account, subject to identity and authority verification.

13. International Processing


Information may be processed in the United States and other countries where our service providers operate. Where applicable law requires, we use appropriate safeguards for cross-border transfers.

14. Privacy Preference Signals


The mobile App does not receive browser "Do Not Track" headers. On our website, we will honor legally required privacy preference signals, such as Global Privacy Control, where applicable to the processing performed on the website.

15. Community Pilot Notices


A community or ward pilot may include pilot-specific instructions, notices, surveys, or participation information. Unless a pilot-specific notice expressly states otherwise, this Privacy Policy governs SplitSec's handling of personal information. Pilot partners receive only the information described in Section 6.

16. Changes to this Policy


We may update this Policy. We will provide notice of material changes through the App, email, our website, an app-store listing, or another reasonable method. When required, we will request renewed consent or acknowledgment. The "Effective" date above identifies the current version.

17. Contact Us


SplitSec AI LLC • 2246 W Madison Ave, Suite 1 #1018, Chicago, IL 60612 • Phone: (812) 509-5260 • Email: support@splitsec.ai

Book 30 minutes