Reconstruct any record as it stood on any past date
"Here's the current record" is not an answer
When a supervisory authority or an internal investigation asks what a processing activity looked like eighteen months ago, "here's the current record" is not an answer. The obligation is to show the state as it stood on a specific date — the legal basis you relied on then, the recipients you disclosed to then, the vendor terms in force then.
Most teams cannot produce that. They hold a change log — a list of edits — but turning it back into a coherent prior version means reassembling the document by hand. Under audit pressure, that reconstruction is slow, error-prone, and hard to defend as accurate.
The exposure is not only the gap in evidence. It is standing in front of a regulator unable to demonstrate the historical state of your own records.
What you can do with Time Machine
- Set a historical date and scope your records to how they stood that day.
- Reconstruct the exact version of each element in force at or before that date.
- View point-in-time snapshots of ROPA entries and vendor records, not current state.
- Render historical state in the screens you already use — the date context applies transparently.
- Toggle Time Machine on and off from a settings page that shows the active date.
- Answer "what did this say then?" from the record itself, not from change logs.
What it delivers to your program
- Answer point-in-time questions in minutes, not days — auditors see the real historical record, not a manual approximation.
- Defend the historical state of processing records in an investigation with reconstructed versions you can show on screen.
- Retire manual reconstruction from change logs — evidence work that once consumed an analyst now happens on demand.
- Walk into an inspection prepared — past states of your ROPA and vendors are recoverable, not lost to the current view.
Built for compliance
DPMS helps you evidence the specific obligations that govern point-in-time record history — mapped to the article and control, never to "the GDPR."
| What DPMS does | Maps to | How |
|---|---|---|
| Reconstructs records as they existed on a chosen date | GDPR Art. 30 | Point-in-time view of accountability records, not only their current state |
| Returns the version in force at or before a given date | GDPR Art. 5(2) | Aggregation over change history reassembles the latest element version for that date |
| Evidences the historical state of records on demand | ISO 27001:2022 Annex A 5.34 | Date-scoped reconstruction of ROPA and vendor records for investigation and audit |
Why Priverion
Unlike general-purpose GRC tools that store a flat change log and leave reconstruction to you, Time Machine performs true point-in-time reconstruction — aggregating over change history to return the version actually in force on your chosen date. Because it lives inside one unified privacy and InfoSec platform, the date context applies transparently across the ROPA and vendor screens you already use. You do not read diffs to imagine the past; you view the record as it stood.
Questions DPOs ask before a demo
Which records can I reconstruct?
Is this just a change log?
How do I switch it on?
Does it change my current records?
Explore related capabilities
Ready to see your records as they stood?
