A table name is not a portable login
A guest name helps people recognize your seat, but someone typing the same name elsewhere does not become the same account. Browser guest access depends on local session credentials. Clearing browser storage, using a private window or moving to another device can remove access to that local identity.
If you want to keep playing under the same identity, create the account before taking those steps. Use the registration prompt attached to your current guest session. Do not send your session token, password or password-reset link to another person as a way of transferring progress.
Registration and login solve different problems
Registering a new account from the guest flow upgrades the current identity. Logging into an account that already exists selects that other identity. Pitch warns that these histories are not merged, so read the message before proceeding.
If the address you enter already has an account, a duplicate-address error is not proof your guest progress has been saved to it. You can choose to log into the existing account or continue with the guest while deciding. There is no automatic transfer of gems between those identities.
Treat the guest return path as temporary recovery
When a guest logs into an existing account, the browser can keep a session backup and offer Return to my guest profile. That is a convenience for the current browser session, not a permanent cloud backup or an account-merging service. The saved profile must still validate as a guest.
For a registered account whose password you forgot, use password recovery instead. If you cannot recover an identity, contact Support with a description of what happened and your device. Avoid posting private credentials in feedback. The safest long-term habit is to save the guest identity before you leave the browser where it was created.
Check which identity you are trying to preserve
Before changing account state, ask whether your goal is to keep this guest’s progress or return to an account you already own. Those goals use different actions. Creating a new free account from the current guest flow preserves that guest identity. Logging in selects the existing account associated with the credentials you provide. It is not a request to combine two histories. This difference matters most after a good guest session, when you may assume that any successful login will attach the new match results and cosmetics to the account you choose.
A display name is not proof of identity. Two browser sessions can use similar names without sharing credentials or progress. The name helps people recognize the seat; the session determines which profile is actually in use. If you are unsure, stop before clearing browser data or switching to another window. Read the current account prompt and the warning about existing-account login. Taking a moment to identify the intended profile is safer than treating a familiar name as evidence that every device is already using the same account.
Walk through two different account scenarios
In the first scenario, you played as a guest and have never created a registered Pitch account. While still using that guest profile, choose the option to create a free account and complete registration with an address that can be used for the new account. The purpose is to upgrade the identity you were just playing with. Afterward, use the registered credentials when moving to another supported signed-in device. Do not rely on recreating the guest name elsewhere, because that does not carry the original session with it.
In the second scenario, you already have an account but played several games as a different guest session. Logging into the existing account returns you to that account’s identity. The guest progress is not automatically merged. If the browser offers a return-to-guest control, it can help you revisit the saved local guest session, but it is not a transfer command. A duplicate-address error during registration is a clue to pause and choose which identity you intend to use, rather than repeatedly submitting and assuming the histories will eventually combine.
Understand what a browser-session backup can do
The saved guest return path is deliberately narrower than permanent account recovery. It can remember the guest session when you switch into an existing account in the same browser session. Before restoring it, the app validates that the saved credentials still refer to a guest. That check prevents a stored value from being treated as unquestioned proof of a valid profile. The convenience depends on the backup still being available and valid. It should not be presented as a durable cloud archive that survives every browser reset, closed private session or device change.
If returning fails, avoid destructive troubleshooting as your first response. Clearing all local storage can remove the very session information you are trying to preserve. Note the current screen and the action you attempted, then use Support if you need help understanding the options. Do not copy session tokens into a support message or send them to a friend. Account credentials grant access; they are not ordinary diagnostic text. The safest everyday approach is saving the intended guest profile before leaving the browser where you have been playing.
Use password recovery for a registered login problem
For an account already registered with email, forgetting the password is a different problem from losing a local guest identity. Use the password-recovery flow for that registered account rather than creating a new guest with the same name. Follow the current link instructions and keep reset links private. A reset link is a credential, not a resource to share in a screenshot or group chat. If you requested several links, use the appropriate current one and pay attention to expiry or already-used messages rather than assuming any older message remains valid.
When reporting an account problem, describe whether you were a guest or registered, which device and browser you used, and whether you changed devices, signed into an existing account or cleared local data. Those details explain the account transition without revealing the secret used to authenticate. Support can understand the sequence more easily from “I logged into my older account after a guest match” than from a vague statement that all progress vanished. Clear expectations about identities prevent the problem as often as a recovery button can resolve it afterward.
Before you leave this browser
If you want to keep this guest identity, use its create-account option before clearing data, moving devices or starting a separate private session. If you want an older account instead, read the warning that progress does not merge and make that choice deliberately. Keep passwords and recovery links private. A table name alone is not a login, and a temporary guest-return backup is not a permanent account archive. Knowing these distinctions is more useful than repeatedly trying different entry buttons after a profile switch. When you need help, describe the sequence of actions and device rather than sharing the credential that grants access to the account.