Improve Privacy Data Rights

Goal

Fix the selected privacy/data-rights boundary across collection, storage, derived data, external providers, user/admin controls, tests, and documentation when directly affected.

Scope selection

Use the selected data field, consent setting, deletion/export flow, retention job, audit finding, failing test, or explicit privacy bug. Stop for missing legal/product decisions instead of inventing policy.

Change targets

• Data collection/validation, storage schemas, access controls, retention/deletion/export jobs, and derived stores.
• Provider adapters and webhooks that receive or delete the selected data.
• Logs/traces/analytics/error reports that may expose sensitive payloads.
• User/admin UI, copy, privacy settings, and operational docs when they implement the same boundary.
• Tests/fixtures proving primary and derived behavior.

Implementation principles

• Minimize data exposure and preserve necessary compatibility.
• Do not claim legal compliance; implement repository-visible behavior and state remaining gates.
• Avoid broad data migrations unless the selected fix requires a safe migration/forward-fix plan.
• Keep maps/docs synchronized when used.

Validation

Run targeted tests and safe scenarios for collection, consent/opt-out, export/deletion/retention, derived stores, logs, and provider behavior relevant to the selected boundary. Report unavailable managed-provider or backup checks as gates.

Correct the owning collector, access/retention rule, export/delete transaction or provider adapter using distinguishable synthetic subject data. Replay the original lifecycle and inspect primary, derived and provider/log output according to the accepted policy. Feed that evidence into the data-rights check; unresolved policy or provider behavior stays a gate. Finish Patch Checking after supported acceptance, without turning technical tests into a legal-compliance claim.