StationCommand Privacy Notice
Last updated August 15, 2026
Public analytics
StationCommand uses first-party analytics to understand public statistics and incident-display use. It may record pages/screens viewed, approximate session duration, referrer, browser/device information, and coarse geographic information when supplied by the hosting network. The public analytics system does not retain the visitor's full IP address and does not request GPS location.
Global Privacy Control and Do Not Track signals reduce public analytics. StationCommand does not use analytics for advertising profiles, fingerprinting, or sale of visitor information.
Security and audit logging
Protected services maintain security/audit records including login successes and failures, account identifier when known, authentication provider, date/time, full source IP address, coarse network-supplied location, browser user agent, authorization failures, logout, and protected actions. Passwords, OAuth tokens, GPS coordinates, and dispatch narratives are not intentionally stored in security logs.
Retention
Public detailed analytics and security/audit records are retained according to the configured records-retention policy. Legal holds, investigations, public-records requirements, or other legal obligations may require longer preservation.
Location
StationCommand does not request device GPS/geolocation permission.
Public analytics and security logging
StationCommand uses first-party analytics to count public visits, viewed screens, approximate session duration, and coarse IP-derived geographic area. It does not request browser GPS. Public analytics are reduced when supported privacy signals are received. Full IP addresses are retained for security events and authorized audit activity according to the department's retention configuration.
Public incident information is intentionally generalized. Exact incident addresses, internal narratives, responder identities, and member-only operational data are not exposed through the public incident APIs.