Objective: FLW users work in the field, often without internet. Consent must work fully offline in the FLW app and sync to the central server later.
Scope: Download of latest notices (all languages), purposes and consent status of beneficiaries in the user's area; take, check and withdraw consent offline; upload of consents, withdrawals, audit entries and access logs when online; proof files uploaded separately; duplicate handling and "withdrawal always wins" rule.
Source: DPDPA Compliance Proposal v14, sections 3.2.1, 3.2.2, 8. Mirrors AMM-2502 for the FLW app.
Dependencies: AMM-2499, AMM-2510 (proof upload), AMM-2533 (sync APIs).
Open questions: [TBD/CLARIFICATION REQUIRED]
- AMM-2533 is designed for the STOP TB camp laptop. How does the FLW app sync consent: directly to central, or through another path?
- How is the device key issued and revoked for the FLW app?
- Decision D-06: maximum age of downloaded data.