FAQs
-
Can we raise bulk PII data deletion requests?
For bulk PII deletion, use Connect+. See PII data flow.
-
Is the PII deletion request approved by default?
This depends on the query parameter. PII deletions need to be approved.
-
Are custom fields and extended fields part of PII data?
No. But, you can mark the desired custom fields and extended fields as PII data.
-
Will PII details in the Auth engine be deleted for the users who raised the request?
Yes. After the PII deletion waiting period lapses.
-
Will event data (behavioural events, transaction events, etc.)be deleted?
No. Data attributed to the user id is not deleted as the user id is not categorized as PII data.
-
What happens if the waiting period is set as 0 days?
If the waiting period is set to 0 days, the system deletes the data on the same day.
-
My brand's transaction custom fields/extended fields also have PII data. Can those be marked for deletion?
Yes. You can mark that data as PII data. See Custom field and extended field PII data.
-
Can I view a deleted customer's events on Member Care?
Yes.
-
Will the profile be visible if I go to the profile using user_id in the Member Care URL?
No.
-
Are payment mode attributes deleted by default?
No. But you can configure payment attributes as PII data. See payment attributes.
-
My brand's payment mode attributes have sensitive PII data. Can I delete that?
You can configure payment attributes as PII data. See payment attributes.
-
I want to delete event data (transactions, behavioural events and so on) of customers. Is this possible?
No.
-
Will communications sent to a customer be deleted?
No.
-
What happens to active coupons that are not redeemed?
You cannot redeem the active coupons associated with the deleted customer ID.
-
Will OTP messages get sent to customers?
After the PII deletion, the customer will not get any message.
-
How can a customer track the status of a deletion request?
Brands can use the GET APIs and the event notifications to update the status of the customers.
-
Is there a UI to view all deletion requests raised in an org?
Yes.
-
How can a CSR raise a deletion request?
CSR can raise deletion requests through member care.
-
Can any CSR raise a deletion request?
This depends on access rights. If you have access, you can raise deletion requests on behalf of a customer.
-
How is PII deletion handled for connected orgs?
In connected orgs, PII deletion is based on the PII deletion policy configuration.
-
Does the configured card status "DELETED" override the card's previous state?
Yes. The PII deletion process updates the status for all cards associated with the customer, regardless of their previous state (e.g., ACTIVE, ISSUED, SUSPENDED, or EXPIRED).
-
Does NOT_ISSUED vs. DELETED have any operational difference beyond the status label?
If you want to reuse the cards after PII deletion, you can have the cards set to NOT_ISSUED. If you don't want to reuse the cards, you can configure them as DELETED. Only cards with the NOT_ISSUED status can be linked to a new customer.
-
Does changing the configuration later affect past PII deletions?
No, the card status will take the label that was configured at the time of the PII deletion. The configuration can be changed only for the future deletions.
-
Can the card status be updated manually after PII deletion has occurred?
No, you cannot update the
DELETEDlabel. You can, however, update the status of aNOT_ISSUEDcard. Once you link aNOT_ISSUEDcard to a customer, its status will change to ACTIVE, and you can then update its status as per requirement. -
Does this
CONF_PII_DELETION_CARD_UNLINK_STATEconfig affect physical cards?Yes, this feature affects all cards, both physical and digital.
Updated about 5 hours ago
