Jewelry AI · Account

Signing out on this phone is also a cleanup of this phone

Ending a session somewhere else and ending the one you are sitting in front of are two different operations. On this device the sign-out reaches further than the account: it attempts to remove the generated images cached on the phone, and it closes the device's Google session so the next sign-in starts with an account picker.

Three actions carry the same word

Which one you performed decides what happened on the phone in your hand, and whether a failure would have been shown to you.

Ending another device's session from the list.: That device is dropped. The phone you are holding keeps its session and keeps its local data.
Ending your own session from the list.: This goes through the ordinary sign-out flow and clears local data with it. No separate single-session cancellation is sent for your own entry, because the sign-out already covers it.
Signing out of all devices.: The local sign-out completes, and a server failure is passed to the screen instead of being absorbed. An ordinary sign-out does the opposite and swallows such an error, because the local cleanup is treated as enough on its own.

What leaves this phone with the sign-out

Two things happen locally beyond ending the account session. The generated images cached on the device are cleared, and the device's Google session is closed.

The first matters most on a shared or resold phone: the point of clearing the cache at sign-out is that the previous user's generated images are not left sitting on the device for whoever picks it up next.

The same local cleanup runs when an account is deleted. The deletion flow itself, and everything it involves on the server, belongs to a separate page.

The Google session on the device is closed; Apple has no matching step

As part of the sign-out the app closes the device's own Google session. The visible result is at the next sign-in: Continue with Google opens the account picker rather than restoring the account that was in use before.

This is the behaviour that makes a sign-out on a shared phone mean something to the next person who opens the app.

It applies to Google alone. There is no equivalent local cleanup call on the Apple side, and this page does not imply one.

Reading the device list, including when it will not load

The list is a screen like any other and can fail on its own.

A failure to load is reported, with a retry.: You are shown an error and given the chance to try again rather than an empty list that could be mistaken for no other sessions.
An older session may arrive without a label.: In that case a readable name is derived from the platform, so an entry you do not recognise is not in itself evidence of a session that is not yours.
Your own entry behaves differently from the others.: Ending it is the ordinary sign-out with its local cleanup; ending someone else's is a drop and nothing more.

Before this phone leaves your hands

Each item corresponds to a behaviour stated above, not to general advice.

Sign out on the device itself, so the local cleanup runs there rather than only dropping the session from elsewhere.
Open the app once afterwards and confirm that Continue with Google offers the account picker.
Treat the cached generated images as attempted-cleared, and verify on the device where those images matter.
If you used sign out of all devices, check whether a server error was reported before recording the other sessions as closed.
Do not read an unfamiliar entry in the device list as proof of an intruder; an unlabelled older session is named from its platform.

What this page leaves to other pages, and what it cannot state

Any session lifetime, refresh interval or revocation timing. No figure of that kind is readable from the client.
What the server does when a session is revoked, and what a dropped device experiences at the moment it is dropped.
The steps of the account deletion flow, and what deletion does on the server. A separate page covers the flow; the server side is outside this surface altogether.
What a password change does to your devices. That belongs to the page on passwords and lockouts.
Whether Google or Apple sign-in is switched on in the app you are holding; the code shows only that a provider is drawn when it has been configured.
Whether the cached images were in fact removed on a particular device. The clearing is attempted and the outcome is not reported on the screen.

The code these statements were read from

All of the above was read from the Jewelry AI mobile client in August 2026. The local cleanup, the closing of the device's Google session and the surfaced failure of the everywhere action come from apps/jewelry-mobile/src/features/auth/auth-provider.tsx, where the cache clearing is written to be ignored on failure, the Google sign-out is called as part of the flow, and the server error of the wider action is re-raised rather than swallowed.

The difference between ending your own entry and ending another device's comes from apps/jewelry-mobile/src/features/auth/sessions-screen.test.tsx, where the comment records that no single-session cancellation is sent to the server for your own device because the sign-out flow already clears everything.

Server-side session rules are not part of that reading, and this page does not extend into them.

Questions

Does signing out delete my images from the phone?

The sign-out attempts it. Clearing the cached generated images is part of the flow, which is what keeps a previous user's images off a shared phone, but the step is best effort: if it does not succeed the sign-out completes anyway. Treat the images as attempted-cleared rather than certainly gone.

Why does the app sign back in with the same Google account?

It should not, after a sign-out on that device. The sign-out closes the device's own Google session, so the next Continue with Google opens the account picker. If the picker does not appear, do not assume the earlier sign-out went through on that device.

Sign out of all devices reported an error. What is my position?

The local sign-out completed. The error you were shown is the server's, and it is surfaced deliberately so that you are not told everything closed when it did not. Until it succeeds, the other sessions cannot be recorded as ended.

There is an entry in my device list I do not recognise. Is someone else signed in?

Not necessarily. Older sessions can arrive without a label, and the screen derives a readable name from the platform instead, which can look unfamiliar. Ending that entry drops that device alone and changes nothing on the phone you are holding.