Update hivegrid-cloud reference to latest main
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
1 parent
e98d38e716
commit
7b21524c86
3781 files changed
+373484
-225607
No files matched your search
@@ -0,0 +1,30 @@
|
||||
# DSGVO-Auskunft Playbook (v1)
|
||||
|
||||
Stand: 2026-07-02 · Ticket: AK-P21
|
||||
|
||||
Dieses Playbook beschreibt den manuellen v1-Prozess fuer DSGVO-Auskunftsersuchen. Es ist bewusst kein automatisierter Wizard; der Vollausbau folgt in VR-P31/M166.
|
||||
|
||||
## Ziel
|
||||
|
||||
Innerhalb von 30 Tagen eine nachvollziehbare, redigierte Auskunft zu einer betroffenen Person erstellen, ohne Rohdaten in Support-Tickets, Chat oder externe Tools zu kopieren.
|
||||
|
||||
## Ablauf
|
||||
|
||||
1. Eingang erfassen: Support-Ticket im Admin Support Inbox oeffnen, Identitaet und Mandant pruefen, Frist auf +25 Tage setzen.
|
||||
2. Person finden: Cmd+K / globale Suche nutzen, relevante Kontakte, Nutzer, Projekte, Aufgaben, Termine und Dateien notieren.
|
||||
3. Detaildaten sammeln: Kontakt-/User-Detailseiten und Activity-Stream pruefen. Nur notwendige Datenkategorien dokumentieren.
|
||||
4. CSV-Exports nutzen: vorhandene Listenexporte pro Bereich erstellen, lokal pruefen und offensichtliche Drittpersonen-Daten entfernen.
|
||||
5. Antwortvorlage befuellen: anwaltliche DSGVO-Auskunfts-Vorlage verwenden. Keine Daten in freie Support-Kommentare kopieren.
|
||||
6. Review: zweite Person oder Verantwortlicher prueft Inhalt, Rechtsgrundlagen, Ausnahmen und Redaktionen.
|
||||
7. Versand dokumentieren: Versanddatum, betroffene Datenbereiche und Request-ID im Support-Ticket festhalten. Keine Exportdateien dauerhaft anhaengen.
|
||||
|
||||
## Sicherheitsregeln
|
||||
|
||||
- Keine Rohdaten in Plane, Chat, Commit-Messages oder Logs.
|
||||
- Keine signed URLs, Tokens, Cookies, Objekt-Keys oder Provider-Payloads in die Antwortnotiz kopieren.
|
||||
- Exportartefakte nur lokal und temporaer verwenden; nach Abschluss loeschen.
|
||||
- Bei Identitaetszweifel, Drittpersonenbezug oder Rechtsunsicherheit an Datenschutz/Anwalt eskalieren.
|
||||
|
||||
## v2-Abloesung
|
||||
|
||||
VR-P31 ersetzt dieses Playbook durch echte Self-Service-Workflows mit AVV-/Subprozessoren-Verwaltung, Auskunfts-Tooling und Admin-Legal-Flaechen.
|
||||
@@ -20,7 +20,7 @@ The inventory covers user, tenant, authentication, API, file, entity-row, import
|
||||
| Exports | Export jobs and generated files referenced by Compliance Retention baseline tests (`packages/db/src/export-jobs.server.test.ts`, `packages/exports/*`) | Export-related package tests and file-object storage surfaces | Export artifacts can aggregate tenant personal data and require explicit expiration/deletion follow-up. |
|
||||
| Notifications | In-app/email delivery category, message key, status, provider message ID, payload metadata, sent/read timestamps, user preferences | `NotificationDelivery`, `UserNotificationPreference` in `prisma/schema/notifications.prisma` | Payload metadata and provider message IDs can identify users or message content. |
|
||||
| Email and campaigns | Inbound/outbound addresses, names, subjects, text/html bodies, reads, CC recipients, senders, campaigns, opens, clicks, unsubscribe/bounce timestamps | `Email`, `EmailRead`, `EmailCc`, `EmailSender`, `Campaign`, `OutboundEmail`, `OutboundEmailOpen`, `OutboundEmailClick` in `prisma/schema/email.prisma` | Email bodies, addresses, tracking events, and provider configuration are high-risk personal-data surfaces. |
|
||||
| Billing and subscriptions | Stripe customer/subscription/session identifiers, checkout email, from URL, usage records, credits, product entitlement state | `TenantSubscription`, `TenantSubscriptionProduct`, `TenantSubscriptionUsageRecord`, `CheckoutSessionStatus`, `Credit` in `prisma/schema/subscriptions.prisma` | Billing records can link identity, payment-provider identifiers, and usage. |
|
||||
| Billing and subscriptions | Lago customer/subscription/invoice identifiers, Mollie payment identifiers, checkout email, from URL, usage records, credits, product entitlement state | `TenantSubscription`, `TenantSubscriptionProduct`, `TenantSubscriptionUsageRecord`, `CheckoutSessionStatus`, `Credit` in `prisma/schema/subscriptions.prisma` | Billing records can link identity, payment-provider identifiers, invoices, and usage. |
|
||||
| Audit, events, metrics, and impersonation | Logs, event payloads, webhook attempts, metric logs, IP geolocation, impersonation actor/target, request path, metadata | `Log`, `Event`, `EventWebhookAttempt`, `MetricLog`, `IpAddress`, `IpAddressLog`, `ImpersonationAudit` | Audit data is needed for security but can include personal data, URLs, IPs, and payload fragments. |
|
||||
| Optional plugin-candidate surfaces | Knowledge base, workflow, app engine, forms, portals, sites, prompt/AI, help desk, analytics, feature-flag, and onboarding surfaces | baseline report plus schema roots such as `prisma/schema/appsEngine.prisma`; additional schema files under `prisma/schema` | Treat as potentially personal until each plugin-candidate surface has a dedicated data review. |
|
||||
|
||||
@@ -32,7 +32,7 @@ The inventory covers user, tenant, authentication, API, file, entity-row, import
|
||||
- Entity-builder flows process tenant-defined rows, values, comments, tasks, tags, permissions, files, formulas, relationships, and custom schemas. These rows may contain arbitrary personal data because field semantics are tenant-defined.
|
||||
- File, import, export, and email flows process uploaded documents, generated artifacts, object metadata, message bodies, attachments, campaign tracking events, and provider delivery identifiers.
|
||||
- Worker, queue, notification, mail, analytics, metrics, app sync, and webhook flows process operational metadata and delivery state. Raw job payloads, provider payloads, webhook bodies, and source/destination sync data are not safe evidence.
|
||||
- Billing and subscription flows process Stripe-linked customer/subscription/session identifiers, usage records, checkout emails, credits, and entitlement state.
|
||||
- Billing and subscription flows process Lago-linked customer/subscription/invoice identifiers, Mollie payment identifiers, usage records, checkout emails, credits, and entitlement state.
|
||||
|
||||
## Storage evidence
|
||||
|
||||
@@ -61,7 +61,7 @@ The inventory covers user, tenant, authentication, API, file, entity-row, import
|
||||
- User erasure must account for direct user records plus created rows, comments, tasks, entity views, notifications, preferences, API keys, tenant memberships, invitations, impersonation audit actor/target links, email reads, analytics sessions, metrics, formulas, workflows, apps, forms, portals, sites, and optional plugin-candidate surfaces.
|
||||
- Tenant erasure must account for tenant profile, tenant users, invitations, API keys/logs, rows, row permissions, entity views, imports, exports, files, email/campaign data, notifications, billing/subscription records, app sync data, workflow data, portals, forms, sites, and object-store artifacts.
|
||||
- Operational audit data may need restricted retention rather than immediate deletion when required for security, fraud, accounting, or legal defense. That policy is not implemented in this task and must be explicitly defined later.
|
||||
- External providers and object stores require deletion hooks beyond database cascades: Mailjet/mail providers, Stripe, Redis/queue payloads, object storage, analytics providers, and deployment/runtime logs.
|
||||
- External providers and object stores require deletion hooks beyond database cascades: Mailjet/mail providers, Lago, Mollie, Redis/queue payloads, object storage, analytics providers, and deployment/runtime logs.
|
||||
- Deletion evidence must be redacted to status labels, request IDs, job IDs, model/surface labels, counts, and redacted diagnostic codes. Do not include deleted data samples, emails, tenant names, object keys, signed URLs, API keys, webhook bodies, or raw queue payloads.
|
||||
|
||||
## Retention status
|
||||
@@ -89,6 +89,9 @@ Repository-level retention defaults now live in [`docs/data-retention.md`](../da
|
||||
|
||||
## Downstream follow-ups
|
||||
|
||||
- v1 DSGVO-Auskunftsersuchen laufen ueber das manuelle Playbook
|
||||
[`docs/compliance/dsgvo-auskunft-playbook.md`](./dsgvo-auskunft-playbook.md);
|
||||
VR-P31 ersetzt diesen Ablauf durch Self-Service-Tooling.
|
||||
- Implement focused verification that rejects missing data-protection inventory sections and placeholder markers while staying non-E2E.
|
||||
- Define data-subject export scope across users, tenants, entity rows, files, imports, exports, email, notifications, audit data, billing references, and plugin-candidate surfaces.
|
||||
- Define erasure workflows for user and tenant deletion, including soft delete, hard delete, object-store cleanup, provider deletion, queue cleanup, and audit-minimization exceptions.
|
||||
|
||||
Reference in new issue
Block a user