Where Does the 1822direkt App Store Data?
The 1822direkt banking app keeps login session and photoTAN state in private storage on Android and iOS.
Last updated
The Frankfurter Sparkasse direct bank runs one shared ID on both mobile OSes under de.direkt1822.banking. Databases and prefs sit in private storage. That storage holds login session plus photoTAN binding. It is the reason the path matters for restores. Copies of the folder cannot carry the binding to another install.
iOS containers add a per install GUID. Treat every reinstall as a new device for TAN purposes. Keep a second TAN method ready before wiping the old phone. Re register inside online banking and approve with the existing method. Exports from inside the app stay readable when the local store is gone.
Where 1822direkt stores this, by platform
/data/data/de.direkt1822.banking
Private databases and prefs for the verified 1822direkt package. TAN binding is device bound; copying never transfers it.
/var/mobile/Containers/Data/Application/<guid>/Documents
GUID container for the same bundle (App Store ID 1124909265). Re register photoTAN after restore.
Frequently asked questions
Why must I reactivate photoTAN after reinstall?
Yes. TAN bindings are device bound by design. Re register the device in 1822direkt online banking and approve with your existing method. Folder copies never transfer the binding.
How do I back up 1822direkt statements?
Export statements as PDF from inside the app first. Manual data copies miss encrypted databases. The export stays readable without the app. Do the export before wiping and keep the PDFs outside the app so a reinstall cannot touch them.
Notice an outdated path? Let us know.