MOSIP-42813: Collab | Un-Subscription & UIN Data Deletion via email

[exalate-issue-sync]

Problem Statement: Community users currently lack a simple way to unsubscribe from Collab emails, leading to unwanted communications and a suboptimal user experience.

Proposed Solution: Introducing an unsubscribe mechanism will empower users with control over their communication preferences, improve compliance with privacy regulations, and build greater trust in the platform by ensuring that only relevant and opted-in communications are delivered.

Title
As a Community User,
I want the ability to unsubscribe from Collab emails through a simple process,
So that I can stop receiving communications that I no longer find relevant.

Basic Flow:

1. Every email contains an Unsubscribe link at the bottom.

2. Clicking the link redirects the user to a https://forms.gle/EDFs6gi7pdjmAgZ36 to capture relevant details for unsubscribing.

3. The form includes the following fields:

Header: MOSIP Collab – Email Un-Subscription Form

Description: We are sorry to see you go. Please complete the form below to unsubscribe from all future emails from the MOSIP Collab environment.

E-Mail* (enter the email you wish to unsubscribe)

Form Fields:

Reason for Unsubscribing* (dropdown):

###* I no longer wish to receive these emails
###* The content is not relevant to me
###* I receive emails too frequently
###* I didn’t sign up for these emails
###* Others

Additional Comments (optional)

“I agree to unsubscribe”* (checkbox)

Submit (button)

A clear note is displayed on the form: Unsubscribing will also delete your associated UIN. Once unsubscribed, you will not be able to use this UIN in the future.

1. On click of the “Submit” button, the user sees a success message: “You have successfully unsubscribed. Your associated UIN and related data have been deleted.”

Alternate Flow: TBD based on technical feasibility
Approach 1: Redirects to Form but Submission Detects Already Unsubscribed

1. User clicks on the Unsubscribe link in the email.

2. The system navigates the user to the Unsubscribe Form. (as detailed above)

3. The user enters required details and clicks Submit.

4. The system checks the database and identifies that the email address is already unsubscribed.

5. The system displays a clear message:
   “You are already unsubscribed from MOSIP emails. No further action is required.”

Approach 2: Directly Identifies Already Unsubscribed

1. User clicks on the Unsubscribe link in the email.

2. The system immediately checks the status of the email address in the database.

3. If the system finds that the email is already unsubscribed, it does not show the form.

4. The user is redirected to a page that clearly states:
   “You are already unsubscribed from MOSIP emails. No further action is required.”

Acceptance Criteria:

1. Every email contains an Unsubscribe link at the bottom (as per the UX design)

2. On submitting the form,

The user sees a confirmation message: “You have successfully unsubscribed. Your associated UIN and related data have been deleted.”

The system triggers a cleanup process: The email ID is identified in the database, and the associated UIN along with any linked personal data is permanently removed from all relevant databases and tables. (What if the email ID is associated to multiple UINs?)

1. No further emails are sent to the unsubscribed address unless the user registers again and a new UIN is issued.

2. All unsubscribe submissions should be tracked in the backend for reporting and analytics.

Business Rules:

• NA

UX Design: TBA

🔗 Linked Issues

ISSUE

• MOSIP-42892
  Status: New Dev