The dashboard brings together the compliance status of MyZapp, area by area, for the data protection officer (GDPR articles 38 and 39). It only shows figures, never a person's identity.
The screen is in Data protection › Dashboard. The whole module can read it; the compliance file is reserved for data protection officers (and administrators).
What the dashboard shows
Each card is an area. The first figure counts the items; the orange figure, when it appears, counts those that need action. Clicking the line opens the screen where you handle them.
| Area | What is counted | What needs action |
|---|---|---|
| Processing register | Active activities; proposals to validate | Review overdue; proposal to validate |
| Data subject requests | Open cases; external system tasks | Due within 7 days or overdue |
| Data breaches | Open breaches | 72-hour deadline near or past, not notified |
| Impact assessments | Assessments in progress; validated assessments | Authority consultation in progress; review due |
| Processors | Active processors | Review overdue |
| Consents | Choices in the last 30 days | Withdrawals |
| Retention | Categories applied; active legal holds | Purge failures in the last 7 days |
| Security and governance | Security measures, processing activities without a by-design review, open actions of the plan | Planned measures or those due for review, activities to review, overdue actions |
The compliance file
The GDPR requires you to be able to demonstrate compliance (article 5.2). The compliance file prepares an audit in one click: choose the legal entity, then Download the file. You get a dated ZIP file that contains:
- the processing register (controller and processor), as CSV and PDF;
- each impact assessment, as PDF;
- the breach register (CSV) and the PDF record of each breach;
- the processors and their transfers outside the Union (CSV);
- the retention policies and the purge log of the last two years (CSV);
- the summary of data subject requests: a count per right and per status, with no identity;
- a manifest (
manifest.json): date, entity, list of documents with the SHA-256 fingerprint of each.
If a document could not be produced (for example when PDF rendering is not available), the manifest lists it under notProduced: the file never hides a gap.
Good to know
- The file can also be downloaded through the API:
GET /api/v1/privacy/dashboard/dossier?entity=<id>&lang=en. - The dashboard figures are computed when the screen opens.