Collab | Un-Subscription & UIN Data Deletion via Collab Landing Page

[Pragya279]

1. Ticket Contents: Description

This feature enables community users to unsubscribe from MOSIP Collab emails directly from the Collab Landing Page, providing an alternative and easily accessible mechanism outside of email links.

Currently, users can only unsubscribe via links in emails (or not at all), which creates friction and may result in unwanted communications. This feature introduces a visible unsubscribe option on the landing page, allowing users to opt out at any time.

The solution ensures user control, improved experience, and compliance with privacy regulations, while also triggering secure deletion of associated UIN and personal data upon successful unsubscription.

2. Goals & Mid-Point Milestone

Overall Goals

• Add Unsubscribe option on Collab Landing Page
• Enable redirect to unsubscribe form (Google Form or equivalent)
• Capture user input (email, reason, consent)
• Validate unsubscribe requests against backend systems
• Implement data deletion workflow (UIN + associated data)
• Handle already unsubscribed users gracefully
• Prevent future communications to unsubscribed users
• Maintain audit logs and analytics for unsubscribe actions
• Ensure compliance with data privacy and consent requirements

Mid-Point Milestone (1.5 Months)

• Add Unsubscribe CTA on Collab Landing Page
• Redirect flow to unsubscribe form
• Form with required fields (email, reason, consent)
• Backend API to process unsubscribe requests
• Validation for already unsubscribed users
• Success and error messaging
• Basic tracking of unsubscribe requests

3. Expected Outcome

The final implementation will provide a simple, accessible, and compliant unsubscribe experience via the landing page:

• Users visiting the Collab Landing Page can easily find and click on the “Unsubscribe” option

• Clicking the option redirects them to an unsubscribe form where they:

  • Enter their email ID
  • Select a reason for unsubscribing
  • Provide optional feedback
  • Confirm consent

• Upon submission:

  • The system validates whether the email is already unsubscribed

  • If not:

    • The system deletes the associated UIN and all linked personal data
    • Marks the email as unsubscribed
    • Displays a success message

  • If already unsubscribed:

    • Displays a message indicating no further action is required

• The system ensures that no further emails are sent to unsubscribed users

• All unsubscribe actions are logged for audit and analytics purposes

This feature improves discoverability, user autonomy, and trust, while ensuring regulatory compliance.

4. Acceptance Criteria

Landing Page Integration

• AC1: Collab Landing Page displays a visible “Unsubscribe” option
• AC2: Clicking “Unsubscribe” redirects user to the unsubscribe form

Form Behavior

• AC3: Form captures:

  • Email ID (mandatory)
  • Reason for unsubscribing (mandatory dropdown)
  • Additional comments (optional)
  • Consent checkbox (mandatory)

Submission & Validation

• AC4: On submission, system checks if the email is already unsubscribed

• AC5: If already unsubscribed, user sees:

  • “You are already unsubscribed from MOSIP emails. No further action is required.”

Unsubscribe Processing

• AC6: If not unsubscribed:

  • System deletes associated UIN(s) and all linked personal data

• AC7: System handles cases where one email is linked to multiple UINs as per defined policy

User Feedback

• AC8: User sees confirmation message:

  • “You have successfully unsubscribed. Your associated UIN and related data have been deleted.”

Post-Unsubscribe Behavior

• AC9: No further emails are sent to unsubscribed email IDs
• AC10: User must re-register and obtain a new UIN to receive emails again

Tracking & Analytics

• AC11: All unsubscribe requests are logged in backend
• AC12: Data (email, reason, timestamp) is available for reporting

5. Implementation Details

Frontend (Collab Landing Page)

• Add Unsubscribe CTA/button on landing page

• Redirect to:

  • Google Form (initial approach), or
  • Custom unsubscribe page (future enhancement)

Form

• Fields:

  • Email ID
  • Reason dropdown
  • Free-text comments
  • Consent checkbox

• Static note about UIN deletion

Backend

• Unsubscribe API/service:

  • Validate email status
  • Process unsubscribe request
  • Trigger deletion workflow

• Maintain unsubscribe registry:

  • Email
  • Reason
  • Timestamp

Data Deletion Workflow

• Identify all UINs linked to email

• Delete:

  • UIN(s)
  • Associated demographic/personal data

• Ensure deletion across all relevant services/databases

Email Suppression

• Maintain suppression list of unsubscribed emails
• Ensure email service excludes these addresses from campaigns

Alternate Flow Handling

• Approach 1 (Preferred):

  • Always show form → validate on submission

• Approach 2 (Optional):

  • Pre-check unsubscribe status → bypass form

Security & Privacy

• Ensure consent is explicitly captured
• Secure handling of email input
• Compliance with data protection regulations (right to opt-out, data deletion)

Analytics & Reporting

• Store unsubscribe data for:

  • Trend analysis
  • Reason categorization

• Build dashboards for monitoring unsubscribe rates

Performance & Reliability

• Lightweight landing page integration
• Asynchronous deletion processing
• Retry mechanisms for cleanup failures

Product Name

MOSIP - Resident Portal

Organisation Name

C4GT

Organizational Mentor

Feature Support : @Pragya279
Tech Support: @MadhuMosip

Complexity

Medium

Category

Frontend + Backend

[Soniyakmt]

I would like to work on this feature.
Before starting implementation, I will analyze the repository structure and propose a detailed technical plan covering frontend integration, backend validation, data deletion workflow, and audit logging.
Kindly confirm the preferred approach (Approach 1 or 2) and whether a custom unsubscribe page is expected instead of only Google Form redirection.