Auto Secure LoginDevice monitoring that proves it stayed in scope.
ASL Supervision is an organization-administered monitoring program for agency-owned supervised endpoints. An agency records a specific authority — a court order, supervision condition, participant agreement, or employer policy — with jurisdiction, dates, notice acknowledgment, and an explicit list of allowed data categories. The platform then enforces that scope at the ingestion boundary, rejecting anything outside it or after suspension. Officers spend their time on supervision, not on proving the monitoring stayed in bounds — the platform carries that burden by construction.
The problem
Monitoring that can't prove its limits is a liability.
Probation, parole, and pretrial programs need to monitor agency-owned devices under a court's authority — but a system that can't prove exactly what it was allowed to collect, and when, is indefensible in front of a judge or a defense attorney.
ASL Supervision makes scope a structural property: authorization is re-checked on every single upload, so suspension or revocation takes effect immediately and out-of-scope data is rejected before it's ever stored.
What it deliberately does NOT do
- Decrypt HTTPS or read message contents
- Scrape screens or log keystrokes
- Use the mic, camera, or covert screenshots
- Automatically decide a violation
Alerts are evidence pointers for a trained human — never a verdict. Proven by end-to-end negative tests.
Capabilities
Authorized, minimized, and auditable.
Monitoring authorizations
Authority type, reference number, jurisdiction, effective window, participant notice acknowledgment, approver, and an explicit allowed_categories list — active, suspended, or revoked.
Enforced at three gates
A record with no valid authority can't enroll, out-of-scope categories are rejected before storage, and suspension stops uploads even if the device still holds a credential.
One-time enrollment
30-minute, single-use enrollment tokens bound to a specific authorization; activation returns a random per-device credential exactly once.
Signed telemetry
Every upload signs method, path, timestamp, nonce, and body-hash; the server enforces a 5-minute window and consumes each nonce once to defeat replay.
Managed iOS
SwiftUI client with disclosed location/geofence and device-health, Keychain identity, an offline queue, and a Network Extension that retains flow metadata but never payload contents.
Native Android
A visible ongoing-supervision notification, Android Keystore encryption, a bounded offline queue, and an Android Enterprise policy that forces Play Protect and blocks untrusted installs.
Windows service
A .NET 8 service with DPAPI-protected identity, an encrypted queue, allowlisted collectors, and ECDSA-signed policies with rollback rejection.
Per-agency audit chain
Hash-linked over every sensitive action and device ingestion, with a low/medium/high alert acknowledgment workflow.
Officer PWA portal
An installable portal for officers and organizations to manage records, assignments, and alerts.
Monitoring that survives scrutiny.
Scope-bound by construction, minimized by policy, and auditable end to end — built for agencies that answer to a court.