Your browsers
Every browser holding a session, and throwing one out — which takes effect on its very next request.
security lists every browser currently holding a session for your account:
what it is, roughly where it signed in from, and when it was last used.
Throwing one out
Press it and that session ends. The browser fails on its very next request —
not in an hour, not when something happens to lapse.
Do it for the laptop you sold, the machine at the office, the tab on a friend's
computer.
What it does not do immediately
Immediately for everything on beafk cloud; up to an hour for a panel that
browser was already inside, because the machine gave it a session of its own and
honours that without calling us. Why, and what to do on the day an hour is too
long:
cutting somebody off takes up to an hour.
Your own current session
It is in the list too, marked. You cannot throw yourself out from under your own
session by accident.
The device key
Each browser also holds a key it made and cannot export, which is what a
certificate is issued against. Clearing your browser's site data destroys it —
that browser then makes a new one and asks for a fresh certificate the next
time. Nothing is lost.
It is also why a session cannot be moved: copying the cookie to another machine
gives you a cookie without the key it was paired with.
What we hold about those sessions, and what we never see, is
what beafk can see.