Encrypted Assignment Dispatch
Feature Detail
Description
Enables coordinators to dispatch sensitive personal data - including names, addresses, and medical summaries - to peer mentors via an end-to-end encrypted channel. The system tracks delivery confirmation and read receipts per assignment and provides coordinators with a status overview of all open assignments. An automatic reminder is triggered after 10 days if no contact has been established with the assigned individual.
Sources & reasoning
Lines 94-95 explicitly describe Blindeforbundet's requirement for encrypted sensitive data dispatch with delivery and read receipts plus a 10-day reminder. The priority matrix (line 153) classifies this MUST for Blindeforbundet, Phase 2, which maps to target_release v1.0.
-
docs/source/likeperson.md · line 94-95- **Kryptert oppdragshåndtering:** Sende sensitive personopplysninger (navn, adresse, epikrise) til likepersoner med leveringsbekreftelse og lesebekreftelse. Statusoversikt over åpne oppdrag.
-
docs/source/likeperson.md · line 95- Automatisk påminnelse etter 10 dager dersom kontakt ikke er opprettet.
-
docs/source/likeperson.md · line 153| Kryptert oppdragshåndtering | - | - | ✓ | - | ✓ | MUST (Blindeforbundet) | 2 |
Analysis
For Blindeforbundet, encrypted assignment dispatch is mission-critical: coordinators regularly share sensitive patient data (names, addresses, medical records) with peer mentors, and doing so via unencrypted channels creates serious GDPR and data-security risks. The delivery and read-receipt mechanism gives coordinators certainty that sensitive information reached the right person, while the 10-day automatic reminder reduces the risk of follow-up falling through the cracks. This feature directly enables Blindeforbundet to adopt the platform while meeting their legal and operational obligations around sensitive personal data handling at scale without manual coordination overhead.
End-to-end encryption should use asymmetric cryptography (e.g. X25519/ChaCha20-Poly1305 via libsodium or the platform secure enclave), with the peer mentor's public key stored server-side and the private key protected by biometric or device authentication on-device. The server stores only ciphertext and cannot read the payload. Delivery confirmation requires a signed acknowledgement token; read receipts are logged when the decrypted payload is first rendered on-device. The 10-day reminder runs as a server-side background job. Flutter integration uses platform secure storage for key material and the assignment inbox screen for per-assignment status display.
Quality Assurance
No QA section has been generated for this feature yet.
Components (22)
Shared Components
These components are reused across multiple features
User Stories
No user stories have been generated for this feature yet.