DPDPA FLW: Consent enforcement, preference centre and withdrawal in the FLW app

XMLWordPrintable

    • Type: Epic
    • Resolution: Unresolved
    • Priority: High
    • 3.0
    • Affects Version/s: None
    • DPDPA FLW Enforcement
    • FLW Mobile App
    • All

      Objective: The FLW app checks consent before it shows or saves beneficiary data. FLW users (ASHA/ANM/CHO) can view, change and withdraw a beneficiary's consent. Every view and change of a beneficiary record is logged.

      Scope: Preference centre (view, change one purpose, withdraw one or all, history); consent check on every FLW screen and API that reads or writes beneficiary data, including reminders and notifications; data-access log.

      Priority rationale: Without enforcement, captured consent has no effect on data access.

      Source: DPDPA Compliance Proposal v14, sections 3.1, 4, 5, 6, 7. Mirrors AMM-2501 for the FLW app.

      Dependencies: AMM-2499, AMM-2508 (consent check), AMM-2509 (withdraw), AMM-2529, AMM-2532.

      Out of scope: Doctor time-limited and emergency (break-glass) access (AMM-2511 is not in 3.14).

      Open question: [TBD/CLARIFICATION REQUIRED] Rule D-02: can a FLW user treat or register a beneficiary while consent is pending?

              Assignee:
              Saurav Mishra
              Reporter:
              Shivani Garg
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: