Retention and compliance reporting
Meeting data-protection obligations means keeping records long enough to prove compliance, but not indefinitely. MobilityManager combines an immutable audit trail, GDPR pseudonymization, and governed retention runs so you can both report on activity and dispose of data on schedule. This article explains how those pieces fit together for compliance reporting.
Required permissions
settings:view— to read the audit trail and produce activity reports.users:manageplus the SystemAdmin role — to run GDPR erasure.belege:compliance-trail— to view the Belege (receipts) compliance dashboard, including retention run status and the access trail.
Reporting from the audit trail
The audit trail is your primary source of compliance evidence. You can assemble reports by:
- Filtering audit entries by entity type, action, user, or date range.
- Pulling the full history of a single record with the entity history view.
- Pulling everything one user did with the per-user history view.
Because entries are immutable and timestamped in UTC, the reports you build from them are defensible.
Governed retention runs
In the Belege (receipts) compliance area, MobilityManager records the outcome of automated retention runs, which delete data that has passed its retention window. Each run is logged with:
| Field | Meaning |
|---|---|
| Run time | When the retention run executed. |
| Outcome | Whether the run succeeded or failed (with an error message on failure). |
| Bookings deleted | How many booking records were purged. |
| Audit entries deleted | How many audit entries were purged. |
You can review the most recent runs from the compliance status view. This gives you an auditable record that retention actually happened.
Note: Retention runs are a governed, logged process. This is different from manual deletion of audit entries, which is always blocked. The audit trail stays immutable; only the scheduled retention process disposes of aged data, and it records what it removed.
Reporting on erasure requests
When you fulfill a GDPR right-to-erasure request, the pseudonymization operation returns statistics — the pseudonym assigned and the number of user, driver, and audit records updated. Capture these figures as evidence that the request was completed across all databases.
Tip: For a complete compliance picture, pair the audit trail (what changed and by whom) with the retention run log (what was disposed of and when) and your record of fulfilled erasure requests.
Related
- Why audit entries cannot be edited or deleted
- The audit trail and what it captures
- GDPR compliance in MobilityManager
- Pseudonymize a user (GDPR right to erasure)
