Privacy and records data
Separate website information from owner-provided records data; establish purposes, grounds and roles.
Final sources tied to business decisions
Grounds and scope
Owners establish purposes/grounds, sensitivity and retention. Confirm controller/processor roles, DPA, residency and support access per project. Consent is not a universal default ground.
Minimization and access
Process necessary fields only; redact dissemination copies; authorize OCR, search, logs and exports. API Explorer samples are synthetic; the tool accepts no record uploads.
Rights and conflicts
Access/correction/erasure requests are assessed against applicable grounds/duties. Holds/retention may constrain erasure; record reasons and authority. Proposed website/records policies require Mobile-ID confirmation.
Continue the workflow
Two journeys, one records lifecycle
Connect paper and born-digital records through persistent identifiers, policies and evidence.
Read detailsIntegration quickstart
Exercise ingest → job tracking → registration → verification with synthetic data.
Read detailsIntegrity, provenance and evidence
Each evidence type answers a different question; hashes, timestamps and approvals are not interchangeable.
Read detailsStart with a verifiable scope.
Agree record classes, quality criteria, permissions and evidence before scaling.
Plan assessment