Settlement Archive DSAR Claimant Access UI

Quick answer

Archived DSAR UI handles privacy requests years after portal closure—when claimants no longer log in but still have rights to their data. Design DSAR-ARC- request queues* that search ARC-* packages, assemble redacted export bundles, or respond with PRF-DST-* destruction certificates when DST-* jobs already ran. Privacy admins need identity verification stronger than a live account—pair with email OTP and IDV step-up patterns without reopening CLM-* workflows. Start from the Figma guides hub and reuse privacy request queue and DSAR portal layouts.

Who this is for

Product designers building post-closure settlement systems that still receive GDPR/CCPA access and erasure requests.
Privacy and legal ops triaging DSAR-ARC-* cases against immutable PKG-* snapshots without mutating archive integrity.
Settlement administrators coordinating responses that reference court-approved retention—not live claimant dashboards.

Archived DSAR lifecycle overview

ArchivedDsarProgram — DSAR-ARC-992 · settlement_id: SET-992 · Status: Active intake
├── Triggers:
│   ├── Claimant submits request via public DSAR form (post WIN-* hard close)
│   ├── Privacy team receives forwarded mail from [notice FAQ](/designing-breach-faq-and-notice-landing-page-ui-in-figma/)
│   ├── Regulator inquiry references specific CLM-* or PAY-* ID
│   └── [Privacy queue](/designing-privacy-request-queue-and-case-management-ui-in-figma/) routes settlement-tagged case
├── ID namespace:
│   ├── DSAR-ARC-* (archived settlement privacy case)
│   ├── IDV-ARC-* (identity verification attempt)
│   ├── LKP-ARC-* (PKG-* lookup result)
│   ├── EXP-ARC-* (export bundle job) · RED-ARC-* (redaction manifest)
│   ├── RSP-ARC-* (response letter template) · LOG-DSAR-ARC-* (access audit)
│   └── PRF-LINK (pointer to PRF-DST-* if destroyed)
├── Request types:
│   ├── Access / portability — EXP-ARC-* from PKG-*
│   ├── Rectification — usually "cannot amend archived record" + process note
│   ├── Erasure — check HLD-* · RET-* · DST-* status
│   ├── Restriction / objection — document legal basis · link [objection UI](/designing-objection-and-restrict-processing-ui-in-figma/)
│   └── Third-party authorized agent — extra IDV-ARC-* + authorization doc
├── Resolution paths:
│   ├── Found in PKG-* → redacted EXP-ARC-* + RSP-ARC-*
│   ├── Partial (logs destroyed) → explain RET-* schedule in RSP-ARC-*
│   ├── Already DST-* → PRF-DST-* certificate + tombstone index
│   └── Not found → negative search attestation · no false "never existed"
└── Outcomes:
    ├── DSAR-ARC-* closed within SLA · LOG-DSAR-ARC-* complete
    ├── No PKG-* mutation · hash chain intact
    └── Regulator-ready audit trail for [compliance exports](/designing-compliance-exports-and-legal-hold-ui-in-figma/)

DSAR-ARC state	Claimant sees	Admin can
Intake	Confirmation · expected timeline	Assign · request IDV
IDV pending	OTP / document upload prompt	Review IDV-ARC-*
Lookup	Status “searching archive”	Run LKP-ARC-* across PKG-*
Export prep	—	Build EXP-ARC-* · RED-ARC-* review
Response sent	Download link or letter	Close · LOG-DSAR-ARC-*
Destroyed cert	PRF-DST-* summary	No re-export

Verdict: Archived DSAR is read-only archaeology—never reopen PAY- or edit CLM- inside PKG-*.**

Public intake form and post-closure claimant UX

ArchivedDsarIntake — form_id: DSAR-ARC-PUBLIC · settlement: SET-992 (closed)
├── Header:
│   ├── "This settlement program closed on [date]" · link [notice FAQ](/designing-breach-faq-and-notice-landing-page-ui-in-figma/)
│   ├── Expected response time (30/45 days per jurisdiction)
│   └── Languages · accessibility · [cookie consent](/designing-cookie-consent-and-tracking-preference-ui-in-figma/) if tracking
├── Required fields:
│   ├── Full legal name (as on original claim)
│   ├── Email for response · optional phone
│   ├── Claim ID (CLM-*) if known · optional last-4 SSN / DOB for match
│   ├── Request type (access · erasure · other)
│   └── Free-text description · authorized agent checkbox
├── Identity path (no live account):
│   ├── Email OTP ([verification UI](/designing-email-verification-and-otp-ui-in-figma/))
│   ├── Upload government ID (IDV-ARC-* · [file upload](/designing-file-upload-and-drag-drop-ui-in-figma/))
│   └── Optional: answer security questions from original claim
├── Disclosures:
│   ├── Records may exist only in archive · not real-time portal
│   ├── Erasure may be impossible under court retention order
│   └── Link [privacy settings](/designing-privacy-settings-and-data-management-ui-in-figma/) patterns for active products
└── Submit:
    ├── DSAR-ARC-* created · confirmation email
    └── Route to [privacy queue](/designing-privacy-request-queue-and-case-management-ui-in-figma/) with SET-992 tag

Use forms patterns for validation states and inline alerts when settlement ID is invalid or program never existed.

