> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/chord-oms/chord-oms-overview/users/remove-anonymize-customers-in-chordoms.md). # Remove/anonymize customers in ChordOMS ## Remove/anonymize customers in ChordOMS {% hint style="info" %} /This article is for Autonomy customers only. Performance and Data-only customers should refer to other articles or contact Chord regarding data management. {% endhint %} 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. {% hint style="danger" %} 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. {% endhint %} ## 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: 1. All store credits and gift cards are invalidated. Refunds will **not** be automatically provided - **all refunds must be completed *****before***** removing/anonymizing the user.** 2. All subscriptions (standard and pre-paid) are cancelled. 3. Personally identifiable attributes are deleted or anonymized (see the "Affected Data" table below on what data gets updated). 4. 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.** 5. ChordOMS instructs Segment to supress and delete the user from its internal database. More details can be found in the [Segment documentation](https://segment.com/docs/privacy/user-deletion-and-suppression/). ### 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. ![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-11ad066bcdb8607b0f9af0835655a1f87c0e7193%2Fremoveanonymize-customers-in-chordoms-1.png?alt=media) 2\. Review the confirmation message, input the customer's email address, and click **Confirm**. ![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-a4f1c6391d7dc9912b9d85672e67c98322a3a35a%2Fremoveanonymize-customers-in-chordoms-2.png?alt=media) 3\. You will see a message at the bottom of the screen stating that the customer removal job will execute in the background. ![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-a2524a09f208ff24744de3a16c0419f23e21850c%2Fremoveanonymize-customers-in-chordoms-3.png?alt=media) 4\. The user has been removed from Chord OMS and will no longer be visible on the Customers page. ![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-68d16ac7877dbf5e60266fb65cbb9ca4aebbcd39%2Fremoveanonymize-customers-in-chordoms-4.png?alt=media) 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. ![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-db3ef848d81c7d139a0e40b0a9f4471eef5b9272%2Fremoveanonymize-customers-in-chordoms-5.png?alt=media) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.chord.co/chord-oms/chord-oms-overview/users/remove-anonymize-customers-in-chordoms.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.