Export and deletion need direct entry points

What it is

A privacy rights action hub lets a person move from seeing data to export, deletion, and related requests in the same context. It distinguishes download copy, portable export, selected-data deletion, account deletion, and future-processing withdrawal because their scope and consequence differ. Centralization does not mean collapsing rights into one dangerous master action.

Why it happens

Inspection creates concrete needs: correcting an error, moving one class, or clearing old activity. When action is displaced to support, policy text, or another settings hierarchy, users must rediscover and redescribe the object. Stable identifiers shared by a displayed item and request workflow reduce scope ambiguity while connecting verification, backend execution, and status feedback.

Studying it

End-to-end tasks can begin with discovery of a record and ask participants to export its class, delete it, and delete the account, measuring path success, scope prediction, errors, verification burden, and backend outcome. Studies should detect confusion between export and deletion and between local and global scope. A clicked button is not completion evidence; generated files, storage, and subsequent processing need inspection.

Where it stops holding

High-risk deletion and bulk export may warrant reauthentication, delay, or confirmation, but friction should protect the account rather than retain data. Requests requiring human review or subject to exceptions still need intake and state explanation. Joint content and managed accounts may limit unilateral action; role and effect should be disclosed instead of hiding the route.

Applying it

• Place applicable actions beside each data class and account-level requests in one hub.
• Preview concrete objects, time range, shared effects, and reversibility before confirmation rather than asking only to continue.
• Show verification, processing, partial completion, exception, and failure states with a trackable case identifier.
• Exercise export and deletion from discovery to backend result across roles and data combinations, reconciling files, stores, and jobs rather than success messages.

Related

• Same group: O2.04.1 Users need to see the data already collected · O2.04.3 Discoverability determines whether a dashboard has practical value
• Adjacent: O1.07 Right to erasure and data deletion · O1.12 Data portability and export
• Search terms: privacy rights hub · self-service deletion · data export entry point