Compliance & accountability
Audit & accountability
For oversight, accountability to islands and partners, and legal defensibility, full traceability of actions in CVR is essential. On this page we account for how this is designed.
Purpose-bound access
Every access to personal or vehicle data takes place with a recorded purpose. For API calls (e.g. enforcement check) a purposeCode is required. For police actions a caseRef is required, so that each lookup and action can be linked to a case. This allows accountability for who, when, and for what purpose accessed which data.
Audit log
The audit log records: actor (user or system), action, entity concerned, before/after where applicable, purpose (purposeCode), caseRef where applicable, correlation_id and timestamp. Logs are append-only; changes or deletions are not possible. Retention follows the policy per jurisdiction.
Event-driven recording
Important mutations (registration, transfer, suspension, block, ownership change, etc.) are recorded as events with a legal meaning. There are no silent updates; every change is traceable and can be used for objection, appeal or oversight.
Non-repudiation
Ownership changes, assessments, enforcement actions and lookups are linked to an actor and a correlation_id. This supports non-repudiation: actions cannot be denied without traces in the audit log.
Oversight and reporting
Auditors and read-only roles can consult audit logs and reports within their authorisation. The platform supports accountability to islands, regulators and where applicable to the citizen.