Remove/anonymize customers in ChordOMS

/this article is for autonomy customers only performance and data only customers should refer to other articles or contact chord regarding data management chord oms contains many pieces of personal information about customers (i e the consumers who make purchases via chord merchants) customer data is owned by merchants and merchants have ultimate accountability over all customer data since chord stores the data, chord acts as a 'data custodian' with responsibility to safeguard customer's personal information occasionally, customers request that their data be removed from chord oms now, chordoms provides an easy method for handling removal requests from customers the customer anonymization process will remove or anonymize all of a customer's personally identifiable information in chord oms upon completion, the customer will be effectively removed from chord oms and the user cannot be personally identified by any data retained in chord oms removing/anonymizing customer data is an irreversible process once completed, it is impossible to recover the user record and related data if a removed/anonymized user wishes to transact with your store again, they must create a new customer account chord cannot provide support to restore customers that were removed why anonymize customers? to maintain data integrity, customers cannot be deleted in chord oms deleting a user would result in many records (e g orders, shipments, subscriptions) becoming 'orphaned' and no longer linked to a specific customer that data can no longer be used for modelling purposes in the data warehouse, reducing the accuracy and completeness of reports used to make business decisions therefore, when removing a customer from chord oms, some attributes and records will be deleted while others will be securely anonymized removal/anonymization process overview the following steps occur when a customer is removed/anonymized from chordoms all store credits and gift cards are invalidated refunds will not be automatically provided all refunds must be completed before removing/anonymizing the user all subscriptions (standard and pre paid) are cancelled personally identifiable attributes are deleted or anonymized (see the "affected data" table below on what data gets updated) a user deleted event is emitted to the cdp (e g segment) merchants can configure segment downstream destinations to handle this event as appropriate the workflow neither removes nor requests to remove data in downstream systems (beyond emitting the user deleted event) merchants are accountable for removing customer data from these systems chordoms instructs segment to supress and delete the user from its internal database more details can be found in the segment documentation affected data the table below indicates what fields are blanked, anonymized or retained when a customer is removed entity anonymized attributes blanked attributes retained attributes customer (user) email login api key stripe user id unconfirmed email name phone date of birth orders email phone addresses firstname city lastname state name address1 zipcode address2 phone alternative phone name credit cards name cc type month gateway customer profile id year gateway payment profile id last digits pre launch signups email name referrals email stock requests email prepaid subscription recipient email promotion codes email gift cards recipient email name purchaser name remove/anonymize a customer 1\ view the customer in chordoms and click the anonymize user data button 2\ review the confirmation message, input the customer's email address, and click confirm 3\ you will see a message at the bottom of the screen stating that the customer removal job will execute in the background 4\ the user has been removed from chord oms and will no longer be visible on the customers page however, their record remains in chord oms but with anonymized personal information viewing orders associated with the removed user show that the personal information was anonymized/removed