◼Still Signed In signed in Open the partner account
paid
Affiliate disclosure. The partner link in the masthead and in the band beside the copy on this page is a sponsored link to a partner operator, and this site may be paid if you open an account through it, at no extra cost to you. It carries rel="sponsored noopener" and opens in a new tab. The subject of this desk is a session - an interval that ends and leaves nothing behind - so its own interest is stated here rather than left for a footer: one link funds the site, and no operator, platform, device, browser or product is named, rated or recommended anywhere on it.
Still Signed In / The session
Temporary inside permanent

The session: a temporary interval inside a permanent account

Almost every confusion about being signed out comes from treating one word as two things. This page separates the account from the session it is used through, and says which one holds your balance, your bets and your settings.

Open the partner accountWhat signing out does not do
Session spec
signed in
09:00
clocks
2
session ends
10:11
account ends
when you close it
the sessionThe interval between signing in and being signed out. It holds your authenticated use of the account and nothing else; the balance, the bets and the limits are held by the account and survive it.
the two clocksThe idle clock runs from your last counted action and restarts; the absolute lifetime runs from the sign-in and never restarts. On the samples 30 minutes and 12 hours, and the earlier one always decides.
the tokenWhat a persistent sign-in leaves on a device, so the next visit needs no password. On the samples 30 days - 1,440 idle windows - and only a sign-out or a revocation removes it.
Direct answer

The account holds the balance, the placed bets, the limits and the settings, and it exists whether or not you are signed in. The session holds only your authenticated use of it: an identifier, a token, a last-action time and a clock. A session ending therefore changes nothing about the account. It only stops you from operating it until you sign in again.

Two things, one word

On sample A the difference is easy to see, because both clocks are published and both end the same session. The account is the thing that survives both.

Sample A - what the account holds against what the session holds
ItemHeld bySurvives the session
the balancethe accountyes
a placed betthe accountyes
the deposit and loss limitsthe accountyes
the identifier you are signed in asthe sessionno
the token that carries itthe sessionno
the last-action timethe sessionno
a betslip that was never placedthe sessionno
7 itemsaccount 3 / session 43 yes / 4 no
sample A - the two clocks are not the same limit the account has no timeout: it is closed by you, or by an operator's own rules the session has two: an idle clock (30 minutes) and an absolute one (12 hours) 09:00 + 12 h = 21:00; last action 09:41 + 30 min = 10:11 so a sign-out tells you the interval ended, and nothing about the account.

Why the distinction is worth a page

Four everyday questions are answered by it. Why is my bet still running after I was signed out? Because the bet is in the account. Why did my betslip disappear? Because it was in the session. Why does the operator want the password again for a withdrawal? Because a session proves you signed in once, not that you are the account holder now. And why does the site still show my balance when I sign back in? Because the balance was never in the session at all.

The second consequence is about time. An account's history is measured in months and its statements in days; a session's history is measured in minutes and is usually discarded. That is why the record a reader can see is a list of sign-ins and not a list of what happened inside them.

Read next

The idle timeoutThe short clock, and the actions that restart itThe absolute lifetimeThe long clock that no activity can delayThe endingsThe five published ways a session can end