Vehicle data policy · 1 August 2026
Vehicle history stays sourced, scoped and accountable.
This policy describes the product rules that separate public vehicle transparency from private evidence and personal information.
Persistent identity
An OID remains with the vehicle. Control may change, but an authorised transfer does not reset or privately rewrite the prior record.
Source and verification
Every contribution carries a source role and verification state. Owner-reported, contributor-submitted and independently verified events must remain distinguishable. Trust indicators are summaries of recorded factors, not guarantees.
Evidence boundaries
Supporting invoices, reports, images and authority documents are restricted by default, stored separately from the public record and sealed with an integrity hash. A public event can refer to evidence without exposing that evidence.
Controller authority
The controller manages publication, contributions, transfers and connected-agent permissions. Control is operational authority within OID and does not replace legal ownership, registration or another external right.
Agent access
An agent's effective access is the intersection of its certified scopes and the controller's active connection for that vehicle. Customer-level disclosures and consent are added where required. Revocation stops new access; it does not erase legitimate historical audit events.
Transfers
Transfers record the initiating controller, intended recipient, status and acceptance outcome. Sensitive connected services may pause during transfer so the recipient can make a fresh permission decision.
Correction, dispute and removal
Incorrect personal details can be corrected. Disputed vehicle events may be restricted or relabelled while reviewed. OID preserves a minimal audit trail when removal of an event or access path is necessary, unless law requires a different outcome.
Retention
Data is retained according to purpose, record integrity, consent, provider obligations and applicable law. Short-lived contact information expires before persistent vehicle identity and audit records. Recovery queues and operational logs use bounded retention and avoid storing unnecessary personal content.
Report a concern
Email admin@onsellr.com with the OID code, the event or permission concerned, and your relationship to the vehicle. Do not attach sensitive evidence until a secure submission path is provided.