Skip to content

docs/design/gdpr_erasure.md: wrong detail — | (e) Legal obligation | Court order. | ... | (f) Child's data offered without parental consent | Subject was a minor at point of collection. | (DOC-BLEGAL-003) #130

Open

Description

@cemililik

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

Summary

The design narrows two erasure grounds: (e) to court orders only, and (f) to cases without parental consent. Requests on the real grounds, a statutory duty or a child's ISS data collected even with consent, could be wrongly rejected.

Primary finding

DOC-BLEGAL-003 — docs/design/gdpr_erasure.md: wrong detail — | (e) Legal obligation | Court order. | ... | (f) Child's data offered without parental consent | Subject was a minor at point of collection. |

severity High

Where. docs/design/gdpr_erasure.md:43-44 · type: wrong detail

The document says. | (e) Legal obligation | Court order. | ... | (f) Child's data offered without parental consent | Subject was a minor at point of collection. |

What the code does. GDPR Art. 17(1)(e): 'the personal data have to be erased for compliance with a legal obligation in Union or Member State law to which the controller is subject'. This covers any statutory erasure duty, and a court order is only one route. Art. 17(1)(f): 'the personal data have been collected in relation to the offer of information society services referred to in Article 8(1)'. It has no parental-consent condition.

User impact. The design narrows two erasure grounds: (e) to court orders only, and (f) to cases without parental consent. Requests on the real grounds, a statutory duty or a child's ISS data collected even with consent, could be wrongly rejected.

Proposed correction. (e): 'Erasure required by a legal obligation under Union or Member State law (statute, regulator or court order).' (f): 'Data collected in relation to information-society services offered to a child (Art. 8(1)), regardless of consent.'

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