Where Does the Barclays easybank App Store Data?
The former Barclays app, now easybank, keeps session in private storage under legacy package IDs. Accounts sync from servers after login.
Last updated
Barclays Deutschland became easybank with the app ID staying put. Android runs the barclaycard string, iOS a de.co.barclays bundle. Private storage holds login session plus document cache. The location matters because tokens keep accounts visible. Cached documents build up with use.
Renames confuse store searches that expect easybank in the ID. Use the legacy strings on device. Accounts sync from servers after login regardless of branding. Do not install a second copy. Clearing storage while logged in ends the session. Check accounts inside the app after relogin.
Where easybank Deutschland stores this, by platform
/data/data/com.barclaycard.germany
Private session and cache for the legacy Android package, now easybank branded. Accounts sync from servers; local holds tokens.
/var/mobile/Containers/Data/Application/<guid>/Documents
GUID container for the iOS bundle (App Store ID 868737672). Same rename history; re login restores accounts.
Frequently asked questions
What happened to the Barclays Germany app?
Update to the easybank build and log in with existing credentials. Accounts sync from servers. The legacy com.barclaycard.germany package updates in place; do not install a second copy.
Why do the package IDs still say Barclaycard?
Android kept com.barclaycard.germany while iOS uses de.co.barclays.barclaycardgermany. Same bank after the easybank rename, different strings per platform from history.
Notice an outdated path? Let us know.