Customer Anonymization

Overview

This article describes the workflow for handling customer-initiated account deletion flows.

Cleeng offers two ways depending on your integrations:

For backend integrations using only publisher token
For MediaStore SDK integrations - using customer token for fetching entitlements and then publisher token for account

Follow the steps below if you have backend integration:

In order to delete the account (anonymize a customer) we first need to make sure the customer doesn’t have any active subscriptions. We call the List entitlements endpoint to check.
If there are no active entitlements, the account can be deleted - see point 3.
To terminate entitlements, call the updateCustomerSubscription endpoint to set the status to terminated. (The customer can be asked to confirm this.)
When entitlements are successfully terminated, or if there are no active entitlements returned at all, call the Delete customer endpoint to delete (anonymize) customer.

Follow the steps below if you have MediaStore SDK integration:

A customer initiates the account deletion action in an application, for example via a UI-provided button. (Please note that MediaStore SDK MyAccount feature does not offer this functionality).
In order to delete the account (anonymize a customer) we first need to make sure the customer doesn’t have any active subscriptions. We call the Fetch customer's offers endpoint to check it.
If there are active entitlements, the customer should be informed that these will be terminated and asked for confirmation. For termination - see point 4 below.
If there are no active entitlements, the account can be deleted - see point 5.
To terminate entitlements, call the updateCustomerSubscription endpoint to set the status to terminated.
When entitlements are successfully terminated, or if there are no active entitlements returned at all, call the Delete customer endpoint to delete (anonymize) customer.