IBAN Storage Policy Decision¶
Date: 2026-11-08 (replaces the decision of 2026-06-25) Status: Accepted. Roadmap item: EP8-T1.
Decision¶
End-to-end encryption was removed from MamNajem on 2026-11-05 to 2026-11-08 (see
plans/e2ee-removal-inventory.md, decision 14). Bank account details are now plain
values in the backend:
| Area | Decision |
|---|---|
| Owner bank account profile | displayName, iban and accountHolderName are plain columns. The display name and the IBAN are required (database check chk_bank_accounts_content_present). |
| Tenant rent payment instructions | Accepted lease participants see the full IBAN and holder name on payment schedules and payment requests, because they need them to pay rent from their own bank app. |
| Backend controls | Authorization, least-privilege access, TLS in transit, production database and storage encryption at rest with the application KMS key, audit logging and telemetry scrubbing. |
| Admin and support surfaces | No full IBAN unless a specific support workflow is approved later. Show no IBAN, the last 4 digits, or a masked value. |
| Data export | The owner's own export contains the plain bank account fields. |
The only field the backend encrypts itself is the tenant document number
(lease_tenants.doc_nr, stored through SensitiveText with the application key).
Why¶
Tenants must read the landlord's IBAN to pay rent, so a backend-unreadable IBAN breaks the core flow. Encryption at rest already protects the stored value, and the removal of client-side encryption made a second layer for bank details unnecessary.
History¶
The 2026-06-25 decision kept the bank details inside a client-encrypted
encryptedDetails envelope and exported only that envelope. It no longer
applies: the envelope columns, their API fields and the app code were deleted.