Deloosh signs you out when the API rejects your authentication token. Sign in again with Google or an email magic link; your workspace data is stored server-side and is not lost when the browser session is cleared.
When the app receives an unauthorized response, it clears the local auth session and reports “token rejected — sign in again.” This is a security boundary: the app does not keep retrying with a rejected credential.
Deloosh does not publish a fixed session-duration promise. Sessions normally refresh automatically, but you may occasionally be asked to authenticate again.
If you need a reminder of the two sign-in methods, see GS-2, How do I sign in? (No password — by design).