Every time you close the Supabet Casino app and open it again hours later, something has to remember that you already logged in. On Android that “something” is usually SharedPreferences, a plain XML file sitting in the app’s private storage. On iOS it is the Keychain, backed by hardware-level encryption. Both mechanisms are ordinary mobile engineering, and both interact with device backups in ways that matter once real money is involved. A restored backup can carry a live authenticated session onto a new handset, and that is exactly the kind of event a licensed operator watches for.
This piece is a technical walkthrough for players who want to understand what sits behind the login screen of a Supabet Casino Canada account. It covers how session tokens are written and read on each platform, what travels inside an iCloud or Google backup, and where the platform defaults collide with Supabet casino terms. The operator behind the brand, Supabet Entertainment Ltd, holds the Curacao eGaming licence 8048/JAZ, and that offshore casino licence requires identity checks before payout. Session persistence is convenient, but it also creates a paper trail the cashier team will read closely when you request an Interac withdrawal from a device it has never seen.
Keep three facts in view as you read. First, Supabet Casino is licensed by Curacao eGaming under number 8048/JAZ, so dispute recourse runs through the Willemstad regulator rather than a Canadian provincial framework, and the operator is not part of the Ontario regulated market. Second, the app exists in three builds, an Android app, an iOS app and a mobile browser build, and each stores credentials differently. Third, Supabet Casino sets ceilings and wagering multiples through its own operator terms, which means the account-security clauses you agreed to at sign-up are the ones that govern a mismatched restore. The sections below treat backup migration as a security event with a defined resolution path, not as a mystery.
How Mobile Casino Apps Persist Sessions Between Launches
Open the Supabet Casino app after a week away and you land on your balance, not a login screen. That behaviour is not magic. It is a stored credential plus a refresh routine, and where that credential lives on the device determines how exposed it is to backups, clones and forensic inspection.
Every session begins with a server-issued access token and a longer-lived refresh token. The access token expires in minutes. The refresh token can be exchanged for a new pair without re-entering a password. If the app kept the refresh token only in memory, it would vanish on process kill. Android reclaims background processes aggressively, and iOS suspends apps within seconds of the user switching away. Without persistence, a player checking a bet on the sportsbook and returning to a slot would face a password prompt every few minutes. No casino could retain users under those conditions.
Two storage models, one shared weakness
Android apps write small key-value pairs to SharedPreferences, an XML file inside the app’s private data directory. Supabet’s Android build, like most casino clients, likely stores a device identifier, a session flag and possibly a refresh token there. The file is plain text. On a rooted device, or through a full-device backup, it can be read without decrypting anything. The EncryptedSharedPreferences wrapper exists precisely because the default is inadequate, and whether a given build uses it is not something a player can see from the outside.
iOS takes a different route. The Keychain is a system-managed, encrypted store tied to the app’s entitlements, and items can carry access classes such as “when unlocked” or “this device only.” The strictest class, kSecAttrAccessibleWhenUnlockedThisDeviceOnly, excludes the item from iCloud and encrypted local backups. A laxer class lets the credential travel to a new iPhone during a restore. Apple leaves that choice to the developer, so two casino apps with identical features can behave very differently after a device upgrade.
The Supabet Casino offers an Android app, an iOS app and a mobile browser build. The browser path stores session state in cookies and localStorage, which follow browser sync rules rather than app entitlements. Each of the three paths has its own backup behaviour, and each is governed by the same Supabet casino terms on account access.
One more baseline fact matters for everything that follows. Supabet Casino is licensed by Curacao eGaming under number 8048/JAZ, and the licence holder is Supabet Entertainment Ltd. That offshore casino licence places identity verification duties on the operator, which is why a session that reappears on a different handset can trigger a review rather than a silent re-login.
- Access tokens: short-lived, held in memory, reissued silently.
- Refresh tokens: persisted, the real target of any backup or extraction.
- Android: SharedPreferences XML, plain text unless explicitly encrypted.
- iOS: Keychain with developer-chosen access classes controlling backup inclusion.
- Browser: cookies and localStorage, synced by browser account settings.
SharedPreferences on Android: What Supabet’s App May Store and Why It Matters
Android gives developers a deceptively simple storage primitive: SharedPreferences. It writes key-value pairs to an XML file inside the app’s private data directory, typically /data/data/<package>/shared_prefs/<name>.xml. On a stock, non-rooted phone, other apps cannot read that file. The protection is the Linux user ID sandbox, not encryption. The values sit on disk in plain text, and anyone with root access, a debug build, or a forensic image can read them with a text editor.
That distinction matters for a casino app because session persistence is usually built on exactly this store. A token, a refresh key, a player ID, a “remember me” flag, the last balance snapshot: all of it fits neatly into a preferences file. Supabet Casino offers an Android app alongside its iOS app and mobile browser build, and the same pattern applies to any Android casino client. What sits in those XML keys determines how much a stolen or backed-up device exposes.
What Typically Lands in the Preferences File, and What Should Not
Walk through the keys you would expect in a casino build and sort them by sensitivity:
- Benign: locale, last selected game category, notification opt-in, app version marker, whether the intro screen was dismissed.
- Sensitive but low impact: last known currency (CAD, USD or EUR), preferred deposit method such as Interac, cached VIP loyalty tier label.
- High impact: bearer tokens, refresh tokens, session cookies, anything that lets a server accept a request as the logged-in player.
A well-built client stores only the first two groups in SharedPreferences and keeps tokens in EncryptedSharedPreferences (backed by the Android Keystore) or in memory with a short-lived refresh flow. A weaker build drops a long-lived token straight into the XML. You cannot tell which from the outside, which is why Supabet casino review write-ups that claim “bank-grade encryption” without naming the storage mechanism are worth discounting.
The practical implications for players are concrete. First, Android’s auto-backup can sweep SharedPreferences into Google Drive unless the developer excludes the file via backup rules, so a plain-text token can leave the device without the player doing anything. Second, a token in SharedPreferences survives app updates and cache clears, so “log out everywhere” is not the same as clearing app data. Third, shared or resold handsets with root access expose the file directly, and a copied token can drive an authenticated session from another location, which is exactly the kind of mismatch that identity verification and KYC documents are designed to catch before an Interac withdrawal clears.
The checklist takeaway: assume the XML exists, assume it is readable with sufficient access, and treat any token stored there as a credential rather than a convenience.
Keychain on iOS: Secure Enclave Protections and Their Limits
On iOS, Supabet’s app does not get a plain-text XML file. Session tokens, refresh credentials and any stored login identifiers go into the Keychain, Apple’s encrypted credential store. Each item is sealed with keys held in the Secure Enclave on devices with an A7 chip or later, so the raw value never sits in a file the app can read directly. The app asks the Keychain for the item, the system checks the access policy, and the value is returned only if the policy passes.
The access class attached to each item decides what can unlock it. The relevant ones for a casino app:
- kSecAttrAccessibleWhenUnlocked: readable only while the device is unlocked. The default choice for a session token that should not survive a powered-off phone.
- kSecAttrAccessibleAfterFirstUnlock: readable after the first unlock following a reboot, even if the screen locks again. Common for background refresh tokens.
- kSecAttrAccessibleWhenPasscodeSetThisDeviceOnly: requires a passcode and is excluded from backups entirely. The strongest option, and the one that stops cross-device carryover.
- kSecAttrAccessibleAlways: deprecated and now heavily restricted. If an older Supabet build used it, the token is far easier to extract from a jailbroken or imaged device.
The “ThisDeviceOnly” suffix is the pivot point for backup behaviour. Keychain items without it are included in encrypted iTunes, Finder and iCloud backups, and they restore onto a new iPhone. Items marked ThisDeviceOnly do not migrate; the new device starts with an empty credential slot and the user has to log in again. For an offshore casino licence holder like Supabet Entertainment Ltd, which operates Supabet Casino under the Curacao eGaming licence 8048/JAZ, that distinction matters. A restored token means an authenticated session appears on hardware the casino has never fingerprinted.
Limits sit on top of the encryption. The Secure Enclave protects key material, not the logic around it. If the app stores a long-lived refresh token with a permissive access class, the encryption buys little: the token restores to a new phone and works until it expires. There is also no server-side visibility into how many devices hold a valid token unless the backend tracks it. Keychain synchronisation via iCloud adds another path, since items flagged for sync can appear on a second device signed into the same Apple ID.
For the iOS build, the practical checks are the access class on the session item, whether synchronisation is disabled, and the token lifetime set server-side. The Supabet casino terms and the identity verification duties that follow from them are covered next, because a restored Keychain item is often what triggers a mismatch flag during KYC review.
Device Backup Restores and Cross-Device Session Carryover
A phone upgrade is where session storage stops being an abstract concern. Restore an Android or iOS backup onto a new handset and the app data comes with it: the same XML files under SharedPreferences, the same Keychain items on iOS if the right access class was used. Launch Supabet’s app after that restore and the client can present a token the server still considers valid. No password prompt, no one-time code, just a session that followed the backup across devices.
On Android the mechanism is unglamorous. Auto Backup uploads app data to the user’s Google Drive quota, typically capped at 25 MB per app, and restores it during first-run setup on the new device. If Supabet’s Android build keeps its auth token in a standard preferences file and does not exclude it from backup rules, that token is in the archive. On iOS the equivalent path is an encrypted iTunes or Finder backup or an iCloud device backup. Keychain items marked kSecAttrAccessibleWhenUnlocked without the ThisDeviceOnly suffix are included; items set to WhenUnlockedThisDeviceOnly or AfterFirstUnlockThisDeviceOnly are not, because the suffix exists precisely to stop migration. Which class a casino app uses is not visible to players, so treat any assumption about it as unverified.
What happens next is where the casino’s fraud systems wake up. A token minted on a Pixel in Mississauga suddenly appearing from an iPhone in Calgary, with a new device fingerprint and a fresh IP, is a classic account-takeover signature. Supabet’s platform sees a session that never logged in on the new hardware, and its risk engine cannot tell a legitimate restore from a stolen backup. The usual response is a soft lock: the session is killed, the account is flagged, and the cashier holds withdrawals until identity verification clears.
- The device fingerprint changes while the token stays the same.
- The IP and rough geolocation shift to a new city or province.
- The session age looks impossible for a device that was activated hours ago.
- Any pending Interac withdrawal sits in review while KYC documents are re-checked.
Two practical consequences follow. First, a restored session is not a free pass. It is a trigger. Second, players who sell or trade in an old phone without wiping it may hand over a live session inside the backup image, which is a far bigger problem than a forgotten password. Before any restore, sign out of Supabet on the old device, then wipe it. After the restore, expect a verification request and have ID ready.
Supabet Casino Terms, Curacao eGaming Licence 8048/JAZ, and Account Security Obligations
Supabet Casino is licensed by Curacao eGaming under number 8048/JAZ, and the licence holder is Supabet Entertainment Ltd. The practical consequence for a restored session is simple: the operator is required to know who is holding the account at the moment of a payout request, not who happened to hold it at sign-up. That obligation sits behind the identity checks players meet at the cashier, and it is the reason a migrated session on a new handset can stall a withdrawal even when the login itself still works.
Read the Supabet casino terms with three clauses in mind.
- One account, one named holder. Account sharing, resale, and use by a third party are prohibited. Restoring a backup onto a family member’s phone and leaving the session live can look like sharing from the operator’s side, regardless of intent.
- Verification duties. The terms reserve the right to request KYC documents, including photo ID and proof of address, before a first payout or after a device, payment-method, or location change. Under the Curacao eGaming framework, identity checks before payout are a licensing requirement, not an optional courtesy.
- Consequences of a mismatch. Where the device fingerprint, IP region, or payment instrument does not match the verified profile, the operator may freeze the cashier, void bonuses, or suspend the account pending review. Bonus funds tied to uncompleted wagering multiples are typically forfeited in that scenario.
The Supabet casino terms also set ceilings and wagering multiples through its own operator terms rather than through the licence. Withdrawal limits, cashier processing windows, and bonus clearing times are commercial choices, and they can be changed with notice. The licence governs conduct and gives players a route of recourse; it does not fix a maximum payout.
That recourse runs through the Curacao regulator in Willemstad. Supabet Casino is not part of the Ontario regulated market, so players in Ontario have no provincial framework or AGCO dispute channel behind the account. Complaints go first to the operator’s support desk, then to the Willemstad regulator, and the process is slower and more document-heavy than a provincial one. For players elsewhere in Canada, the same applies: the Curacao eGaming licence 8048/JAZ is the backstop.
Two habits keep a restored session from becoming a verification case. First, if a phone is sold, traded, or handed down, sign out of the app and clear app data before the factory reset, so the token never enters a backup. Second, when you move to a new device deliberately, message support before the first withdrawal and confirm which documents they want. A short paper trail beats a frozen cashier.
Practical Guidance for Supabet Casino Canada Players: Reviews, Backups, and Safe Restores
Treat session persistence as an account-security decision, not a convenience setting. The steps below are the ones that matter for a Supabet Casino Canada player moving between phones, or judging what a Supabet casino review says about app security.
Checklist: reviews, backups and verification flags
- Audit the review’s security claims. A credible Supabet casino review names the licence and the entity behind it. Supabet Casino is licensed by Curacao eGaming under number 8048/JAZ, held by Supabet Entertainment Ltd. Reviews that skip the Willemstad regulator, the offshore casino licence number, or the cashier ceilings are recycling marketing copy.
- Match claims to the terms page. Withdrawal limits, wagering multiples, bonus clearing times and KYC documents should be quoted from Supabet casino terms, not paraphrased. If a review says “instant Interac withdrawal” but the terms list a pending window and identity verification before payout, trust the terms.
- Turn off app-data backup before you migrate. On Android, exclude the Supabet app from Google backup or set the device to not restore app data during setup. On iOS, use an encrypted local backup and deselect the app, or skip iCloud restore for that app. A restored token is what triggers an identity-verification mismatch flag.
- Log out before wiping or selling a phone. A clean logout invalidates the stored token on the server side. Factory reset alone does not always clear Keychain items tied to a backup.
- Keep one device per account. Account-sharing rules sit in Supabet casino terms. A session appearing on a second handset from a different province or IP range reads as sharing, even when it is a backup restore.
- Resolve flags with documents, not retries. When the cashier freezes a withdrawal, submit the requested KYC documents through support and reference the device change. Identity verification is a Curacao eGaming licensing requirement before payout, not an operator whim.
- Escalate only after support. Dispute recourse runs through the Curacao regulator in Willemstad, and complaints generally need a support ticket trail first.
| Option | What it does | Trade-off |
|---|---|---|
| Full device restore (Android or iOS) | Copies app data, including a stored session token, to a new phone | Fast setup, but likely triggers a verification flag and a cashier hold |
| Fresh install plus manual login | No token migration; credentials re-entered on the new device | Extra two minutes, no mismatch risk |
| Selective backup exclusion | Keeps the app out of Google backup or the iCloud snapshot | Requires changing settings before the old phone is retired |
| Logout then factory reset | Server-side token invalidation plus local wipe | The only clean handover if the phone is sold or given away |
Two Canadian specifics. Supabet Casino is not part of the Ontario regulated market, so players in Ontario sit outside the provincial framework and rely on the Curacao licence for recourse. And a CAD account supports Interac deposits and withdrawals without conversion, which means a frozen cashier is a cash problem, not a currency one. Supabet Casino accepts CAD, USD and EUR, and has accepted Canadian sign-ups since 2021, so support has handled backup-restore flags before. Say “restored to a new phone” in the first message and skip three rounds of scripted replies.
Before you install the Supabet app on a new phone, decide what you want to carry over. If you are upgrading hardware, sign out of the app on the old device first, then install fresh and log in with your credentials. That single step avoids the most common trigger for an identity-verification flag: a session token that arrives on new hardware through a Google or iCloud restore while the old device is still active. On Android, check Settings > Google > Backup and confirm whether app data is included; on iOS, review Settings > [your name] > iCloud > Manage Account Storage > Backups and the per-app toggles. Where the option exists, exclude the casino app from device backups. A CAD account supports Interac deposits and withdrawals without conversion, so there is no reason to route account recovery through a backup file when the cashier and the support desk can handle it directly.
Keep a short record you can hand to support if a flag appears: the date you changed devices, the last four digits of the card or bank account used for your last Interac transaction, and the approximate time of your last login. Supabet Casino sets ceilings and wagering multiples through its own operator terms, and the identity checks attached to those terms are the same ones that resolve a mismatch, so responding quickly and with accurate details shortens the hold. Remember where recourse sits if a dispute drags: Supabet Entertainment Ltd holds the Curacao eGaming licence 8048/JAZ, and complaints that cannot be settled with the operator run through the Willemstad regulator. Players in Ontario should note that Supabet Casino is not part of the regulated provincial market, which means provincial consumer protections do not apply and the Curacao framework is your only formal channel. Read Supabet casino review coverage with that in mind: any review that praises security without mentioning device backup behaviour, KYC document handling or withdrawal limits is describing marketing, not mechanics. Treat your phone backup as part of your account security, not as an afterthought, and the restore process stops being a risk and becomes a routine five-minute task.