forked from SWISDATA/processintel
pages.privacy: data retention does not match the privacy policy #34
Labels
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
ffrauenberger/ProcessIntel#34
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Severity: medium (the privacy policy promises retention that the code does not enforce)
Where
app/pages/privacy.py:43-52app/pages/main_app.py:16-22module.nix:149-156,:250-265app/mining_algorithms/genetic_mining.py:424-430and otherlogger.debugcalls that dump logsProblem
The privacy page states "Automatic deletion after a maximum of 2 hours" and "No permanent storage". The code does not guarantee this:
st.session_stateas long as the session exists. For an open tab that can be many hours, independent of the 60-minute file timer.startAt = "hourly"and-mmin +60, files can survive almost 2 h, which meets the claim only barely and only for files.debuglogs write complete traces and event data to stdout and therefore to the journal (e.g.[LOG TRACES]in the genetic miner;Succession Matrix,SPM Filtered LoginBaseMining). WithlogLevel = "DEBUG", uploaded process data ends up in system logs with their own retention.Steps to reproduce
Expected behavior
User data is deleted after at most 2 hours, as stated in the privacy policy, and never written to logs.
Actual behavior
Data stays in memory for the lifetime of the session; with debug logging enabled, event data is written to the system journal.
Related: #20, #61.
Fix
Enforce a session time-to-live (clear
session_stateand temp files after N minutes of inactivity), avoid temp files (render to bytes), never log event data (or redact it), and align the policy text with what the code actually guarantees.from
issues/SEC-004-privacy-policy-retention-claims-not-enforced.md(code analysis of commit6bcc646, 2026-10-03)Reviewed by Codex (GPT-6) against origin/main
6bcc646eb464.Review: partially correct.
The retention mismatch is supported. Two details need correction. An hourly timer with
find -mmin +60does not guarantee deletion before two hours: minute-age comparison rounds down, the strict+60test needs age at least 61 minutes, and timer scheduling adds delay. A file missed just before that point can survive slightly beyond two hours; modified files have their age reset.Also, “clear after N minutes of inactivity” is not sufficient to satisfy a maximum lifetime of two hours: an active session could keep extending it. Decide whether the policy promises absolute age since upload or inactivity expiry, implement that specific rule, and account for persisted debug logs separately. This is a code/policy-text review, not a legal compliance determination.
Code references: module.nix:252, module.nix:258, app/pages/privacy.py:48.