Analyze roadway behavior without identifying individuals.
Cumulant is designed to understand movement, interactions, and roadway conditions—not personal identity.
The plain-language summary.
Cumulant processes roadway video and related context to identify visible movement, behavior, and events. The transportation and safety workflow is not designed to establish personal identity.
Purpose follows the project
The site, source, observation period, event definitions, outputs, access, and retention should be tied to an agreed transportation or safety question.
Source stays connected
Event metadata and findings remain linked to the originating video, location, time, and available review context.
Access stays bounded
Customer and Cumulant access should be limited to authorized users and necessary operating roles.
What may enter the system.
Roadway video
Stored footage, supported live feeds, or video captured through a Cumulant deployment.
Site and source context
Camera, location, time, study, deployment, customer GIS, and source-reference information.
Event and review metadata
Observed category, timestamp, location, review state, notes, measurements, and related outputs.
Account information
Authorized-user details and customer-provided operational or study context.
How roadway video is processed.
Detection and classification
Identify visible road users or objects relevant to the configured transportation workflow.
Movement and interaction
Organize tracks, paths, timing, proximity, speed, and other visible relationships within the scene.
Event organization
Apply configured definitions and index matching moments for search, review, analysis, and reporting.
Edge and cloud processing
The processing path depends on the source, deployment, connectivity, and agreed operating workflow.
What the roadway workflow does not need.
General event search and movement analysis should not be interpreted as a claim of personal identification.
Facial recognition
Not part of the described Cumulant transportation and safety workflow.
Biometric identification
Not part of the described Cumulant transportation and safety workflow.
Persistent identity tracking
Movement and event analysis does not establish a persistent personal identity.
License-plate recognition
Not implied by general search or visible-attribute language; any separate capability would require explicit scope.
Storage, transmission, retention, and deletion.
Transmission
Video, clips, metadata, and results may move through secured connections appropriate to the deployment.
Storage
Source footage, derived clips, event metadata, findings, reports, and backups may use different storage systems.
Retention
Retention periods should follow the project, source, customer requirements, and the role each record plays.
Deletion
Deletion responsibilities and timing should be defined for source footage, derived clips, metadata, outputs, and backups.
What the customer controls.
Lawful source access
Customers are responsible for the authority and permissions associated with provided or connected video sources.
Project and deployment scope
Customers participate in defining the location, purpose, observation period, source, outputs, and authorized uses.
Authorized users
Customers should limit access to appropriate staff, partners, and operating roles.
Records responsibilities
Municipal customers may have public-record and records-management obligations that affect project data.