lumen.privacy · Data subject rights & breaches

When the clock is ticking, the system counts along

Data subject requests must be answered within 30 days, breaches reported within 72 hours. lumen.privacy manages both as cases with countdown, ownership and complete documentation.

Data subject rights (Art. 15–22)

Every request a case — no request forgotten

Access, erasure, rectification, objection: every data subject request is managed as a case with request type, ownership and the 30-day deadline. The countdown always shows how much time is left — linked tasks distribute the work across the team.

  • Case management with request type and clear ownership
  • 30-day deadline with a countdown per case
  • Tasks right on the case — delegable and trackable
  • Processing documented and retrievable as evidence
Betroffenenanfragen in lumen.privacy mit 30-Tage-Frist und Zuständigkeit

Data breaches (Art. 33–34)

72 hours. The countdown is running.

A breach is stressful enough — the reporting deadline shouldn't be a memory game. In lumen.privacy you record the incident with severity and status; the 72-hour deadline runs visibly as a countdown until reported or a documented justification exists.

  • Incident capture with severity and status
  • 72-hour reporting deadline as a visible countdown (Art. 33)
  • Notifying data subjects per Art. 34 documented in the same case
  • Incident chronology as evidence for the supervisory authority
Datenpannen-Fall in lumen.privacy mit Schweregrad und Meldefrist

Early access

Deadlines under control before it gets serious

Rehearse the process before the real thing: in the demo we play through one data subject request and one breach end to end.