Where Does the comdirect App Store Data?
The comdirect bank app keeps banking session and photoTAN bindings in private storage on Android and iOS, tied to each device.
Last updated
The comdirect app runs under de.comdirect.app on Android with the usual private databases and prefs. Banking sessions and TAN bindings live there and resist simple file copies. The bindings stay device bound by design, so a folder copy never moves them. Plan reactivation as a new device after any reinstall or restore.
iOS uses a GUID container under the de.comdirect.App bundle. The capital A matters when searching support docs. Treat any reinstall as a new device for TAN purposes and plan reactivation time. Export statements as PDF from inside the app before wiping, since manual copies miss encrypted data and break the binding. Re register through the web portal with an existing TAN method.
Where comdirect stores this, by platform
/data/data/de.comdirect.app
Private databases and prefs for the verified comdirect package. TAN bindings are device bound; copying the folder does not transfer them.
/var/mobile/Containers/Data/Application/<guid>/Documents
Sandboxed GUID container for bundle de.comdirect.App. Access via backup; GUID changes per install. Re register photoTAN after restore.
Frequently asked questions
Why does comdirect ask to reactivate photoTAN after reinstall?
Yes if you cleared storage or switched phones. PhotoTAN bindings are device bound by design. Re register the device in the comdirect web portal and approve it with your existing TAN method.
How do I back up comdirect statements?
Export statements as PDF from inside the app before wiping. Manual folder copies miss the encrypted databases and break the TAN binding. The export stays readable without the app.
Notice an outdated path? Let us know.