[Privacy] Add governed Addresses DSAR coverage #24

New Issue

2026-08-21T00:53:00+02:00

zemion commented

2026-08-21 00:53:00 +02:00

Outcome

Addresses participates in the provider-neutral data-subject request workflow with tenant-isolated, minimized discovery across authoritative contact records, contact points, governance facts, list use, provenance, merge/sync evidence, and personally attributed configuration.

Acceptance criteria

Publish a versioned privacy.dsar.addresses capability through the manifest.
Corroborate canonical email/account selectors and namespaced contact/contact-point references; fail closed on conflicts.
Search is exact-tenant, capped, deterministic, and excludes connector state, raw source payloads, opaque metadata, snapshot payloads, import plans, and unrelated contacts.
Export matching contact identity/contact points and only the related list, governance, provenance, merge, redirect, and sync evidence needed to explain use.
Distinguish authoritative or shared contact records requiring manual review from immutable quality, merge, sync, and import evidence with explicit retention reasons.
Erasure execution cannot silently delete a shared/synchronized contact or weaken institutional evidence and handles non-executable plans deterministically.
Static administrator documentation explains selector coverage, exclusions, retention, and manual remediation.
Tests cover tenant isolation, selector conflicts, minimization, unrelated-contact exclusion, classifications, disabled-provider coverage, and foreign actions.
Addresses tests, manifest checks, and the focused workspace gate pass.

Parent umbrella: GovOPlaN/govoplan#47 ## Outcome Addresses participates in the provider-neutral data-subject request workflow with tenant-isolated, minimized discovery across authoritative contact records, contact points, governance facts, list use, provenance, merge/sync evidence, and personally attributed configuration. ## Acceptance criteria - [x] Publish a versioned `privacy.dsar.addresses` capability through the manifest. - [x] Corroborate canonical email/account selectors and namespaced contact/contact-point references; fail closed on conflicts. - [x] Search is exact-tenant, capped, deterministic, and excludes connector state, raw source payloads, opaque metadata, snapshot payloads, import plans, and unrelated contacts. - [x] Export matching contact identity/contact points and only the related list, governance, provenance, merge, redirect, and sync evidence needed to explain use. - [x] Distinguish authoritative or shared contact records requiring manual review from immutable quality, merge, sync, and import evidence with explicit retention reasons. - [x] Erasure execution cannot silently delete a shared/synchronized contact or weaken institutional evidence and handles non-executable plans deterministically. - [x] Static administrator documentation explains selector coverage, exclusions, retention, and manual remediation. - [x] Tests cover tenant isolation, selector conflicts, minimization, unrelated-contact exclusion, classifications, disabled-provider coverage, and foreign actions. - [x] Addresses tests, manifest checks, and the focused workspace gate pass.

zemion commented

2026-08-21 01:21:46 +02:00

Implemented and pushed in 8740fb3 (feat(addresses): add governed DSAR coverage).

The provider publishes privacy.dsar.addresses, performs exact-tenant and fail-closed subject discovery, exports minimized related contact/governance/provenance/sync data, excludes raw/opaque/source/connector payloads and unrelated people, and deliberately routes reusable contact changes to dependency-aware manual review. Immutable governance, quality, merge, redirect, sync, import, snapshot, and attribution evidence carries explicit retention reasons.

Verification: 65 Addresses tests passed; manifest/architecture/information-governance checks passed; the full focused workspace gate passed, including 59 WebUI permutations and 7 browser conformance tests.

Implemented and pushed in `8740fb3` (`feat(addresses): add governed DSAR coverage`). The provider publishes `privacy.dsar.addresses`, performs exact-tenant and fail-closed subject discovery, exports minimized related contact/governance/provenance/sync data, excludes raw/opaque/source/connector payloads and unrelated people, and deliberately routes reusable contact changes to dependency-aware manual review. Immutable governance, quality, merge, redirect, sync, import, snapshot, and attribution evidence carries explicit retention reasons. Verification: 65 Addresses tests passed; manifest/architecture/information-governance checks passed; the full focused workspace gate passed, including 59 WebUI permutations and 7 browser conformance tests.

zemion closed this issue

2026-08-21 01:21:47 +02:00

zemion referenced this issue from GovOPlaN/govoplan

2026-08-21 01:21:47 +02:00

[Privacy] Complete DSAR provider coverage across data-owning modules #47

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-addresses#24