Where Does the MyLebara App Store Data?
MyLebara credit lives in private storage under wallet branded IDs that differ per platform. Credit syncs from servers after login.
Last updated
Lebara Germany ships MyLebara under wallet branded Android ID with a mylebara twin on iOS. Private storage holds login session plus prepaid cache. Top ups apply server side. The location matters because the session keeps credit visible. Cached counters build up with use.
iOS adds a per install GUID. Keep login ready before switching phones. Folder copies miss the encrypted session. Same vendor with different product strings from history. Clearing storage while logged in ends the session. Check credit inside the app after relogin.
Where MyLebara stores this, by platform
/data/data/com.lebara.wallet
Private session and credit cache for the verified wallet package. Credit syncs from servers; local holds tokens.
/var/mobile/Containers/Data/Application/<guid>/Documents
GUID container for the iOS twin bundle (App Store ID 1122491914). Note the string differs from Android.
Frequently asked questions
Does Lebara credit survive reinstall?
No. Credit and plans sync from Lebara servers after login. Local data holds session and cached counters. Reinstall and sign back in. Keep login ready. Top ups apply server side.
Why do Lebara IDs differ?
Android uses com.lebara.wallet while iOS uses com.lebara.mylebara. Same vendor, different product strings from app history. Confirm in system app info.
Notice an outdated path? Let us know.