What Data Do You Lose With an Install-Over Update? Does KYC or Order History Survive?
Installing over the Binance app with a new APK, dmg, or exe basically doesn't lose any data — your account info, KYC status, order history, and asset balances all carry over. This article lists exactly which data survives an install-over update and which resets, compares install-over versus uninstall-and-reinstall, and explains the boundary between server-side data and local data.
The most common way to update the Binance app is to download the new version's APK or dmg/exe and install it directly over the old one. This "install-over" approach almost never loses any important data. Specifically: account information, KYC verification status, order history, asset balances, your bound 2FA, favorited trading pairs, and device trust records are all retained; only a small amount of purely local cache data (like custom chart layouts or temporary download files) might get reset during a major version update. If you're on the Binance Official Site getting ready to download the new APK and install it over your current version, it's important to understand the line between "server-side data" and "local data."
The reason install-over updates are this reliable comes down to the fact that all of Binance's core data lives on cloud servers — the app itself is just a client shell. Let's go through it by data type.
Server-Side Data vs. Local Data
To understand what an install-over update actually affects, you first need to distinguish between two categories of data.
| Data Category | Storage Location | Install-Over Impact | Uninstall-and-Reinstall Impact |
|---|---|---|---|
| Server-side data | Binance servers | Fully retained | Fully retained |
| Local cache | Device storage | Mostly retained | Fully wiped |
| System-level credentials | iOS Keychain / Android Keystore | Retained | May or may not be retained |
| Config preferences | App's internal database | Retained | Wiped |
Server-side data is the core: your account, KYC, assets, orders, futures positions, trade history, referral relationships, and more. This data is tied to your Binance account, not stored locally — as long as you can log into the account, the data is there.
Local data is auxiliary: login state, UI preferences, cached market charts, dark mode toggle, and so on. Install-over updates mostly keep this data; uninstall-and-reinstall loses it.
Exactly What an Install-Over Update Retains
Step 1: Account and Identity Information
Everything at the account level is fully retained after an install-over update.
| Item | Status After Install-Over |
|---|---|
| Bound email / phone number | Retained |
| Login password | Retained (server-side) |
| 2FA binding (Google Authenticator) | Retained |
| Device trust record | Retained |
| Anti-phishing code | Retained |
| Withdrawal address whitelist | Retained |
| API key list | Retained |
After updating, you typically won't need to log in again — the app opens straight to your "Profile" page. In rare cases, security policy may require you to re-enter your 2FA code.
Step 2: KYC Identity Verification
This is what most people worry about most: will updating force you to redo your identity verification? The answer is almost certainly not.
Your KYC data lives in Binance's server-side compliance database, completely decoupled from the app version. Even if you jump from v2.50 to v2.84, migrate from one phone to another, or switch from Android to iOS, your KYC status follows your account.
Specifically retained:
- Your approved verification tier (Basic / Advanced)
- Uploaded ID card / passport photos
- Facial recognition records
- Proof of address
- Withdrawal and futures permissions
For more detail, see How Binance Updates Relate to KYC (if that article exists).
Step 3: Trading and Asset Data
| Item | Status After Install-Over |
|---|---|
| Spot assets | Retained (server-side) |
| Futures positions | Retained (server-side) |
| Margin borrowing | Retained (server-side) |
| Flexible / fixed savings | Retained (server-side) |
| Order history | Retained (server-side) |
| Trade history | Retained (server-side) |
| Deposit and withdrawal history | Retained (server-side) |
| C2C trade history | Retained (server-side) |
All of your asset-related numbers live on the server — the app is only a display window. No matter how you update, uninstall, or switch devices, the balance you see after logging in is the real one.
Step 4: UI Preferences and Local Configuration
This is the only area where an install-over update might introduce a small change.
| Item | Status After Install-Over |
|---|---|
| Dark / light theme | Usually retained |
| Language setting | Usually retained |
| Default trading pair | Usually retained |
| Favorited trading pairs list | Retained (tied to your account, stored server-side) |
| Custom chart indicators | May reset with a major version update |
| Custom keyboard shortcuts (desktop) | May reset with a major version update |
| Font size | Retained |
Custom chart indicators and desktop keyboard shortcuts are the two items that occasionally get reset to their defaults during a cross-major-version update (like 2.x → 3.x), because a new version may change the storage format.
Step 5: Local Cache and Temporary Files
| Item | Status After Install-Over |
|---|---|
| Market chart cache | Likely retained, refreshed by the new version |
| Avatar cache | Retained |
| Offline announcements | May reset |
| Debug logs | Usually cleared |
These are temporary files the app manages internally. During an install-over update, the new version may choose to keep or clear them — the impact on users is minimal either way.
The Difference With Uninstall-and-Reinstall
If instead of installing over the old version you uninstall first and then install the new version, the difference mainly shows up in the "local data" category.
| Item | Install-Over | Uninstall and Reinstall |
|---|---|---|
| Account, KYC, assets | Retained | Retained (server-side data) |
| Login state | Retained | Needs to log in again |
| 2FA binding | Retained | Retained (server-side) |
| Device trust | Retained | Needs to be re-trusted |
| Theme, language | Retained | Reset to default |
| Custom chart settings | Likely retained | Completely lost |
| Push permissions | Retained | Needs to be re-granted |
| Anti-phishing code | Retained | Retained (server-side) |
Bottom line: even uninstall-and-reinstall won't lose your account and assets — you'll only lose local UI preferences and your login state. So when the app misbehaves, "uninstall and reinstall" is a safe fallback.
Data Retention When Migrating Across Platforms
An even more extreme scenario: moving from Android to iOS, or vice versa.
| Data Type | Cross-Platform Migration Impact |
|---|---|
| Account, KYC, assets | Fully retained |
| Orders, history | Fully retained |
| 2FA | Needs to be re-bound (unless you're using Google Authenticator's cloud sync) |
| Device trust | New device needs to be re-trusted |
| Theme, language | Reset to default |
| Push notifications | Needs to be re-subscribed |
The most important thing during a cross-platform migration is 2FA: before updating or switching devices, it's worth going to "Security" → "Google Authenticator" and screenshotting the secret key/seed string first, so you don't get locked out because a new device can't bind 2FA.
Data Retention Across the 5 Platforms During Install-Over Updates
| Platform | Install-Over Method | Data Retention | Notes |
|---|---|---|---|
| Android | Install the new APK directly | Fully retained | Don't install a mismatched signature — a different signature gets rejected |
| iOS | Automatic App Store update | Fully retained | Automatic mechanism, nothing to worry about |
| macOS | Drag the dmg into Applications to replace it | Fully retained | User data lives at ~/Library/Application Support/Binance |
| Windows | Install the exe package over it | Fully retained | Just install to the original path |
| Web version | No "install-over" needed | N/A | The browser automatically loads the new front end |
Recommendations
Recommendation 1: Confirm Your 2FA Backup Before Updating
Whether you're installing over the old version or doing a full uninstall-and-reinstall, it's best to back up your Google Authenticator secret key ahead of time. If the app fails to recognize your old 2FA binding after an update, and you don't have a backup, you'll have to go through a slow Binance support reset process.
Recommendation 2: Choose "Install-Over," Not "Uninstall Then Install"
As long as the new APK's signature matches the old one (which official packages always do), install-over is the safest option. A manual uninstall will lose your login state, push authorization, and other extra state.
Recommendation 3: Check the Announcement Before a Major Version Update
For a cross-major-version update (like 2.x → 3.x), Binance usually publishes an announcement explaining data compatibility. Take a look so you know what to expect.
Recommendation 4: Do a Full Check After Updating
Once you're in the app, do the following:
- Check that your asset balance looks right
- Scroll through your last 5 trades
- Go to the "Security" page and confirm 2FA is working
- Try a small transfer to confirm withdrawals still work
Only proceed with larger operations once everything checks out.
If you need to switch devices or grab the newest APK, head to the Official Binance App entry to get the latest version, or check the Download Page.
Handling Unexpected Issues
Issue 1: A White Screen After an Install-Over Update
This may be a failed data migration in the new version. To fix it:
- Force-close the app
- Relaunch it
- If that doesn't work, clear the app cache (not the app data)
- As a last resort, uninstall and reinstall
Issue 2: A Prompt Says KYC Is Invalid After Updating
This is rare but can happen. It's because Binance occasionally requires you to supplement KYC information (like updating your address or re-taking a facial photo). Just follow the in-app prompt through — it's not a redo from scratch.
Issue 3: Assets Look "Off" After Updating
This is usually just a cache that hasn't refreshed. Pull down to refresh on the "Profile" page, or log out and log back in. Your asset numbers live on the server and can never truly disappear.
Issue 4: 2FA Codes Keep Failing After Updating
This can be a device time discrepancy. Check that your phone's time zone is set to "automatic" and the time is accurate. Google Authenticator is time-sensitive, so an incorrect time zone will keep causing errors.
FAQ
Q: Will an install-over update make me redo KYC? A: No. KYC data lives on the server and has nothing to do with the app version. In rare cases you may be asked to "supplement a specific piece of information," but that's not a redo.
Q: Will an install-over update make my assets disappear? A: Absolutely not. Assets are server-side data — as long as you can log into your account, your assets are there. If you don't see your balance after logging in, pull down to refresh or log out and back in first; it's almost always a cache issue.
Q: Will switching from an Android APK to iOS lose any data? A: Your account, KYC, assets, and orders won't be lost; what you lose is local UI preferences, device trust, and push authorization.
Q: Will an install-over update invalidate my 2FA? A: No. Your 2FA binding lives on the server and is decoupled from the app itself.
Q: Will client-side logs get wiped by an update? A: Usually, yes — the new version resets them. This doesn't affect normal users, but if you're working with support to troubleshoot an issue, it's best to export your logs before updating.
Q: What does an iOS "uninstall and reinstall" lose? A: Your login state, push authorization, and device trust. Your account and assets are not affected.
Q: Are there any special cases with a cross-major-version update (like v2 → v3)? A: Occasionally you'll see a "migration wizard" asking you to confirm certain settings, but the overall data still carries over. It's a good idea to check the official announcement before updating.
Q: What happens if the APK signature doesn't match? A: Android will refuse the install-over and show a "package signature mismatch" error. This means the package you're installing isn't the official one. Uninstall the old version and reinstall the new official version instead. For more, see Verifying the Binance APK Signature.