Where Does the Targobank App Store Data?
The Targobank app keeps login session and cached documents in private storage on Android and iOS, with accounts restored after login.
Last updated
Targobank ships platform specific IDs with production flavor strings. Private storage holds login tokens and the document cache on both OSes. Accounts and letters sync from servers after login, so local files hold session state and cached PDFs rather than the account itself. That split decides what survives a wipe. The session keeps you signed in.
iOS paths add a per install GUID, so the container path changes with every install. Keep credentials plus the TAN method ready before switching phones. Manual copies never transfer the session, and clearing storage while the app runs signs you out. Export letters as PDF from inside the app before wiping. Folder copies miss the encrypted stores.
Where Targobank stores this, by platform
/data/data/com.targo_prod.bad
Private session and cache for the verified Android prod package. Accounts sync from servers; local holds tokens and cached docs.
/var/mobile/Containers/Data/Application/<guid>/Documents
GUID container for the iOS release bundle (App Store ID 1441312370). Note the ID differs from Android.
Frequently asked questions
Do Targobank accounts survive reinstall?
No. Accounts and letters sync from Targobank servers after login. Local data holds session and cached PDFs. Reinstall and sign back in, then check the mailbox for letters. Private folder copies do not carry the session to a new phone.
Why do Targobank IDs look so different?
Android uses com.targo_prod.bad while iOS uses ei.targo.release. Same bank, different build strings from separate production builds. Confirm the exact ID in system app info when support asks, since the two look unrelated.
Notice an outdated path? Let us know.