ADAS Calibration Data Retention and Audit Guide
Fleet legal teams, insurers, and OEM field auditors increasingly request ADAS calibration records — scan-tool PDFs, shop invoices, validation timestamps, and continuous monitoring history. Without retention policies, exports scatter across email, shared drives, and vendor portals with inconsistent hashes and no chain of custody. NADIR signed evidence bundles standardize tier timelines, org isolation, and export metadata for audit response — not homologation replacement. This guide defines retention windows, access controls, and audit pack composition for fleet operators and MSO partners evaluating continuous calibration intelligence.
What auditors ask for in 2026
Common requests include: proof of post-glass validation, continuous monitoring coverage between shop visits, CRITICAL closure timestamps, and tamper-evident export metadata. Insurer renewals mirror OEM field reviews — 2026 liability trends.
NADIR bundles chain detection events, tier transitions, shop actions, and validation closure with content hashes — field definitions on the evidence page and API patterns in API integration guide.
MSO chain-of-custody language complements bundles — MSO evidence chain of custody.
Recommended retention windows (starting points)
Fleets should align with counsel; typical starting points: tier history retained thirty-six months for insurer audit; signed export bundles seven years for major incident files; raw perception frames per partner contract minima. Document exceptions for litigation holds.
Org-scoped API keys prevent cross-customer leakage on shared MSO platforms — persistence isolation is enforced at NADIR API layer per security overview.
Deletion workflows should propagate to downstream BI — webhook events documented in integration guides.
Audit pack composition
A complete pack for quarterly insurer review: executive summary PDF, tier histogram CSV, three redacted signed bundles (glass campaign, collision repair, routine CAUTION closure), LOI shadow graduation criteria, and safety board deck excerpt — template in safety board reporting.
Regulatory crosswalk slides without overclaiming — ISO 26262 mapping and UN ECE R152 validation.
Telematics RFP retention clauses
Procurement should require export portability, hash metadata, and deletion SLAs — telematics RFP guide.
Repair network record alignment
Scan-tool PDFs alone lack continuous context; NADIR adds tier history before and after bay work — post-repair MSO evidence and repair network quality.
Windshield and structural triggers — windshield recalibration.
Litigation holds and e-discovery
When litigation holds freeze deletion, document which tier exports and bundles remain immutable — counsel should receive hash manifests rather than ad hoc screenshots. eDiscovery vendors need org-scoped credentials with read-only export roles; never share fleet-wide admin keys.
Cross-border fleets should note data residency commitments in MSO contracts — EU operators may require regional export endpoints documented during RFP.
Simulation artifacts for validation teams — simulation drift data retention may differ from operational tier history; label each class in policy docs.
FAQ
Are NADIR exports tamper-evident?
Signed bundles include content hashes; verify against Console export logs.
Can MSOs hold records for multiple fleet customers?
Yes with separate org tenants and keys per fleet contract.
Does retention satisfy ISO 26262?
Retention supports operational audits; homologation records remain OEM scope.
Who wrote this guide?
Sri Balaji, Co-Founder and CTO at NADIR.
Next steps
Review the NADIR platform, explore the HORIZON pilot walkthrough, and open the Calibration Lab before wiring fleet telemetry. Shadow pilots score every eligible VIN without changing dispatch.
Request a four-week cohort via the footer pilot form or team@nadirai.net with fleet size, telematics partner, and target KPIs.