ThreatClock Privacy Policy

Last updated September 14, 2026.

ThreatClock is a local training timer published as:

• iOS / Apple Watch — bundle ID com.matthewlocke.threatcue
• Android / Wear OS — package ID com.matthewlocke.threatclock

This policy describes what the app uses on your device.

Data we collect

ThreatClock does not require an account and does not operate a user database. Training data stays on your device unless you choose to back up the device with Apple or Google.

• Settings — schedule window, days, threat count, sound and voice preferences.
• Drill log — times you mark visualized or dry-draw complete, and saved shot-clock strings.
• Custom start sound — if you record one, the audio file is stored on the device.

Permissions

• Alarms — on iOS, AlarmKit; on Android, exact alarms, a full-screen notification, and a foreground service. Used only to fire scheduled threat cues, including when the phone is locked, silent, or in Focus / Do Not Disturb.
• Microphone — used only on the shot clock to hear shot reports and, if you choose, to record a custom start beep. Audio is processed on device and is not uploaded.
• Notifications / Live Activities — used to show armed status and threat alerts.
• Watch — if you install the Apple Watch or Wear OS companion, threat cue details are sent to your paired watch.

What we do not do

• We do not sell your information.
• We do not use advertising SDKs or third-party analytics in the app.
• We do not upload microphone audio, drill logs, or custom recordings to our servers.

Apple and Google

If you install via the App Store, TestFlight, or Google Play, Apple or Google processes the information needed to deliver the app under their privacy policies. ThreatClock does not use advertising SDKs or the Google advertising ID.

Children

ThreatClock is not directed at children under 13.

Contact

Questions about this policy: mattnlocke@gmail.com