◼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 / Overview
Eight invented samples, one interval

Still signed in: what a session is and what it is not

An account is permanent; a session is the temporary interval you use it through. This desk explains that interval: which clock ends it and when, what resets the clock and what does not, how long a persistent sign-in can outlive it, how many devices can hold one at once, and what survives the moment it ends.

Open the partner accountWhat signing out does not do
Session spec
samples
10 invented
idle timeout
30 minutes
absolute lifetime
12 hours
persistent token
30 days
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.
09:11 09:26 09:41 09:56 10:11 last action 09:41

One sign-in at 09:00 under a 30-minute idle clock. The hatched band is the allowance the last counted action bought: from 09:41 to 10:11. The same session never touched again ends there, and touched constantly ends at 21:00 on the other clock instead - 10 hours 49 minutes later, from the same two settings.

laptopsigned in 09:00 · the 4th sign-in ended itended
phonesigned in 09:10 · the 5th sign-in ended itended
tabletsigned in 09:20 · still openlive
laptop againsigned in 09:30 · still openlive
phone againsigned in 09:40 · still openlive
A limit of three sessions. Neither clock ended anything here: the 4th and 5th sign-ins ended the two oldest sessions, and the three that remain are the newest three. A control beside this list signs out every session at once, which is the only ending on the list that removes a persistent sign-in from a device you no longer have.
Direct answer

A session is the interval between signing in and being signed out, and two clocks can end it: an idle clock that runs from your last counted action, and an absolute lifetime that runs from the sign-in itself, whichever comes first. A placed bet is not in the session and survives it; a betslip that was never placed is not, and does not. Closing the tab ends neither clock.

What the samples show

The desk's whole argument fits in one figure, so it is stated first and then shown eight ways. The interval you are signed in for is not the interval you are using the account, and the two are set by different clocks. On the samples, a session signed in at 09:00 with a 30-minute idle timeout and a 12-hour absolute lifetime ends at 10:11 if you stop touching it at 09:41, and at 21:00 if you never stop - a range of 10 hours 49 minutes from the same settings. Five of eight candidate actions do not reset the idle clock at all, so a screen can look busy while the clock runs down. The bet placed two minutes before a session ends lives 14.7 times as long as the whole idle window that ended it. And the longest-lived thing in the whole picture is the one nobody looks at: a 30-day persistent sign-in outlives a 30-minute idle window by 1,440 times.

None of the samples describes a real operator, a real account or a real person. They are eight invented sets of settings and times, defined on this page, and every figure anywhere on the site is derived from them and can be re-derived from the arithmetic shown beside it.

Eight samples

Sample A
One session, two clocks

One sign-in at 09:00 under a 30-minute idle timeout and a 12-hour absolute lifetime, with activity that stops at 09:41.

signed in
09:00
last activity
09:41
ends
10:11 or 21:00
Sample B
What counts as activity

Eight candidate actions and which of them the invented rules count as activity.

candidates
8
counted
3
not counted
5
Sample C
The devices

Five sign-ins against a limit of three sessions at once, and which two ended.

sign-ins
5
live
3
ended by the limit
2
Sample D
Three durations

The idle window, the session and the persistent sign-in, measured against each other.

idle
30 minutes
session
12 hours
token
30 days
Sample E
The open bet

A bet placed two minutes before the idle sign-out, and when it is settled.

placed
10:09
session ends
10:11
settles
17:29
Sample F
The endings

The five ways the invented rules allow a session to end, and the ending that is not on the list.

published
5
on the list
5
closed the tab
0 of 5
Sample G
The record

Ten lines of session history, and what each line does and does not carry.

lines
10
device
10
who ended it
0
Sample H
The recheck

Six actions inside a session, three of which ask for the password again.

actions
6
rechecked
3
not rechecked
3

Two further samples are defined on the pages that use them: sample I on the timeout table and sample J on what a session's end touches.

One sign-in, two endings

Sample A is the clearest place to start, because it shows that two clocks are running from two different moments. The idle clock starts again on every counted action; the absolute clock never restarts until the session is replaced by a new one.

Sample A - one sign-in at 09:00 on a 30-minute idle timeout and a 12-hour absolute lifetime
MomentClockEnds atWhy
signed in09:00-both clocks start here
last counted action09:4110:11idle clock restarts from here
no further action-10:11idle clock reaches 30 minutes
action every few minutes-21:00idle never fires; absolute lifetime does
2 endings, 1 sign-in-10 h 49 m apartsame settings, different behaviour
sample A - one setting, two ends idle ending = last action 09:41 + 30 minutes = 10:11 absolute end = sign in 09:00 + 12 hours = 21:00 gap between them = 10 h 49 m = 10.817 hours so the setting is not "how long a session lasts"; it is two limits and the earlier one decides in every case.

Why the activity list matters more than the timeout

The second worked example is the desk's central finding, and it is arithmetic rather than opinion. A timeout is only as long as its definition of activity allows.

sample B - five of eight actions do not reset the clock counted: clicking in the account, loading a page, typing a stake → 3 of 8 not counted: scrolling, a stream playing, a bet settling, an email arriving, a betslip left untouched → 5 of 8 on a 30-minute idle timeout, a session signed in at 09:00 and only watched ends at 09:30 - thirty minutes after sign-in, not after the last look. five of eight actions are invisible to the clock, and the screen shows none of it.
Every figure on this site is illustrative and derives from the eight samples defined on this page. No real operator, platform, device or person is quoted or described. The desk explains how a mechanism works; it names no product, recommends nothing and rates nothing, and it gives no selection and no prediction.

Read next

The sessionA temporary interval inside a permanent accountThe idle timeoutThe clock that restarts, and what restarts itThe devicesHow many sessions one account can hold at onceThe open betWhat a session end does and does not touch