◼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 devices
More than one at once

The devices: how many sessions an account can hold

One account, several devices, several live sessions. This page is about the limit on that number, the order in which the limit bites, and the one control that ends every session at once.

Open the partner accountWhat signing out does not do
Session spec
sign-ins
5
limit
3
live
3
ended by limit
2
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

An account normally allows a published number of sessions at the same time, and a new sign-in at the limit ends the oldest rather than being refused. On the samples a limit of three turned five sign-ins into three live sessions and two ended, oldest first. A single control signs out every session at once.

Five sign-ins against a limit of three

Sample C follows one invented account through a morning of sign-ins and records which sessions ended, at what time, and why.

Sample C - five sign-ins against a concurrency limit of three sessions
Sign-inTimeDeviceOutcome
1st09:00laptoplive, then ended by the 4th sign-in
2nd09:10phonelive, then ended by the 5th sign-in
3rd09:20tabletlive
4th09:30laptop againlive, and ends the 1st
5th09:40phone againlive, and ends the 2nd
5 sign-ins40 minutes4 devices3 live, 2 ended by the limit
sample C - who the limit ends, and in what order live at the end = tablet 09:20, laptop 09:30, phone 09:40 → 3 sessions ended by the limit = the 09:00 (lived 30 min) and the 09:10 (lived 30 min) → 2 sessions ended by the idle clock = 0; ended by the lifetime = 0 the oldest lives shortest, so the ending is first in, first out.

The two consequences of a limit

The first is that a new sign-in can end a session elsewhere without doing anything wrong and without warning the other screen, which is why an account can appear to sign itself out on a device nobody touched. The second is that the limit is what makes the sign-out-everywhere control necessary: with several sessions live, ending one at a time is slow, and the case the control exists for is a device you no longer have.

Re-signing in on the same device counts as a new session on the samples, which is why five sign-ins came from four devices. That detail matters when reading a session record: the same device name can appear more than once, and each line is a separate interval with its own clocks.

Read next

The recordThe list of sessions and what each line carriesStay signed inThe token that makes the next sign-in freeThe endingsIncluding the limit, as one of the five