Incident log redaction is the removal of personal data from an investigation record. What sits behind the log depends on what the incident is: a workplace safety event may need reporting to the HSE under the Reporting of Injuries, Diseases and Dangerous Occurrences Regulations 2013 (RIDDOR), while a personal-data incident engages the breach-notification duties in UK GDPR Art. 33 and Art. 34. Either way, once the record is anonymous under Recital 26 it falls outside that scope. anonym.plus runs locally and keeps the time-stamped event chain the entries hold.
When this applies
An incident record names the people involved, the reporter, and the responders — whether it is a RIDDOR-reportable safety event or a data incident feeding an Art. 33/34 assessment. To share lessons learned, you clear those names but keep the timeline.
How anonym.plus handles it
- Load the file into anonym.plus on your device.
- The tool flags every named person in the entries.
- Shift event times while you keep the gaps.
- Swap or black out the confirmed names.
- Save the clean copy on your device.
What you need to provide
- The file (CSV, XLSX, PDF, or export).
- A date-shift option to keep elapsed-time analysis.
- An operator (Replace keeps each entry readable).
PII entity types detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | person involved → [PERSON_1] |
| Names | PERSON | responder → [STAFF] |
| Dates | DATE_TIME | 21:14 03/02 → shifted [TIME] |
| Contact | EMAIL_ADDRESS | reporter email → [EMAIL] |
| Location | LOCATION | incident site → [SITE] |
| Identifiers | UK_NINO | staff no. → [ID] |
Compliance achieved
- Anonymous output falls outside scope by UK GDPR Recital 26.
- For a safety event, keeps the record RIDDOR 2013 reporting relies on readable; for a data incident, supports the UK GDPR Art. 33/34 breach-notification record.
- Date-shift keeps elapsed-time gaps for analysis.
- On-device AES-256-GCM guards the working files.
- Runs offline — the file never reaches a cloud service.
Anonymise incident logs offline — see plans & start free →
Limitations & cautions
A record often holds places and bystander names as indirect clues. Date-shift keeps the gaps but breaks links to outside systems unless you shift those by the same offset. Review free-text entries by hand.
Frequently asked questions
Does RIDDOR or UK GDPR apply to my incident log?
It depends on what happened. RIDDOR 2013 governs reportable workplace injuries and dangerous occurrences, notified to the HSE. A personal-data incident instead engages UK GDPR Art. 33 (notifying the ICO) and Art. 34 (notifying the individual). Some incidents trigger both regimes at once.
How does date-shift keep the file useful?
Each entry's times move by one steady offset. The minutes between events stay, so analysis works while the real times are hidden.
Can I clean a whole record at once?
Yes. CSV, XLSX, and PDF files run locally in one pass on your device.