Skip to content

docs/reference/configuration.md: false claim — Set to 0 to retain indefinitely (Article 17(3)(b) defence). (DOC-BLEGAL-016) #133

Open

Description

@cemililik

Wave 1 · theme D1-10: Documentation-only fixes · highest severity High · 1 finding(s) · effort docs fix

Summary

Operators may keep personal data in audit logs indefinitely in the belief that Art. 17(3)(b) covers it, which exposes them to storage-limitation and erasure violations.

Primary finding

DOC-BLEGAL-016 — docs/reference/configuration.md: false claim — Set to 0 to retain indefinitely (Article 17(3)(b) defence).

severity High

Where. docs/reference/configuration.md:262 (Turkish mirror: docs/reference/configuration-tr.md:263) · type: false claim

The document says. Set to 0 to retain indefinitely (Article 17(3)(b) defence).

What the code does. Art. 17(3)(b) lifts the erasure duty only 'to the extent that processing is necessary for compliance with a legal obligation' under Union or Member State law. It covers retention for as long as such a law requires. It does not justify indefinite retention.

User impact. Operators may keep personal data in audit logs indefinitely in the belief that Art. 17(3)(b) covers it, which exposes them to storage-limitation and erasure violations.

Proposed correction. Set to 0 to disable the overdue flag (retain indefinitely). GDPR Art. 17(3)(b) can justify retention only to the extent, and for as long as, a specific Union or Member State legal obligation requires it; indefinite retention needs its own justification.

Turkish mirror. the Turkish page has the same error; fix both in the same PR

Acceptance criteria

  • Each statement is re-checked against the code at fix time.
  • Documentation listed above is corrected in English and in its Turkish mirror in the same PR.
  • Every finding in this issue is resolved or explicitly closed with a reason.

Found by the October 2026 ForgeLM code and documentation review against commit cab2947. Code links point at that commit; line numbers may have moved since. Finding IDs (CR-…, DOC-…, TECH-…) are stable references for this backlog.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationseverity: highWrong behaviour or a false claim users rely onsource: review-2026-10Found by the October 2026 code and documentation reviewwave: 1Roadmap wave 1: high severity, small effort

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions