Shared devices and Fair Go sessions explained
You are finishing a session on a device others can reach, and you have two descriptions of what to do that do not use the same words. The practical question is not which wording sounds stricter, but which one actually removes the things that could let someone reopen your account. That means separating stored sign-in data from live sessions, because they are not the same thing.
Saved credentials and live sessions are different problems
When you look at a login screen after signing out, you may see your email already filled in. That prefilled value is not proof that Fair Go kept your password or that your account is still open somewhere. It can come from browser autofill, a password manager, an HTML suggestion or a field the server filled in when it served the page. Each source lives in a different place and needs a different cleanup step. A browser’s saved form data sits on the device, while a password manager may hold it in a vault that syncs elsewhere. Treating the visible suggestion as the whole problem leads people to clear one thing and assume the rest is handled. Instead, identify where the suggestion comes from before deciding what to remove. To keep the decision clear when considering poolworldwide.com, check saved credentials and active sessions separately before leaving.
A live session is a separate matter. It is the authenticated state held on Fair Go’s side, tied to a session token that your browser or app presents. Signing out from the interface usually asks the operator to end that session, but a prompt or a reopened login page cannot prove whether every session tied to the account has been revoked. If someone else has the device and the browser still holds a valid session cookie, they may reach account pages without entering a password at all. So the two descriptions you are comparing are probably answering different questions: one about what the device remembers, the other about what the account still permits. Read each description for which of those it addresses.
A worked example of two competing descriptions
Suppose one description says to sign out and close the browser, while another also asks you to remove saved credentials and review other sessions. These routines address different exposures. A successful sign-out should end the session it covers, but its scope must be checked rather than assumed to include every device. Closing a normal tab can leave stored credentials or other authenticated tabs available. Closing a private-browsing session may also remove that session’s local cookies, so it can have a useful effect; it still does not establish that all server-side sessions were revoked. A password manager is another separate store. The longer routine is useful only where its steps match your actual setup, and an account-session list is an option only if the operator provides one.
Now test the same two descriptions on a device you share but where you have never asked the browser to save a password. The first routine may be enough for the local device, because there is no stored credential to remove, but it still leaves the question of other sessions untouched. The second routine covers that gap, yet its password-clearing step does nothing if no password was saved. This is how you decide which description applies: map each instruction to a specific store of access, then check whether that store exists on your device and account. If a description tells you to do something that has no counterpart in your setup, it is not wrong, just partly irrelevant. If it omits ending live sessions, it is incomplete for a shared device.
A decision method you can repeat
Work through three checks in order. First, end the session from within Fair Go rather than only navigating away, so the operator receives a sign-out request. Second, inspect the login form on that device and identify what is filling it, then remove that source: delete the saved entry in the browser or the password manager, and turn off autofill for the site if it keeps appearing. Third, open the account’s active sessions area if Fair Go provides one and end anything you do not expect, especially sessions from other browsers or devices. Where a description covers all three, it is the applicable one. Where it covers only the first, treat it as a partial instruction and add the missing steps yourself.
Match the wording to the action it actually performs. A direction to close a page alone is not a reliable substitute for confirmed sign-out or removal of saved access. Closing a private-browsing session may discard its local cookies and other temporary data, while closing an ordinary window may leave persistent cookies and saved credentials behind. Neither action by itself tells you the state of every account session on another device. Check the browser’s storage and password manager separately, and use account-session information if it is available. If you cannot identify the source of a saved suggestion, avoid deleting unrelated data at random; locate the relevant saved entry or ask for clarification. The useful comparison is between the specific exposures each routine addresses, rather than the confidence of its wording.
Finish by confirming sign-out, checking any saved access on the shared device and reviewing other sessions where that facility exists. Closing the window can be part of that routine, but its effect depends on the browsing mode and stored data. Once you distinguish those jobs, the two descriptions become easier to compare and the device can be left in a more deliberate state.
