Confidentiality Declarations

Blindeforbundet requires formal confidentiality declarations from peer mentors who act as drivers or handle sensitive personal information about contacts, as part of their duty-of-care and GDPR-adjacent data protection obligations. Currently these declarations are collected on paper and stored manually, creating compliance risk if declarations are missing during an audit and adding administrative overhead for coordinators maintaining paper records alongside digital activity logs. Digitizing the declaration within the same app flow that captures the associated expense eliminates the risk of missed declarations, creates an immutable digital audit trail, and removes paper storage overhead entirely. The pattern is reusable by other organizations with similar duty-of-care requirements, and the conditional trigger means peer mentors who never perform driver roles are never shown an irrelevant screen.

ConfidentialityDeclarationScreen is triggered conditionally: when an expense item with a driver honorarium type is added, ConsentService checks whether a valid declaration exists for the current user and period. If not, the declaration screen is presented modally before submission proceeds, following the same acceptance state machine pattern established by the progressive-digital-consent feature in the encrypted-assignments area. Declarations are stored in the confidentiality_declarations table with user_id, organization_id, declaration_type, and accepted_at columns. The backend validates declaration existence before persisting driver-type expense items and returns an error if none is found. ConfidentialityRepository handles Drift persistence for offline declaration acceptance, allowing a peer mentor to accept the declaration while offline and sync the acceptance record before the expense submission is processed.