Legal Register
Control Workpaper
OBL-19 Rule 8 — inactivity AND separate retention RULE-8

OBL-19: Account Inactivity Deletion & De-identification (Rule 8)

Enforces automated data erasure after prolonged account inactivity under Rule 8.

Statutory scope: Rule 8 — inactivity AND separate retention · Assigned to Records / storage owner · Systems: Marketing Automation Engine (SYS-003); Foreign-Region Secondary Backup Replica (SYS-008); Restore Quarantine & Sandbox Store (SYS-014)

Operational Interface Requirement

Recommended interface: Restore a pre-withdrawal snapshot without complete current history; expected outcome is quarantine. Hold release reopens review, not automatic erasure.

Expected Audit Assertion / Test Result

Restore a pre-withdrawal snapshot without complete current history; expected outcome is quarantine. Hold release reopens review, not automatic erasure.

Governance & Architecture

Recommended Activity Owner
Records / storage owner
Target Systems & Interfaces

Verification Specification & Workpaper

Proposed Test Specimen ID
SPEC-Q10-OBL-19

proposed per-row review/acceptance specification; not a claim of executed statutory coverage

Populated Teaching Workpaper
out/dossier/CASE-001/retention-decisions.json

populated hypothetical decision/specimen; not actual enterprise execution

Local Execution Reference
out/dossier/CASE-001/tests/results.json

Canonical Statutory Grounding

Source references verified against the official Gazette of India publication baseline.

RULE-8 Lines 1142–1166
Commencement: 2027-05-13 (scheduled, not yet operative)
Obligated Actor

Data Fiduciary (processing itself or through processor)

Trigger Context

Class inactivity or any processing for r8(3)

Statutory Conditions

Third Schedule class/purpose/period; 48-hour warning; separate minimum one-year personal/traffic/other-log retention from processing for Seventh Schedule purposes.

Statutory Exceptions

Legal-retention exception; further retention under other law or Government notification in (3).