Forcing a Logout From the Account Settings Menu
I opened the settings section and selected the logout option on purpose. The page returned to the login screen within a few seconds. No confirmation box appeared and no extra warning was shown. The session ended cleanly.
I closed the browser completely and reopened it. The login screen was waiting. Entering the credentials brought the dashboard back with the correct balance and the full market list. Nothing from the previous session had been retained. The forced logout had removed every temporary setting.
What disappeared after the logout
Any market filters I had applied earlier were gone. The default order returned. I used matchexch 247 for the next login and found a completely fresh view. The absence of previous filters confirmed that the logout had been thorough.
A second forced logout the following evening
I repeated the same steps inside the settings menu. The page again returned to the login screen without delay. The next opening required credentials and showed the same clean state. Two consistent results made the behaviour predictable.
Short replies when I described the settings logout
I mentioned ending the session from inside the account menu. Two people answered that they use the same option at the end of each week. One said it removes any leftover filters automatically. Another noted that the logout is faster than clearing browser data. The comments stayed brief.
One habit that formed after the tests
I now log out through the settings menu at the end of any evening that includes multiple market checks. The step takes only a moment and guarantees a clean start the next time. Leaving the session open overnight is no longer the default.
Forcing the logout from the settings menu produced a complete end to the session. The next login always began with a fresh view and required the credentials again. Once that result was consistent the settings option became the ordinary way to close the account. The match schedule continued to decide when the page needed to open next.