A new phone can leave a sweepstakes account’s sign-in route unclear even when its app icon is still there. Before replacing a device, separate three questions: which account identifies you, where any verification code comes from, and which service can change the registered contact details.
“Sign in with Google” and Google Authenticator answer different questions. Google explains that its sign-in service uses your Google Account to authenticate you with a linked app. Authenticator instead generates one-time codes for services that support that form of verification. Having Authenticator installed does not establish that a casino account uses Google sign-in. [1][2]
This is a preparation checklist based on primary documentation opened on Oct. 27, 2026. We have not tested an operator’s current sign-in or device-transfer process, and the sources’ original publication dates were not established.
Make a private access map
Our original access map keeps the dependencies separate:
| Record | What to identify | What it does not establish |
|---|---|---|
| Operator account | The service and the account identifier you already use | Whether a different email address belongs to that same account |
| Sign-in method | An operator password or a linked identity-provider account | Whether a code-generator app has been transferred |
| Verification method | The method actually enabled for that account, if any | That installing an app restores the method |
Record labels and methods, rather than passwords, one-time codes, backup codes or setup QR images. Keep this map private. An operator using one sign-in method does not establish what another operator supports.
Funrize’s terms illustrate why the distinction matters. Clause 4.5 describes Google, Facebook and Apple login alternatives to selecting a separate password. Clause 4.4 directs users to support when contact details change. Those are published account conditions, not a confirmation that every described option appears on a particular device today. [3]
Check which transfer route applies
Google’s Authenticator guidance distinguishes synchronization through a Google Account from manual transfer when the app is used without one. The manual route requires the old device containing the codes as well as the new device. [2] Do not assume an ordinary phone migration completed that separate step; use the current official instructions for the setup you actually have.
If the operator account uses Google sign-in, identify which Google Account is linked. If it uses a separate password and an Authenticator code, those are different dependencies. Neither observation alone establishes that the operator’s registered phone number or email has changed.
A fictional example
Suppose a reader normally signs into a sweepstakes service with one Google Account, while their Authenticator app holds a code for a different service. Seeing that code on a replacement phone would confirm nothing about which Google Account the sweepstakes service recognizes. This example is invented; it does not describe Funrize’s authentication requirements.
The useful next question is specific: “Which existing sign-in method and registered contact details apply to my account?” Ask through the service’s official route without supplying a password or live code. Our unexpected account-message check covers unsolicited requests for credentials.
This preparation cannot guarantee account recovery, transfer an account between people, or establish redemption eligibility. It helps identify which service and which existing method a question concerns.