Where Does the ALDI TALK App Store Data?
ALDI TALK keeps login session and cached account state in private storage under its E-Plus platform IDs, with balances restored after login.
Last updated
ALDI TALK runs on the E-Plus platform with long client IDs per OS. Private databases hold the login session plus account cache. Balances recompute from servers, so local files hold cached overviews rather than the balance itself. That split decides what survives a reinstall. The platform strings look odd but are verbatim from the store listings.
iOS adds a per install GUID, so the container path changes with every install. Keep login credentials ready before switching phones. Folder copies miss the encrypted session and never transfer login. Sign back in on the new phone and check balance and packages inside the app.
Where ALDI TALK stores this, by platform
/data/data/de.eplus.mappecc.client.android.alditalk
Private session and account cache for the verified Android client ID. Balances sync from servers; local holds tokens and cached packages.
/var/mobile/Containers/Data/Application/<guid>/Documents
GUID container for the iOS twin bundle (App Store ID 423979998). Note the suffix differs from Android.
Frequently asked questions
Do ALDI TALK balances survive reinstall?
No. Balance, packages and bills sync from ALDI TALK servers after login. Local data holds session and cached overviews. Reinstall and sign back in, then check balance and packages inside the app. Folder copies do not carry the session.
Why do ALDI TALK IDs differ by platform?
Android uses de.eplus.mappecc.client.android.alditalk while iOS uses the ios.alditalk twin. Same E-Plus platform, different suffix per OS. Confirm in system app info.
Notice an outdated path? Let us know.