Admin DSAR-ARC-* case workspace

DsarArcCase — DSAR-ARC-992-0042 · requestor: Jane Doe · type: Access
├── Case header:
│   ├── SLA countdown · jurisdiction (GDPR · CCPA · state)
│   ├── Settlement ref SET-992 · ARC-992-001 link
│   ├── IDV-ARC-* status (verified · failed · escalated)
│   └── Assignee · legal review flag
├── LKP-ARC-* lookup panel:
│   ├── Search PKG-* index by name · CLM-* · email hash
│   ├── Match confidence score · multiple CLM-* disambiguation
│   ├── Preview redacted snippets (never full PII in list view)
│   └── "No match" workflow → negative attestation template
├── Export builder (EXP-ARC-*):
│   ├── Select PKG-* sections: claim summary · payments · correspondence
│   ├── RED-ARC-* auto-redact third-party PII · counsel names if sealed
│   ├── Machine-readable JSON + human PDF ([portability](/designing-data-portability-and-machine-readable-export-ui-in-figma/))
│   ├── Dual approval for bulk or sensitive exports
│   └── Time-limited secure download · watermark
├── Erasure branch:
│   ├── Check HLD-* active → deny with legal basis in RSP-ARC-*
│   ├── Check RET-* not elapsed → explain schedule
│   ├── If DST-* completed → attach PRF-DST-* · tombstone ref
│   └── If eligible isolated record → escalate (rare · legal only)
├── Response composer (RSP-ARC-*):
│   ├── Template by outcome · merge fields
│   ├── Plain-language summary for claimant
│   └── Internal notes · LOG-DSAR-ARC-* on send
└── Activity:
    ├── Every PKG-* view logged · break-glass if bulk
    └── Export to [compliance export](/designing-compliance-exports-and-legal-hold-ui-in-figma/) for regulator packet

Pair case tables with figma tables and search UI for PKG-* index browsing.

Comparison: live DSAR vs archived settlement DSAR

Dimension	Live DSAR portal	DSAR-ARC-* (this pattern)
Identity	Logged-in account	OTP + IDV-ARC-* + claim match
Data source	Operational DB	PKG-* snapshot only
Erasure	May queue deletion jobs	Usually blocked · RET-* / HLD-*
Amendment	Profile edit flows	”Cannot amend archived CLM-*“
SLA clock	Standard privacy SLA	Same · document archive search time
Audit	Privacy queue	LOG-DSAR-ARC-* + LOG-ARC-*

Redaction and third-party PII rules (RED-ARC-*)

Design RED-ARC- manifests* visible to legal reviewers before export:

Always redact: other claimants’ names, bank full account numbers, unrelated CLM-* in shared PDFs.
Conditional: call center agent names, fraud investigator notes, sealed court exhibits.
Never include: live admin credentials, internal FIND-* from QA sampling unless legally required.

Show side-by-side before/after redaction preview with legend—reuse content classification label chips on sections.

Common mistakes

Letting claimants “log in” to a fake portal after hard close—use dedicated DSAR form only.
Exporting unredacted PKG- slices* because search was faster than RED-ARC-* review.
Promising erasure when court order requires 7-year RET-* on payment records.
No PRF-DST- path* when data was destroyed—claimants assume you’re hiding records.
Reusing live DSAR templates that reference “account settings” links that no longer exist.

Recommended workflow

Extend public DSAR form with settlement-closed variant and SET-* selector or deep link from FAQ.
Build DSAR-ARC- case workspace* in privacy queue with LKP-ARC-* and EXP-ARC-* flows.
Wire IDV-ARC-* to claimant IDV components without enabling claim edits.
Prototype RED-ARC- review* modal with legal sign-off and dual approval for sensitive exports.
Add PRF-DST- response branch* with tombstone lookup from archive UI.
Document SLA and jurisdiction variants in RSP-ARC-* templates for handoff via Dev Mode.

FAQ

Can claimants still use the settlement portal for DSAR?

No after hard close · Direct to DSAR-ARC-* form · WIN-* redirect explains why.

What if multiple CLM-* match the same name?

Disambiguation UI · last-4 · DOB · address fragment · never show other claimant’s full record in picker.

Erasure request on archived payments?

Usually deny with RET-* / court order citation · Partial deletion of logs only if law allows · Legal must approve.

Authorized agent requests?

Upload authorization + agent ID · Same IDV bar · LOG-DSAR-ARC-* both parties.

Regulator wants all DSAR-ARC-* for SET-992?

Bulk compliance export · not claimant EXP-ARC-* · compliance exports UI.

Response language requirements?

RSP-ARC- locale* matches intake · link translated notice FAQ where available.

Next steps

Design breach settlement archive and long-term record retention UI in Figma — PKG-* source for LKP-ARC-*
Design privacy request queue and case management UI in Figma — Parent queue for DSAR-ARC-*
Design proof of deletion and audit trail UI in Figma — PRF-DST-* certificates
Design data subject access request and GDPR portal UI in Figma — Live DSAR patterns to adapt
Design breach settlement litigation discovery and DSQ export UI in Figma — Counsel-side archive exports

Designing breach settlement archived DSAR and claimant access UI in Figma: DSAR-ARC-* requests, redaction bundles, and PRF-DST-* responses