gdpr: purge expired sign-up, invite and email-change rows #256

Nytt ärende

Stängd

öppnade 2026-09-24 13:03:34 +00:00 av supernaut · 0 kommentarer

supernaut kommenterad

2026-09-24 13:03:34 +00:00

Ägare

Problem

Nothing deletes expired rows from signups, invite_codes and email_change_requests (src/db/schema.ts). Consumed and expired email-change tokens are kept forever. They are hashed, so exposure is low, but keeping them has no purpose. GDPR Art. 5(1)(e) asks for storage limitation.

Done when

A scheduled job deletes rows past expiresAt or consumedAt plus a short grace period.
The retention period is stated in the Privacy Policy's retention section.
A test covers the delete predicate.

## Problem Nothing deletes expired rows from `signups`, `invite_codes` and `email_change_requests` (`src/db/schema.ts`). Consumed and expired email-change tokens are kept forever. They are hashed, so exposure is low, but keeping them has no purpose. GDPR Art. 5(1)(e) asks for storage limitation. ## Done when - A scheduled job deletes rows past `expiresAt` or `consumedAt` plus a short grace period. - The retention period is stated in the Privacy Policy's retention section. - A test covers the delete predicate.

supernaut lade till etiketterna

area/security

area/web

ready-for-implementation

type

task

2026-09-24 13:03:53 +00:00

supernaut lade till detta till projektet Bitborg Web

2026-09-24 13:03:54 +00:00

supernaut refererade till detta ärende från en incheckning

2026-10-02 09:12:10 +00:00

feat(gdpr): purge expired email-change rows and invite codes