Settings

Organisation profile, people, modules and the integrations that feed them.

Organisation Users & roles Modules Integrations Branding Notification rules Demo data

This build runs entirely on mock data

Nothing leaves your browser. Every record you see is generated from a deterministic seed, so the dataset is identical on every machine and every build. Actions you take — withdrawing consent, closing a gap, filing a notification — are persisted to local storage and survive a refresh. Phase 2 replaces this layer with a real API and database behind the same interface.

Current dataset

Live counts from the store, including anything you have changed this session.

Consent artefacts
140
Rights requests
96
Data elements
230
Incidents
10
Gaps
23
Risks
18
Audit entries
120

Reset

Restores every record to its seeded state. Because the seed generator is deterministic, a reset is exact rather than approximate — the same demo, every time.

Reset demo records

Consents, requests, incidents, gaps, detections and the audit trail. Keeps your role, theme and sidebar state.

Full reset

Records plus session: role, SDF flag, enabled modules, branding and sidebar state.

How the demo data is built

DeterministicA small linear congruential generator with a fixed seed. No use of the platform random number generator, so the dataset is byte-identical across builds and machines.

CoherentOne world, shared across modules. The same Data Principals appear in the discovery inventory, hold consents, file requests in the portal and appear in the breach impact assessment. Clicking sideways between modules keeps making sense.

Live where it mattersThe statutory clocks — one-hour acknowledgement, four-hour preliminary assessment, the 72-hour Board deadline — run against the real wall clock, not the frozen demo date.