A phone upgrade is a security event, not just a hardware swap. Bingo apps hold a live session token, saved card details and biometric logins that do not travel with your SIM card. Move to a new handset without closing the old one down properly and you leave a working key to your account sitting in a drawer. This walkthrough covers the order of operations for UK bingo apps in 2026: log out on the old device, revoke trusted devices from account settings, then re-enrol biometrics on the new phone.
Why a new handset leaves old access behind
Most bingo apps keep you signed in indefinitely. The app stores an authentication token on the device and presents it to the operator’s server each time you open the app, which is why you rarely type a password after the first login. That token has no idea the phone has changed hands. If you trade the handset in, pass it to a family member or leave it in a drawer, the session stays valid until it expires or someone revokes it.
Biometrics make this worse in a quiet way. Face ID and fingerprint enrolment is tied to the device’s secure hardware, not to your bingo account. Set up a new iPhone and the app has no biometric credential to check against, so it either falls back to a password or, in some builds, keeps the old token alive and skips the check. Either way, the old phone’s enrolment is still registered on the operator’s side until you remove it.
The practical risk is modest but real. A stale token on a device you no longer control can be used to view balances, change preferences or trigger a withdrawal to a saved payment method. Bingo Daily’s reviews of the best bingo apps UK consistently flag session management as the weakest area across operators, and it is the part players almost never check after an upgrade.
The three-step handover, in order
Do the steps in this sequence before you wipe or sell the old phone. Doing them after is possible but relies on the operator’s support team, which adds days to the process.
Step one: log out on the old device
Open the app on the old phone and use the in-app logout, not just a swipe to close it. Closing an app from the multitasking view does not end the session; the token survives. Look under Account, Profile or the hamburger menu for a Sign Out option. On a mobile site, the logout link is usually at the bottom of the account page.
If the old phone is broken or already gone, skip to step two. Revoking trusted devices from a browser on another machine achieves the same result, because it invalidates every token issued to that account rather than just the one on the handset.
While you are in the app, check two things. First, whether a deposit limit is set in the player’s account, and note the figure so you can confirm it carried over. Second, whether any promo code such as WELCOME2026, GOLD50 or BINGO100 is attached to a live welcome offer, since some operators tie bonus eligibility to the device or account rather than the person.
Step two: revoke trusted devices in account settings
Log in to the operator’s site through a desktop or tablet browser. Navigate to the security or privacy section of account settings. Most UK operators list every device that has accessed the account, with the device name, last login date and a remove or revoke button. Remove everything you no longer use, not just the old phone.
This is the step that actually closes the door. Logging out ends one session; revoking trusted devices invalidates all of them and forces a fresh login with full credentials, and usually a second factor, on any device you keep. It also clears any „remember this device” flags that would otherwise skip verification.
If the operator does not expose a device list, use the „log out of all devices” option if one exists, then change your password. A password change invalidates existing sessions at most operators as a side effect. Where neither option is available, contact support and ask them to terminate active sessions on the account.
Use this moment to check the safer play tools. Confirm the deposit limit is still in place, review any session time reminders and check that your contact details are current. BeGambleAware provides guidance on setting limits that survive a device change, and GamStop supports self-exclusion across licensed UK operators if you want a hard block rather than a soft one. GamCare runs a helpline if you want to talk the settings through with someone.
Setting up the new phone without repeating old mistakes
Once the old device is clean, install fresh. Native apps are installed from the App Store or Google Play, and you should install from the store listing rather than a link in an email or text, which is the standard phishing route for account credentials. Check the developer name matches the operator before you tap install, and treat any other source, such as https://bingodaily.uk/bingo-apps/, with caution.
Sign in with your username and password, complete any second-factor step, and let the app prompt you to enrol biometrics. This enrolment is new; nothing transfers from the old handset. If the app offers a „remember this device” toggle, think before enabling it, particularly on a phone you might resell within a year.
The table below compares the main routes players take when moving a bingo account to a new phone, with the trade-offs that matter for security.
| Method | What it does to the old session | Biometrics on new phone | Best for |
|---|---|---|---|
| In-app logout on old device, then sign in on new | Ends the session on that device only | Requires fresh enrolment | Old phone still working and in your hands |
| Revoke trusted devices from a browser | Invalidates every token on the account | Requires fresh enrolment | Old phone lost, sold or broken |
| Password change plus fresh login | Usually kills all sessions as a side effect | Requires fresh enrolment | Operators without a device list |
| Uninstall app without logging out | None; token stays valid until expiry | Not applicable | Never recommended |
| Contact support to terminate sessions | Operator ends sessions manually | Requires fresh enrolment | No self-service security controls |
Re-enrolling biometrics and checking the app’s settings
Open the app after login and go to the security section. Enable Face ID or fingerprint login and confirm it works by locking and unlocking the app once. Then check that the biometric toggle is the only convenience feature enabled; some apps also offer a four-digit PIN that is weaker than the device passcode.
Review the permissions the app requests. A bingo app needs network access and notifications, and nothing else. Deny location and contacts if prompted. Check the app’s storage footprint too; a fresh install is usually under 100 MB, but cached images and video from bingo rooms can push it past 500 MB within a few weeks, which matters on a 64 GB handset.
Confirm the welcome offer situation before you deposit. If you claimed an offer on the old device, the T&Cs usually prevent a second claim on the same account, and creating a duplicate account to chase a new bonus breaches operator terms and can freeze both. The offer landscape differs by operator: 888 Ladies offers an iOS app, Betfred Bingo offers an iOS app, Betfair Bingo offers iOS and Android apps, and Barbados Bingo offers a mobile site rather than a native download. Each route has different session behaviour, so check how logout works on yours.
Finally, set app updates to automatic or check manually once a week. App updates frequently include security patches, and an out-of-date build may keep a session alive longer than the current version would. If you use mobile data rather than Wi-Fi, check the allowance before a large update; bingo apps are small, but a full reinstall with assets can run to a few hundred megabytes.
Write the sequence down and repeat it at every upgrade: logout on the old phone, revoke trusted devices in account settings, then enrol biometrics on the new one. Add a calendar reminder to review the device list every six months, confirm your deposit limit survived the move, and keep the BeGambleAware and GamCare links saved in your browser. Ten minutes of housekeeping now saves a support ticket, and possibly a locked account, later.