Safety record
Data4 safety record
DEPLOY has no incidents on file for Data4. This rolls up incidents attached directly to Data4, to its models, and to its deployments (operated or manufactured): the same graph as the company page's safety-record summary, shown here with full sourcing and exposure context.
Machine-readable surfaces
- Markdown mirror: /companies/data4/safety-record.md
- JSON-LD: embedded in this page’s head
- REST API:
/v1/safety/companies/04cff8e3-faa9-4090-89ac-f488496ca5d2/profile - Data documentation: /data
- Query this programmatically: Deploy MCP
Incidents
No incidents on record for Data4. Absence of a recorded incident is not proof of a clean operating history; it reflects what DEPLOY has tracked and verified to date.
Exposure
DEPLOY does not have exposure data (deployment-hours, miles driven, or rides given) on file for Data4. This is a genuine data gap, not a rounding to zero: no incident count above can be turned into a defensible rate without it. NHTSA's SGO dataset itself does not publish exposure denominators, and there is no standardized, regulator-verified nationwide source for AV fleet mileage or ride counts today. Where a company self-publishes a mileage figure, it is not independently audited and is not shown here as DEPLOY-verified data.
Common questions
What is Data4's safety record?
Is Data4 safer than a human driver?
Does DEPLOY redact or omit crash details for Data4?
Full company record: Data4