Confidentiality Declarations
Feature Detail
Description
Enables peer mentors acting as drivers to complete digital confidentiality declarations (taushetseerklæringer) within the mobile app before submitting chauffeur-related expenses or activities. Required by Blindeforbundet for activities where drivers are exposed to sensitive contact information, declarations are versioned, timestamped, and stored against the user profile. Submission of chauffeur-type expenses is blocked until a valid declaration is on record for the current declaration version, making compliance automatic. Coordinators and org admins can view declaration status per peer mentor in the Admin Web Portal, providing a complete and traceable compliance audit trail.
Sources & reasoning
Line 70 explicitly names taushetseerklæringer (confidentiality declarations) for drivers as a Blindeforbundet expense-area requirement. The expense-reimbursement area is Phase 2 (lines 148, 343), placing this at v1.0. This is a legal compliance requirement, not a preference, which drives the must-enforce-before-submit design.
-
docs/source/likeperson.md · line 70Sjåfærhonorarer og taushetseerklæringer for sjåfører (Blindeforbundet).
Analysis
Blindeforbundet's chauffeur activities expose drivers to sensitive personal information about contacts, creating a legal obligation to obtain and retain signed confidentiality declarations. Without a digital solution, declarations are collected on paper, creating storage and audit risks and making compliance verification burdensome for coordinators who must manually track which peer mentors hold current declarations. Integrating declarations into the expense registration flow ensures that no chauffeur activity can be completed without a valid declaration on record, making compliance automatic rather than dependent on manual coordinator checks. The digital audit trail supports regulatory accountability and simplifies internal review, reducing organizational risk in Blindeforbundet's operations and providing evidence in the event of a compliance inquiry.
Implement as a modal or dedicated screen triggered when a chauffeur expense type is selected. Declaration text is fetched from the backend as an org-scoped, versioned document updatable by org admins. User acceptance is recorded in the confidentiality_declarations table with user ID, timestamp, and declaration version hash. The expense submission flow checks for a valid declaration against the current version before allowing chauffeur types to proceed. If no record exists or the stored version is outdated, the user is prompted to re-sign. The Riverpod provider manages declaration state; the record is included in the Drift offline sync queue so enforcement applies without connectivity. WCAG 2.2 AA compliance is required for all declaration text rendering and acceptance controls.
Components (7)
Shared Components
These components are reused across multiple features
User Stories
No user stories have been generated for this feature yet.