feat(privacy): what the farm keeps about testers, for how long, and removing it #138
No reviewers
Labels
No labels
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
priority
critical
priority
high
priority
low
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Beanstalk!138
Loading…
Reference in a new issue
No description provided.
Delete branch "HumanBean/Beanstalk:feat/gdpr-retention"
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?
GDPR: the farm kept testers' data (login, PC name, hardware, last seen, reports with log tails) for good, with no notice and no way to remove it. This adds a privacy notice, retention limits and self-service removal.
What changed
/privacypage: linked from the footer,/howand the agent app's sign-in. It covers what the farm keeps, who sees it, OpenAI's part (PR content, hardware tags and numbers, never a login, PC name, log or picture), Cloudflare and IP addresses (the farm logs none), how long, how to remove it, and [email protected]. It links Longshot's https://longshot.magicbean.dev/privacy.BEANSTALK_AGENT_KEEP_DAYS), never while it holds a lease.BEANSTALK_REPORT_KEEP_DAYS), reports, job attempts and jobs stop naming their tester: they point at a retired, hidden stand-in,ag_removed, and the log tail, the stored envelope and the job's live log are dropped. The numbers, results and hardware model stay. Olddashboard_dispatchesrows are deleted.POST /privacy/remove, with CSRF), from the agent (DELETE /api/v1/agents/me,beanstalk-agent remove), and as "Log out and remove this PC" in the app's log-out dialog. Removal anonymises at once, under the same rules.reports.envelopekept every picture's base64, so the "kept a day" failure pictures actually stayed in the database for good. New reports are stored without them, and migration 0025 strips them from the ones already stored.Still to do before ready
coordinator/tests/test_retention.py,ClientChecks.cs) but not run on the author's PC (its rule); CI runs them./privacy, the remove dialog and the app's link: not built or run yet.hardware.tags, so once anonymised they show no hardware tags.Measurements
The sweep is hourly and indexed by
last_seenandcreated_at(migration 0025). No effect on job dispatch or reports' handling beyond the envelope now being smaller.🤖 Generated with Claude Code
Possibly related, for context:
WIP: feat(privacy): what the farm keeps about testers, for how long, and removing itto feat(privacy): what the farm keeps about testers, for how long, and removing it