> ## Documentation Index
> Fetch the complete documentation index at: https://learn.social.plus/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete User

> Understand why user deletion is not exposed through client SDK user operations.

Client SDKs do not expose a public method to delete a user. Treat user deletion as a privileged admin or backend workflow, not as a client-side SDK operation.

<Danger>
  Do not put user deletion credentials or privileged deletion flows in a client app.
</Danger>

## SDK Availability

| Surface            | Availability                                             |
| ------------------ | -------------------------------------------------------- |
| TypeScript SDK     | No public delete-user method                             |
| iOS SDK            | No public delete-user method                             |
| Android SDK        | No public delete-user method                             |
| Flutter SDK        | No public delete-user method                             |
| Admin/API workflow | Use the Console or a backend-controlled API integration. |

## Recommended Workflow

<Steps>
  <Step title="Authorize the request">
    Verify the requester is allowed to delete or deactivate the user account.
  </Step>

  <Step title="Run deletion from a trusted backend">
    Keep API credentials and audit logging outside the client app.
  </Step>

  <Step title="Refresh SDK-powered surfaces">
    Refresh user lists, member lists, profile views, and moderation tools after the backend operation completes.
  </Step>

  <Step title="Handle deleted-user state">
    SDK query results may expose deleted-user state such as `isDeleted`; make your UI resilient to missing names or avatars.
  </Step>
</Steps>

## Alternatives

| Approach                   | Use when                                                                            |
| -------------------------- | ----------------------------------------------------------------------------------- |
| Suspend or ban user        | You need to block access without permanently deleting account data.                 |
| Remove or moderate content | The issue is content-specific rather than account-specific.                         |
| Hide user locally          | You need a product-level visibility rule before a backend account decision is made. |

## Related topics

<CardGroup cols={2}>
  <Card title="Get User Information" href="./get-user-information" icon="user">
    Handle deleted-user state in profile and list views.
  </Card>

  <Card title="Roles & Permissions" href="../roles-permissions" icon="shield">
    Gate privileged admin and moderation actions.
  </Card>
</CardGroup>