Where Does the IONITY App Store Data?
IONITY keeps charging session and station map cache in private storage on Android and iOS under vendor coded IDs.
Last updated
IONITY is a charging network with vendor coded IDs per platform. Private storage holds the login session on the device. It also holds session cache and station maps for daily use. The cache supports station use between server contacts. The store stays private to the app and holds session data.
Sessions and invoices live server side with the account. Local data is session plus station maps. The two platforms do not share local data. Each install reads only its own area. A fresh login restores everything after reinstall regardless of platform. The account holds the sessions.
Where IONITY stores this, by platform
/data/data/com.cleevio.ionity.android.app
Private session and charging cache for the verified cleevio package. Sessions sync from IONITY servers.
/var/mobile/Containers/Data/Application/<guid>/Documents
GUID container for the cz bundle (App Store ID 1551448692). Note the ID differs entirely from Android.
Frequently asked questions
Do IONITY sessions transfer phones?
Log into the same IONITY account on the new phone. Sessions sync from servers to the account. Local data still holds session and station cache. That local part does not move by itself. A fresh login restores the account on the new device.
Why do IONITY IDs look so odd?
Android uses a com.cleevio.ionity vendor string while iOS uses cz.Ionity.app. It is the same network with unrelated strings from platform history. The strings name the same network on both sides. Confirm the exact string in system app info for the device.
Notice an outdated path? Let us know.