> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/how-the-apps-work/screens/account/profile-deleted.md).

# Snapfix profile deleted

{% hint style="info" %}
Draft, written by an agent and not yet checked by a person ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). Platforms: web. [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/screens/account/profile-deleted.md).
{% endhint %}

The page a person sees once, right after deleting their own profile on the web. It confirms the deletion and says they cannot sign in again.

* **Where:** web `/delete-user-confirmation`. "Delete My Profile" in [My profile](https://docs.snapfix.com/how-the-apps-work/screens/account/profile.md) sets a session flag after [`DELETE /v1/app/user`](https://docs.snapfix.com/engineering-reference/api/account.md#delete-v1appuser) succeeds, then opens this page.
* **Who:** only the person who has just deleted their profile. The route guard `authDeleteGuard` sends anyone without the session flag to `/auth/sign-in`. The page clears the flag when it opens, so a reload or a second visit also goes to sign-in (web\_app\_v2 @ 0989b8e685, `src/app/pages/delete-user-confirmation/delete-user-confirmation.component.ts:16-18`).
* **Feature:** [Profile and settings](https://docs.snapfix.com/product/features/account/profile.md)

## Layout

The same two-column layout as [Sign in](https://docs.snapfix.com/how-the-apps-work/screens/account/sign-in.md): the card on one side, the usual random photo with the Snapfix logo on the other. The card, top to bottom:

1. A warning icon and "Snapfix profile deleted".
2. "We have processed your request to delete your Snapfix profile." and "You are now logged out of Snapfix and your profile details have been removed."
3. "Please note:" in bold, then "You will not be able to log into Snapfix again." and "A deleted profile can not be reinstated."
4. A full-width button, "Close Window".

## Inputs

None.

## Actions

| Action         | Who                    | What happens                                                         | API |
| -------------- | ---------------------- | -------------------------------------------------------------------- | --- |
| "Close Window" | The person on the page | Opens `/auth/sign-in` in the same tab. It does not close the window. | -   |

## States

* **Loading:** none; the page is static.
* **Empty:** not applicable.
* **Error:** none of its own.
* **No permission:** without the session flag the guard opens sign-in before the page shows.
* **Offline:** the page makes no request.

## Platform differences

Web only. The apps delete the profile from [Settings](https://docs.snapfix.com/how-the-apps-work/screens/account/app-settings.md) and show their own result: iOS a confirmation screen (`DeleteProfileConfirmationVC`) whose one button signs the person out, Android a dialog (`DeletedSnapfixProfileDialog`) whose button closes the app.

The page says the profile details "have been removed". The server keeps the deleted row: it prefixes the first name with "DEL -", folds the email and phone number into a marked username string, empties the separate phone fields, and soft-deletes the row (api\_php\_live\_v2 @ ef3c4319f6, `UserController.php:201-212`). Whether that matches the promise is open \[[ASK-25](https://github.com/snapfix/docs/blob/main/ASK.md#ask-25-what-should-deleting-a-profile-remove)].


---

# 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.snapfix.com/how-the-apps-work/screens/account/profile-deleted.md?ask=<question>&goal=<user_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.
