ElanoryaJewelry AI · Account
Account deletion ends on the welcome screen, without a separate sign-out
The flow starts from Profile and passes a confirmation that states the action cannot be undone. The server may stop it once to ask you to prove who you are, which is its own state rather than a rejected password. When it succeeds you are signed out on your own and land back on the welcome screen.
Where the flow starts, and what stands in the middle of it
Deletion is reached from the Profile screen and runs on a screen of its own. Between your request and the call to the server there is a confirmation dialog, and its text states that the action cannot be undone.
After you accept it the sequence continues on its own, unless the server interrupts to ask you to prove who you are. What follows is the server's answer and the app reacting to it.
Being asked to prove who you are is not a rejected password
The distinction is written into the screen deliberately, because the two look similar and mean different things.
- The message is specific to re-authentication.
- The screen does not report an incorrect email address or password. It reports that re-authentication is required, which is a request rather than a verdict on what you typed.
- The request comes from the server, at its own moment.
- It can interrupt a deletion that was proceeding normally, and the message that carries it is not a report about what you typed.
- Some accounts have no password to answer it with.
- Where the account has no password field, the screen offers re-authentication through a provider instead. Why an account may have no password in the first place is explained on the page about passwords and lockouts, and is not re-derived here.
- The buttons that carry this step sit on the delete screen.
- They are part of that screen rather than of the account layer described here, and this page describes them only as offered, without going into how they work.
Why one seller sees a provider button and another does not
The provider buttons are conditional. An Apple or Google re-authentication button is drawn only where that provider is actually linked to the account, and the Apple button additionally only on iOS.
The practical reading: their absence is a statement about your account and your platform, not a fault in the screen. An account that never used Google will not be offered a Google button to prove itself with.
What the screen asks for depends on how you sign in
Four situations at the same point in the flow.
| Situation | Choose | Why |
|---|---|---|
| The account has a password. | Answer the re-authentication request in the password field. | Where a password exists, the field is how the request is answered. |
| The account was opened with a provider and has no password field. | Use the provider button that the screen shows. | Where there is no password, re-authentication is offered through the provider that is linked to the account. |
| You expected a provider button and it is not there. | Check whether that provider is linked to this account, and on Apple, whether you are on iOS. | Each button is drawn only under those conditions and is not offered unconditionally. |
| The deletion has succeeded and you are on the welcome screen. | Do nothing further on the device. | The sign-out is part of the flow; there is no separate step left to perform. |
Worth settling before you begin
Each item follows from behaviour described above.
- Move any generated images you want to keep off this phone first: the flow attempts to clear the cached ones as it finishes, and the attempt is not reported to you.
- Expect a possible re-authentication request, and know it is not a report that your details were wrong.
- Check, on a provider account, that the button you will need is the one the screen offers.
- Read the confirmation text as final rather than provisional; accepting it is what releases the call.
- Expect to end on the welcome screen without signing out yourself.
Where this flow catches sellers out
Three misreadings, and what each one costs.
The re-authentication prompt is taken as proof the deletion failed.
Answer the prompt and read the result afterwards. The message is worded to be distinct from a credentials error for exactly this reason.
A provider account is abandoned because there is no password to type.
Look for the provider button; on an account with no password field, that is what the screen offers in its place.
The seller waits on the welcome screen for a further confirmation of the deletion.
Arriving there is the client-side end of the flow. What the server does afterwards is not something this surface reports.
The parts of deletion this page cannot describe
- What the server deletes, what it keeps, and how long any of it takes. The client proves the call and the local behaviour that follows it, and nothing beyond that.
- Any consequence for purchases, plans or balances. This description does not cover them and this page makes no claim about them.
- The mechanism of the local cleanup, which belongs to the page on signing out and what it clears; here it appears only as one attempted step at the end.
- Why an account may have no password, which is covered on the page about passwords and lockouts.
- What happens to sessions on your other devices; that is a separate subject with its own page.
- Whether Apple or Google sign-in is switched on in the app you are holding. The code shows only that a provider is drawn when it is linked and configured, not what the configuration is.
Where this description was verified
The sequence — Profile, the confirmation stated as irreversible, and the automatic move to the signed-out state and the welcome screen — was read from apps/jewelry-mobile/src/app/account/delete.tsx in August 2026, where the success path is recorded in a comment as leading to the signed-out gate and the welcome route.
The re-authentication state and its distinct message come from apps/jewelry-mobile/src/features/auth/auth-errors.ts, and the attempted clearing of this phone's cached generated images from apps/jewelry-mobile/src/features/auth/auth-provider.tsx, where a failure of that step is deliberately ignored so the flow can complete.
How long the deletion takes on the server, and what it covers there, is not readable from any of these files. This page therefore does not say.
Questions
Why is the app asking me to sign in again in the middle of deleting my account?
Because the server can require re-authentication at that point. It is its own state with its own message: the screen says re-authentication is required rather than reporting that an email address or password was wrong, so it is not a judgement on what you typed.
I signed up with Google and have no password. How do I confirm the deletion?
Through the provider. Where the account has no password field, the delete screen offers an Apple or Google re-authentication button instead — drawn only where that provider is linked to the account, and the Apple one only on iOS.
Do I have to sign out after deleting the account?
No. On success the app moves to the signed-out state on its own and returns you to the welcome screen. There is no further step to perform on the device.
What happens to the images on my phone?
The flow attempts to clear the generated images cached on the device as it finishes. The attempt is best effort and its outcome is not reported on screen, so anything you want to keep should be moved off the phone before you start. The mechanism itself is described on the page about signing out and what it clears.