Recommended setups

Clear setup and pilot plan for each environment

Start small, validate in your environment, and expand only when the data supports it.

Cities

Parks, residential areas, municipal corridors, transit hubs

Outcomes

  • Deploy flexible coverage across parks, corridors, and public gathering spaces
  • Privacy-first model: on-device detection with no cameras and no raw-audio transmission to SplitSec
  • Multi-device corroboration can increase confidence in a possible-gunfire detection

Pilot setup

  1. 1
    Identify pilot zonesSelect specific public areas, parks, or event corridors
  2. 2
    Deploy devices with personnelEquip city field teams, park district staff, or safety ambassadors
  3. 3
    Measure & evaluateAssess alert speed, coverage uptime, false alerts, and corroborated detections
Download Whitepaper

Guard companies

Posts, patrols, client sites

Outcomes

  • For smartphone deployments: add a clear safety layer for clients without cameras or wiring
  • Standardize alerts across posts and patrol routes
  • Give supervisors visibility into coverage readiness

Pilot setup

  1. 1
    Pick one siteChoose posts and patrol zones to cover
  2. 2
    Deploy the kitArm coverage and assign supervisor roles
  3. 3
    Report readinessUptime, armed time, alerts, and corroborated detections
Download Whitepaper

Outdoor events

Festivals, parades, fairs

Outcomes

  • Deploy coverage fast and move it as the perimeter changes
  • Build confidence with corroboration across multiple devices
  • Share a simple readiness report after the event

Pilot setup

  1. 1
    Place phones with security personnelEntry, stage, dense areas, command post
  2. 2
    Assign rolesEvent admin, security lead, key staff
  3. 3
    Run and reviewalerts and corroborated detections, then export the pilot summary
Download Whitepaper

Campuses

Districts, campuses

Outcomes

  • Start with one building and expand based on real results
  • Clear messaging: no cameras. Privacy-first, on-device detection. Raw audio is never transmitted to SplitSec.
  • Designed to reduce certain false alerts through multi-device corroboration

Pilot setup

  1. 1
    Define pilot scopeOne building, wing, or floor
  2. 2
    Assign rolesAdmin and SRO response roles
  3. 3
    Report and decideReadiness, false alerts, and coverage gaps
Download Whitepaper

Places of worship

Churches, temples, mosques

Outcomes

  • Extend awareness to entrances, parking areas, and outdoor gathering spaces
  • For smartphone deployments: support staff and volunteer response roles without cameras or wiring
  • Start with one campus area and expand after a measured pilot

Pilot setup

  1. 1
    Assign staff to carry SplitSec phones in key outdoor zonesMain entrances, parking lots, drop off lanes, fellowship areas
  2. 2
    Assign response rolesOperations lead, security volunteer, facilities manager
  3. 3
    Review and refineTrack coverage, false alerts, and response readiness across service times

Logistics yards

Loading areas, parking lots, vehicle entrances, storage areas, and outdoor facility perimeters.

Outcomes

  • Privacy-first, on-device detection. Raw audio is never transmitted to SplitSec.
  • Role based escalation for security and operations leadership
  • Operational reporting focused on device health and perimeter readiness

Pilot setup

  1. 1
    Place phones with staff in key areasGatehouse, loading docks, truck lanes, yard perimeter, employee parking
  2. 2
    Assign response rolesSecurity, shift supervisor, operations manager
  3. 3
    Validate in contextMeasure uptime and false alerts in your industrial noise profile

Pilot

What we measure

Simple numbers that help you decide. Deploy, measure, scale.

Pilot report snapshot

SplitSec pilot report
Weekly summaryAverage response time, % enrolled, average daily coverage.
Incident summaryNo incidents reported.
Coverage statusArmed time and battery health.

Common questions

Core FAQ (for everyone)

SplitSec is a privacy-first safety app that analyzes sounds on-device for potential gunfire and provides safety alerts. Raw audio is never transmitted to SplitSec. Detection runs locally on the phone; connectivity may still be required for alert delivery, corroboration, feedback, and other connected features.

Permissions FAQ

For Parents, Educators & Adult Campus Users

SplitSec app users must be at least 18 years old.

Press & Government

Schools, Campuses & Institutions

Safety & Limitations

Back to top
Book 30 minutes