This functionality enables organizations to adhere to worldwide data privacy laws by anonymizing personally identifiable information (PII) for any customer profile when requested. Through a user-friendly interface, brands can sever all identifiable links between profiles, responses, and transactions, while maintaining the integrity of survey responses.

Anonymization involves replacing sensitive data fields such as name, email, phone number, and profile ID with terms like "Anonymized" or "Removed," guaranteeing that no response can be traced back to a specific person. Moreover, the system automatically adds anonymized profiles to a blocklist to avoid future communication, thus upholding compliance without affecting reporting or analytics.

Business Use Cases

• Data Privacy Compliance: With an anonymization feature, administrators can instantly anonymize a customer’s profile in a single step, ensuring no personal data remains identifiable. This allows organizations to meet regulatory requirements seamlessly while maintaining confidence in their compliance processes and preserving the integrity of non‑personal data for reporting and insights.

• Preserve Data Integrity: With an on‑demand anonymization capability, identifiers can be stripped from customer profiles while preserving the underlying response data. This ensures that trends, benchmarks, and insights remain intact for decision‑making, while the organization seamlessly meets privacy requirements without compromising the quality of its analytics.

With Compliance, the Anonymization feature enables organizations to honor “right to be forgotten” requests by anonymizing all personal identifiers while keeping survey responses intact, ensuring full adherence to privacy regulations; with Analytics Continuity, survey administrators can anonymize sensitive profile data without losing corresponding responses, allowing teams to track trends and insights while safeguarding customer privacy; and with Governance, program managers benefit from automatic blocklisting during anonymization, ensuring anonymized profiles are never targeted in future surveys, reducing compliance risks and strengthening customer trust.

Prerequisites

You would need access to Anonymize Profile Data at App Level under Platform Permissions.

Setting Up On Demand Anonymization

1. Go to Customer Feedback Management and go to Global Settings.

2. Go to Anonymize Profile Data under Data & Privacy.

   

3. Go to Anonymize Profile Data and fill in the details:

   

   1. Request ID: A unique identifier used to internally reference the anonymization request. This can later be used to track or validate the status of the request.

   2. Description: A short description or reason for the request. Adding context here helps with future audits and internal tracking.

   3. Select Profile: The profile to be anonymized. Users can search and select the profile using an email address, phone number, or profile ID.

4. Enter Email ID or Profile ID to search the profile.

5. After completing the anonymization request form, click Confirm and click Anonymize Data, a message will notify that anonymization is irreversible.

   

6. Blocklisting is triggered automatically with anonymization.

Setting up Anonymization condition for Fields (Specific)

1. Submit a list of PII fields (e.g., Name, Email, Phone, User ID, SNID, required custom fields) to Sprinklr Support for backend configuration.

2. These fields are marked for anonymization by Sprinklr support.

System Behavior

1. PII fields are replaced with “Anonymized”.

2. Associations between Profile ↔ Response ↔ Transaction are broken.

3. Blocklisted entries are preserved in suppression lists & will also be reflected in Blocklist Record Manager

4. Reports, dashboards, and exports reflect anonymized values as “Removed.”

Record Manager

The record manager captures the following columns:

Manage Anonymize Profile Data

1. Search: Search is supported for Email Address, Phone Number & Profile ID.

2. Manage Columns: You can manage the columns using this option

3. Refresh: You can refresh the data.

4. Filters: You can filter the data in two ways:

   1. Channel: Filter by channel.

   2. Triggered By: Refine your search by choosing the user that started the trigger event.

Best Practices

• Always add a Request Identifier for tracking anonymization requests.

• Ensure only trained admins have Anonymization Permission.

FAQs