◼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 / Questions
Twelve questions

The questions, in full

Twelve questions the desk is built to answer, each in a few lines and each traceable to a sample on the site. The page is a starting point as well as a reference.

Session spec
questions
12
samples
10
answers
direct
arithmetic
shown
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 desk answers twelve questions about sessions: what one is, what ends it and when, what counts as activity, what the persistent sign-in does, how many devices can hold one, what a shared device leaves behind, what happens to a bet, why a password is asked for twice, what the record shows and how many published endings exist.

The shortest answers

A session is the interval you use the account through; the account is what survives it.
Two clocks end it: an idle one from your last counted action and an absolute one from the sign-in.
The clock counts actions, not attention: 3 of 8 candidates counted, 5 of 8 did not.
A persistent sign-in outlives both clocks and can run for 30 days, or 1,440 idle windows.
An account can hold several sessions at once, and the limit ends the oldest first.
A placed bet is in the account and survives; a betslip is in the session and does not.

Read next

The questions, in full

q01

What is a session in a gambling account?

The interval between signing in and being signed out. It holds your authenticated use of the account and nothing else: a placed bet, the balance and your limits are held by the account and survive it. Sample A signs in at 09:00 and ends at 10:11 or 21:00 depending only on activity.

q02

What signs me out while I am idle?

The idle clock, which counts from your last counted action rather than from the sign-in. On the samples it ranges from 15 to 240 minutes, and with activity at 09:41 a 30-minute window ended a session at 10:11.

q03

What counts as activity?

An action rather than a sight: on the samples a click, a page load and typing in a field count, while scrolling, a stream playing, a bet settling, an email arriving and an untouched betslip do not. Three of eight candidates counted, so 5 of 8 happen without the clock noticing.

q04

Can I keep a session open forever by staying active?

No. The absolute lifetime runs from the sign-in and no activity postpones it: on the samples 12 hours, so a sign-in at 09:00 ends at 21:00 even if the account was clicked a second earlier. Activity can buy up to 24 idle windows and not one minute of the lifetime.

q05

What does the box that says stay signed in do?

It stores a separate token so the next visit creates a session without a password. On the samples it lasts 30 days - 60 sessions or 1,440 idle windows - and it outlives both clocks, which is why it is the object worth revoking deliberately.

q06

How many devices can use my account at once?

Up to a published limit, and a sign-in at the limit ends the oldest session rather than being refused. Sample C turned five sign-ins against a limit of three into three live sessions and two ended, first in, first out.

q07

Does signing out on a shared computer clear it?

It removes the persistent token on that device, which is the action the samples treat as the one a reader controls. Closing the tab does not: a tab closed at 10:11 and reopened at 13:11 came back signed in, 1 of 1.

q08

What happens to my bet if I am signed out?

Nothing. The bet is held by the account. On sample E a bet placed at 10:09 settled at 17:29, 440 minutes later and long after the 30-minute window that ended the session.

q09

Why does a withdrawal ask for my password again?

Because a session proves a past sign-in, not a present person. On the samples three of six actions are rechecked: changing the password, adding a payout method and requesting a withdrawal. A bet and a deposit are not.

q10

What does the session record show?

A list of sign-ins with a time, a device and sometimes an approximate location. Ten sample lines carried ten device names, six locations and three addresses, and none recorded who or what ended the session.

q11

How many ways can a session end?

Five: the idle clock, the absolute lifetime, signing out, the concurrency limit and a revocation. Closing the tab is not among them, and only signing out and a revocation remove the token.

q12

Does any of this change the account?

No. The balance, the bets, the limits and the record are the account, and a sign-out is a statement about an interval. That distinction answers almost every question on this page.