Project and task data is kept forever, with no retention period

[rubenvdlinde]

Planninq sets no retention period on any of its schemas. Projects, tasks and time entries keep the names of the people on them for as long as the instance lives.

This is a code reading of planninq development at f936e09 and openregister development at d611a36, from the planninq timetabling competitor scan (#665, matrix row plt-retention-anonymise).

The competitors

The planninq matrix rates Zermelo unknown, Untis partial, Xedule yes and TimeEdit partial:

• Xedule: "per ORE een bewaartermijn (van 1 tot 10 jaar) ... voor het automatisch anonimiseren van privacygevoelige gegevens" (https://support.xedule.nl/hc/nl/articles/36237385246738-Beheer-Configuratie-Databeheer)
• Untis deletes messages after one year by a fixed rule (https://help.untis.at/hc/de/articles/360016832360)
• TimeEdit anonymises expired persons after a retention period in its Evaluation product (https://www.academy.timeedit.com/guides-tutorials/how-to-get-insight-in-data-in-background)

What planninq has

• lib/Settings/planninq_register.json declares seven schemas. None carries an archival or retention block: a search for archival and retention in the file finds nothing.
• The schemas hold personal data: task.assignedTo, task.reporter, task.watchers, project.owner, project.members, plannedTimeEntry.user.

What the platform offers

• openregister deletes rows past their retention for a schema that declares x-openregister-archival, in an hourly sweep (lib/BackgroundJob/ArchivalRetentionTask.php, class docblock).
• openregister can pseudonymise one data subject's fields on request (openspec/specs/gdpr-data-subject-rights/spec.md:82, :102-103).
• Neither anonymises data automatically after a period.

How I searched

A search of planninq src/, lib/ and appinfo/ for anonymi|retention|bewaartermijn|archival, a read of the register, and a read of openregister's retention job and data subject spec.

Live check

Confirm the live task schema has no archival block, and that no job removes or anonymises a task closed years ago.

[github-actions]

Thank you for opening this issue! It has been assigned to @rubenvdlinde for review.

What happens next:

1. A maintainer will review this issue and determine the appropriate action
2. If accepted, it may be converted into an OpenSpec change for structured development
3. You will be notified of any status changes

Triage labels:

• triage:accept-feature — accepted as a new feature
• triage:accept-bugfix — accepted as a bug fix
• triage:needs-info — more information needed
• triage:wontfix — will not be addressed
• triage:duplicate — duplicate of another issue