> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/profiles/how-to-deactivate-a-customer-account.md). # Delete or Deactivate ### Overview A few reasons why an Admin might want to delete or deactivate a Profile are: * Customer is seen as a bad actor * Customer behaves in problematic ways * Customer is continually exhibiting fraudulent behavior even after a Club staff member speaks with them When these things happen, staff can go to the Customer’s Profile and deactivate or delete it. #### Deactivating a Profile * Stop that Customer from being able to sign-in to the App * Stop the Customer from being able to use their email or phone number on another Profile * Retain their information for future reference #### Deleting a Profile * Remove that Customer's information from the system, entirely * Any reference to purchases they made will show up as "" during [revenue reconciliation](https://podplay.gitbook.io/docs/owners-playbook/accounting-and-stripe/revenue-reconciliation) [Customers can also delete their information from the App](https://podplay.gitbook.io/docs/owners-playbook/data-and-security/data-retention-policies#customers-deleting-data), if they want. ### Let's do it... To deactivate or delete a Profile: * Navigate to the Customer’s Profile * Look for the Account Status section, near the top of the Overview tab of the side panel * Flick the `Status` toggle (deactivate) * Click the `Delete account` button (delete) * Confirm the pop-up window
--- # 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.podplay.app/profiles/how-to-deactivate-a-customer-account.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.