Personal data export for access and portability requests (GDPR Art. 15/20, nDSG) (research first) #1023

Closed
opened 2026-10-27 00:39:26 +00:00 by Cordy · 4 comments
Owner

From the #695 OpenCloud comparison (item 17, kept 2026-10-27). Today, access and portability requests are handled by hand (docs/handbook/data-protection-operators.md:340).

Research:

  • What GDPR Art. 15/20 and the nDSG require.
  • What Nextcloud, OpenCloud and M365 offer.
  • Self-service export versus an admin-run export of one person's data: profile, devices, shares, group memberships and the audit entries about them.
  • The format, and how to deliver it safely.

Part of the compliance cluster with #847 and #876.

From the #695 OpenCloud comparison (item 17, kept 2026-10-27). Today, access and portability requests are handled by hand (`docs/handbook/data-protection-operators.md:340`). **Research:** - What GDPR Art. 15/20 and the nDSG require. - What Nextcloud, OpenCloud and M365 offer. - Self-service export versus an admin-run export of one person's data: profile, devices, shares, group memberships and the audit entries about them. - The format, and how to deliver it safely. Part of the compliance cluster with #847 and #876.
Author
Owner

Research (2026-10-29)

Law (VERIFIED): GDPR Art. 12 (one month, +2; free; electronic → electronic), Art. 15 (copy + information items; 15(4) others' rights → redact, never refuse), Recital 63 (remote self-service "where possible"), Art. 20 (data provided incl. observed; not for public-task processing, 20(3)); EDPB 01/2022 (signing in is sufficient verification; logs in scope; layered answers OK); CJEU C-487/21 (faithful, intelligible copy) and C-579/21 (dates/purposes of consultations; employee names only after balancing). nDSG Art. 25-29 + DSV 16-21 (30 days, free, comprehensible; portability includes data obtained while using a service); cantonal bodies → cantonal law. The operator is the controller; a processor must assist (Art. 28(3)(e), DSV 17(2)).
Market: Nextcloud user_migration (self-service, writes the archive into the user's files, includes others' comments), OpenCloud exportPersonalData (self only, JSON into personal space), M365 admin-run DSR tools, Google Takeout (self-service, admin can block; 7 days / 5 downloads). Nobody does both routes for a self-hosted product; none include audit entries.
Pitfalls: forged requests (study: ~25% disclosed without verification), wrong-person exports (Amazon 2018), third parties in exports, tipping off investigations, huge exports.
Cairn inventory: 37 places hold data about a person (accounts, first sign-ins, devices, pauses, shares made/received, spaces, bells, favourites, Activity, audit entries by and about them, marks, locks, holds, trash, OCM, peering, restore notices, avatar …). Gap: the audit query can't answer "entries about X" (needs a subject matcher).

Recommended design: both routes, one engine.

  • Self-service (Account › Your data): fresh confirmation, async job, ZIP (README in the user's language with the Art. 15 / DSG 25 items and a glossary, manifest, JSON + CSV per category, file inventory without contents), held as sealed state (never in the user's files), 7 days / 5 downloads, one per 24 h. Excludes holds, leak-tracing and admin investigative entries; others' addresses always dropped.
  • Admin-run (Users & access › person, incl. departed): options include file contents, holds, administrators' names (default "an administrator"), others' downloads; required reason; bell to the person (skippable with reason for investigations).
  • New admin-tier audit verbs; operator setting for controller/contact/purposes text.

Open questions (recommendations): both routes → yes; self-service audit scope → others' actions in their folders, no admin/investigative verbs; admin names → off by default; file contents → admin-run only (optional); delivery → never into the user's files; ZIP encryption → not in v1; frequency → 24 h, controller decides "excessive"; toggle → self-service on by default, switchable; notify on admin export → yes; Art. 15 info text → operator setting; structured audit subject field → follow-up.

## Research (2026-10-29) **Law (VERIFIED):** GDPR Art. 12 (one month, +2; free; electronic → electronic), Art. 15 (copy + information items; 15(4) others' rights → redact, never refuse), Recital 63 (remote self-service "where possible"), Art. 20 (data provided incl. observed; **not** for public-task processing, 20(3)); EDPB 01/2022 (signing in is sufficient verification; logs in scope; layered answers OK); CJEU C-487/21 (faithful, intelligible copy) and C-579/21 (dates/purposes of consultations; employee names only after balancing). nDSG Art. 25-29 + DSV 16-21 (30 days, free, comprehensible; portability includes data obtained while using a service); cantonal bodies → cantonal law. The operator is the controller; a processor must assist (Art. 28(3)(e), DSV 17(2)). **Market:** Nextcloud user_migration (self-service, writes the archive into the user's files, includes others' comments), OpenCloud `exportPersonalData` (self only, JSON into personal space), M365 admin-run DSR tools, Google Takeout (self-service, admin can block; 7 days / 5 downloads). Nobody does both routes for a self-hosted product; none include audit entries. **Pitfalls:** forged requests (study: ~25% disclosed without verification), wrong-person exports (Amazon 2018), third parties in exports, tipping off investigations, huge exports. **Cairn inventory:** 37 places hold data about a person (accounts, first sign-ins, devices, pauses, shares made/received, spaces, bells, favourites, Activity, audit entries by and about them, marks, locks, holds, trash, OCM, peering, restore notices, avatar …). Gap: the audit query can't answer "entries about X" (needs a subject matcher). **Recommended design:** both routes, one engine. - **Self-service** (Account › Your data): fresh confirmation, async job, ZIP (README in the user's language with the Art. 15 / DSG 25 items and a glossary, manifest, JSON + CSV per category, file inventory without contents), held as sealed state (never in the user's files), 7 days / 5 downloads, one per 24 h. Excludes holds, leak-tracing and admin investigative entries; others' addresses always dropped. - **Admin-run** (Users & access › person, incl. departed): options include file contents, holds, administrators' names (default "an administrator"), others' downloads; required reason; bell to the person (skippable with reason for investigations). - New admin-tier audit verbs; operator setting for controller/contact/purposes text. **Open questions (recommendations):** both routes → yes; self-service audit scope → others' actions in their folders, no admin/investigative verbs; admin names → off by default; file contents → admin-run only (optional); delivery → never into the user's files; ZIP encryption → not in v1; frequency → 24 h, controller decides "excessive"; toggle → self-service on by default, switchable; notify on admin export → yes; Art. 15 info text → operator setting; structured audit `subject` field → follow-up.
Author
Owner

Decision (Nikola, 2026-10-29): the recommendations above are approved (both routes on one engine). Next: whole-page mockup (Account › Your data, admin export dialog), then spec and build.

**Decision (Nikola, 2026-10-29):** the recommendations above are approved (both routes on one engine). Next: whole-page mockup (Account › Your data, admin export dialog), then spec and build.
Author
Owner

Mockup approved (Nikola, 2026-10-29): design-direction-decision-needed/1023-personal-data-export-mockup.html, all frames, with the recommendations for its 16 open questions (new tab Users & access › Personal data; rail "Your data"; admin delivery "On their Account page" (default) or "To me, to hand over" (only choice for departed); handover link + 8-character code shown once, 5 wrong codes lock it; fresh confirmation for the admin, no second approver; file contents as ZIP parts ≤ 4 GB, home only, space checked up front; switching self-service off keeps ready copies; 24 h slot counted from ready; README in the person's language; others' changes included without addresses; admin look-ups (C-579/21) not in v1, named as omission; bell not switchable, no admin name or reference; all verbs admin tier in group data; fixed limits shown read-only; departed during IdP outage allowed with warning; everyone who can sign in gets Your data). Next: spec and plan, then build.

**Mockup approved (Nikola, 2026-10-29):** `design-direction-decision-needed/1023-personal-data-export-mockup.html`, all frames, with the recommendations for its 16 open questions (new tab Users & access › Personal data; rail "Your data"; admin delivery "On their Account page" (default) or "To me, to hand over" (only choice for departed); handover link + 8-character code shown once, 5 wrong codes lock it; fresh confirmation for the admin, no second approver; file contents as ZIP parts ≤ 4 GB, home only, space checked up front; switching self-service off keeps ready copies; 24 h slot counted from ready; README in the person's language; others' changes included without addresses; admin look-ups (C-579/21) not in v1, named as omission; bell not switchable, no admin name or reference; all verbs admin tier in group `data`; fixed limits shown read-only; departed during IdP outage allowed with warning; everyone who can sign in gets Your data). Next: spec and plan, then build.
Author
Owner

Shipped in v0.6.375 (PR #1051). Both dogfoods run v0.6.375; pods ready, only the known WARN lines.

For the person (Account › Your data)

  • Request a copy of your personal data. This needs a fresh confirmation (password, or for identity-provider accounts a sign-in within the last 10 minutes).
  • The copy can be downloaded for 7 days or 5 times, and one copy can be requested per 24 h. A HEAD request never counts as a download.
  • Self-service is on by default and can be switched off.

For administrators

  • Exports start from Users & access: the row menu, the Departed users block, or the Personal data tab.
  • Each export records the request type, a reference and the options (file contents, holds, administrator names, reads of the person's files).
  • Told or not: the person is told by default. "Don't tell" needs a reason. Departed and deleted accounts are never told and get a handover link only.
  • Delivery: to the person's Account page, or by a handover link with an 8-character code. The link locks after 5 wrong codes, uses a scoped cookie, and its token is redacted in every log.
  • Only the administrator who started an export can download it.

The copy

  • Data ZIP:
    • README in the person's language, with the operator's texts filled in under Personal data settings.
    • manifest.json with a SHA-256 per file.
    • JSON and CSV for 20 parts covering the 37 data places, now including the e-mail address and language from #896.
  • File contents go in separate parts of at most 4 GB, from the home folder only, read as the owner so per-user keys work.
  • Third parties are redacted:
    • other people's addresses;
    • "an administrator" instead of admin names;
    • visitors to public links;
    • share tokens shown as hashed ids;
    • holds, leak tracing and untold exports left out of the person's own copy.

Engine: async with a lease and resumable parts across instances (#742), files sealed with age on s3, audit group data (12 verbs, admin tier), and bells for both sides.

Docs: docs/handbook/personal-data-export.md, a GDPR Art. 15/20 and nDSG Art. 25/28 mapping in compliance-support.md and data-protection-operators.md, and ARCHITECTURE.md.

Upgrade note: self-service is on by default. Fill in the README texts (controller, contact, purposes, authority) under Users & access › Personal data before announcing it, or switch it off.

The live checks are in #1005. Closing.

**Shipped in v0.6.375** (PR #1051). Both dogfoods run v0.6.375; pods ready, only the known WARN lines. **For the person (Account › Your data)** - Request a copy of your personal data. This needs a fresh confirmation (password, or for identity-provider accounts a sign-in within the last 10 minutes). - The copy can be downloaded for 7 days or 5 times, and one copy can be requested per 24 h. A HEAD request never counts as a download. - Self-service is on by default and can be switched off. **For administrators** - Exports start from Users & access: the row menu, the Departed users block, or the Personal data tab. - Each export records the request type, a reference and the options (file contents, holds, administrator names, reads of the person's files). - **Told or not:** the person is told by default. "Don't tell" needs a reason. Departed and deleted accounts are never told and get a handover link only. - **Delivery:** to the person's Account page, or by a handover link with an 8-character code. The link locks after 5 wrong codes, uses a scoped cookie, and its token is redacted in every log. - Only the administrator who started an export can download it. **The copy** - Data ZIP: - README in the person's language, with the operator's texts filled in under Personal data settings. - `manifest.json` with a SHA-256 per file. - JSON and CSV for 20 parts covering the 37 data places, now including the e-mail address and language from #896. - File contents go in separate parts of at most 4 GB, from the home folder only, read as the owner so per-user keys work. - Third parties are redacted: - other people's addresses; - "an administrator" instead of admin names; - visitors to public links; - share tokens shown as hashed ids; - holds, leak tracing and untold exports left out of the person's own copy. **Engine:** async with a lease and resumable parts across instances (#742), files sealed with age on s3, audit group `data` (12 verbs, admin tier), and bells for both sides. **Docs:** `docs/handbook/personal-data-export.md`, a GDPR Art. 15/20 and nDSG Art. 25/28 mapping in `compliance-support.md` and `data-protection-operators.md`, and ARCHITECTURE.md. **Upgrade note:** self-service is on by default. Fill in the README texts (controller, contact, purposes, authority) under Users & access › Personal data before announcing it, or switch it off. The live checks are in #1005. Closing.
Cordy closed this issue 2026-10-30 02:46:45 +00:00
Sign in to join this conversation.
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#1023
No description provided.