The persistent sign-in: the box you ticked once

The box that says stay signed in does not lengthen the session. It replaces it with something that outlives it, and that difference is measured in weeks rather than minutes.

Open the partner account What signing out does not do

Session spec

idle window: 30 minutes
session: 12 hours
token: 30 days
ratio: 1,440 times

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

A persistent sign-in stores a separate token on the device so the next visit creates a session without a password. On the samples the token lasts 30 days against a 30-minute idle window and a 12-hour session. It is the longest-lived credential in the picture, it survives closing the browser, and it is the reason a shared device can still be signed in days later.

Three durations, one account

Sample D puts the three published periods next to each other. Each one is a different object, and only the shortest one is the session.

Sample D - the idle window, the session and the persistent token
Object	Published period	In minutes	Ended by
the idle clock	30 minutes	30	no counted action
the session	12 hours	720	the lifetime, or a sign-out
the persistent token	30 days	43,200	expiry, a password change, or revocation
3 periods	48 times the session chain	43,200	3 different ends

sample D - how far the token outlives the others 12 h ÷ 30 min = 24 - the session lasts 24 idle windows 30 days ÷ 12 h = 60 - the token lasts 60 sessions 30 days ÷ 30 min = 1,440 - the token lasts 1,440 idle windows in minutes: 43,200 against 30 → the ratio is 1,440 to 1.

What the box changes, and what it does not

Ticking it does not change the idle clock or the lifetime. Those still run, and a session created by a persistent token still ends on the same schedule as any other; what changes is that the next visit does not need a password and creates a fresh session immediately. The consequence people miss is the one that matters: signing out is normally what removes the token, so a device where the box was ticked and no sign-out ever happened can be reopened into the account after the session and even after the browser was closed. Closing the tab is not a sign-out, which is the subject of its own page in this desk.

The second consequence is that the token is the most valuable thing on the device. A password can be changed and a session expires by itself; a token that is valid for weeks is worth revoking deliberately, and the standard way to do that is a password change or the sign-out-everywhere control named on the devices page.

Know whether the box is ticked on each device, and treat a tick as a decision with a period attached rather than as a convenience.
Expect the persistent token to outlive the session by a factor of weeks; on the samples it is 60 sessions.
Revoke deliberately when a device is lost, resold or borrowed: a password change is the usual way.
Do not rely on closing the browser to end a persistent sign-in; on the samples it does not.
Sign out rather than close the tab on any device you share, because signing out is what removes the token.

The persistent sign-in: the box you ticked once

Three durations, one account

What the box changes, and what it does not

Read next