Swipey questions: logins, loading and shared devices

It will work, but you will sign in every single visit. The session that keeps you logged in lives in browser storage, so wiping it on exit logs you out by design. If you like that setup, keep it — nothing is lost, since your conversations sit with the account rather than the browser. If you would rather not retype anything, add an exception for the site in whatever clears your cookies, and leave the rest of your rules alone.

Look in your account settings for the email or sign-in section — that is where any change of address is offered, and it is worth doing sooner rather than later if the current inbox is one you might lose. Do it while you can still open both addresses, because verification usually goes to the old one. If you originally signed in through a linked account, check what that link controls before you unpick it, so you do not end up locked out of the route you actually use.

Coming back after a long gap normally just means signing in again, and finding your companions and threads where you left them. The realistic risk is not the service forgetting you — it is you forgetting which address you used, or losing access to that inbox entirely. Before a long break, make sure the sign-in email is one you will still control, and note it somewhere you will find again. That single habit prevents most permanent lockouts.

Test something else first. Open two or three unrelated sites: if they are slow or failing too, your connection is the suspect and there is nothing to fix on the Swipey side. If everything else is fine, move to the browser — reload once, then try a private window, then a different browser entirely. Each step rules out a layer, and by the third one you usually know whether you are dealing with an extension, a cache problem, or something genuinely outside your control.

Blocked cookies and blocked scripts, in that order. The chat needs to set a session cookie to know who you are, and it needs its own scripts to run to draw the conversation. Aggressive tracker blockers, strict privacy modes and content blockers sometimes catch these in the crossfire. The clean test is a private window with extensions disabled: if it loads there, work back through your blockers one at a time until you find the one responsible, then add a single exception rather than switching protection off.

Sometimes, and it is easy to diagnose. A VPN changes where your traffic appears to come from, which can make a session look suspicious or route you through a slower path that times out mid-load. If sign-in stalls with the VPN on and works with it off, you have your answer. Try a different server before you give up on it — usually one location behaves badly while others are fine, and keeping the VPN is perfectly compatible with using the site.

It keeps the visit out of that browser profile: no history entry, no lasting cookie, no saved session once you close the window. That is genuinely useful on a family computer. What it does not do is hide traffic from the network you are on, remove anything already saved before you switched, or protect you if you leave the window open and walk away. Treat it as tidying up after yourself rather than as invisibility, and it does exactly the job you want.

Sign out first if you can still reach the machine — that ends the session properly rather than just hiding it. Then clear the site data for that address in the browser settings, and check the browser password manager for a saved entry, because that is what quietly refills the form for the next person. If the computer is beyond your reach, change your sign-in password from a device you do control, which is the one move that reaches backwards.

Start in your account settings and turn the frequency of anything optional right down — the fewer messages sent, the less there is to notice. On the browser side, decline the notification permission prompt when it appears, since desktop pop-ups are the least discreet thing on this list. If the sign-in inbox is shared with anyone, that is the real weak point, and moving the account to an address only you open fixes it more thoroughly than any setting will.