Refresh HiveGrid Cloud reference snapshot

This commit is contained in:
david committed 2026-08-03 15:31:14 +02:00
1 parent 5e99e14772
commit 7f88026f79
5955 files changed
+1177325 -188362

No files matched your search

@@ -1,11 +1,13 @@
# DSGVO Bulk-Ops (Self-Service Export, Deletion, Pseudonymisation)
**Phase:** 10 — Compliance Polish
**Status:** active
**Status:** legacy / dormant
This document describes the runtime architecture of the DSGVO bulk-ops
pipeline that delivers the user-facing rights under GDPR Art. 15, 17
and 20.
This document describes a legacy bulk-ops implementation that is not wired into
the current worker runtime. The active user-facing export paths are the P21
privacy export and customer-portal export services: they store bounded objects
with SSE-C and deliver them only through authenticated `200` app routes. Do not
use this document as deployment evidence for those paths.
## Schema
@@ -62,8 +64,8 @@ interface identifier (/48) for `AuditEvent.actorIp` rewrites.
## Worker Pipeline
Three worker jobs (`apps/worker/src/jobs/dsgvo-*.ts`) execute the
heavy lifting:
Three dormant worker jobs (`apps/worker/src/jobs/dsgvo-*.ts`) describe the
legacy implementation:
### 1. `dsgvo-export.ts`
@@ -86,9 +88,10 @@ Bundle layout:
}
```
After completion a presigned URL is minted (7-day validity), emailed
to the user and audited as `EXPORT_PERSONAL_DATA` with
`regulatoryScope=["gdpr"]`, `dataSensitivity="pii"`.
The legacy code mints a presigned URL with seven-day validity and emails it to
the user. It is not runtime-wired and must not be enabled as a fallback for the
active SSE-C P21/portal export contract. Any future reactivation requires a
separate security review and migration to the current authenticated proxy.
### 2. `dsgvo-deletion.ts`