Users need to see the data already collected

What it is

A personal data dashboard presents data held about a person through intelligible categories, sources, purposes, and time so they can inspect what the system knows. It is more than an account profile: behavior, device information, location history, uploads, and account-linked archives may all be in scope. Values need provenance and processing state rather than a raw dump of internal fields.

Why it happens

Backend data are distributed across operational stores, logs, warehouses, and processors, while ordinary screens expose only what a current task needs. Without a unified view, people cannot find errors, unexpected collection, or expired data, and teams can mistake invisibility for absence. A readable catalog tied to lineage reduces information asymmetry and gives correction, restriction, and inquiry a concrete object.

Studying it

Using accounts seeded with known records, studies can ask participants to locate a data class, identify its source, and find a planted error, measuring coverage understanding, retrieval, misconception, and confidence. Backend audits should reconcile dashboard entries bidirectionally with catalogs, queries, and processor copies. Entry count is not completeness: broad categories can conceal many fields, and untriggered conditional data may evade testing.

Where it stops holding

A dashboard need not disclose security secrets, fraud rules, or another person's data verbatim, but should name restricted classes and reasons. Visibility of aggregates and inferences depends on applicable rights and promises, not whether the user typed them. Streaming raw logs creates overload and new exposure, so decision-relevant layering and reauthentication may be necessary.

Applying it

• Generate categories from the data inventory rather than the existing settings page, covering supplied, observed, derived, shared, and archived states.
• Show sample value or summary, source, purpose, update time, retention state, and available action for each item.
• Name restricted content, basis, and alternative access route rather than representing it as absence.
• Reconcile accounts containing current, erroneous, stale, and processor-held records against the backend; revise classification when people cannot locate data or diagnose the error.

Related

• Same group: O2.04.2 Export and deletion need direct entry points · O2.04.3 Discoverability determines whether a dashboard has practical value
• Adjacent: O1.12 Data portability and export · O2.10 Privacy dashboards and data visibility
• Search terms: personal data dashboard · data inventory view · privacy self-service