Where Does the congstar App Store Data?
The congstar app keeps login session and cached contracts in private storage on Android and iOS, with details restored after login.
Last updated
Telekom brand congstar runs one app ID on both mobile OSes. Private databases hold the login session plus contract cache. Usage figures recompute from servers, so local files hold cached overviews rather than the contract itself. That split decides what survives a reinstall. The session is what keeps you signed in.
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. Clear cache from system app settings for stale consumption bars. Bills stay in the mailbox after relogin.
Where congstar stores this, by platform
/data/data/de.congstar.meincongstar
Private session and contract cache for the verified congstar package. Contracts sync from servers; local holds tokens and cached bills.
/var/mobile/Containers/Data/Application/<guid>/Documents
GUID container for the same bundle (App Store ID 917314686). Re login restores contracts.
Frequently asked questions
Do congstar contracts survive reinstall?
No. Contracts, bills and data usage sync from congstar servers after login. Local data holds session and cached overviews. Reinstall and sign back in.
How do I fix stale congstar consumption?
Clear cache from system app settings for stale consumption bars. Full storage clear logs you out. Bills stay in the mailbox after relogin. Check consumption inside the app after clearing cache, and sign back in when a full clear drops the session.
Notice an outdated path? Let us know.