PRIVACY REQUESTS — FICTIONAL CASE RECORD OUTLINE

This is an illustrative reading aid, not an actual customer record,
the application's export schema, a legal opinion, or proof of compliance.
The app provides JSON and printable HTML exports from Case record.

Reference: EXAMPLE-ACCESS-001
Request: A customer asks for a copy of their account information.
Owner: Example operations owner
Reviewer: Example authorized reviewer (Legal Reviewer role)

Intake
- Original request received through the hosted portal.
- Scope and contact details reviewed by staff.
- Suggested deadline reviewed; exceptions require a recorded rationale.

Verification
- Requester contact confirmed.
- Identity evidence and request scope reviewed.
- Staff verification decision and notes recorded.

Fulfillment
- Customer-record search assigned to the responsible owner.
- Task completed; relevant evidence attached to the case.
- Unrelated information excluded from the response.

Response review
- Response text prepared and selected attachments checked.
- Human reviewer approval recorded.

Delivery
- Expiring secure link created with passcode protection.
- Access and download activity recorded separately from link creation.
- Link revoked when access was no longer needed.

Closure
- Current record exported.
- Closure requirements reviewed for the selected outcome.
- Final note and outcome retained in the case history.

The organization remains responsible for verification, legal decisions,
disclosure scope, security configuration, and retention requirements.