Where Does the Audibene App Store Data?
Audibene keeps appointments and hearing data in private storage on Android and iOS under one shared ID.
Last updated
Hearing care Audibene runs one shared rta package on both mobile OSes. Private storage holds login session plus appointment cache for booked visits. The rta string marks the retail appointment flow used by the app. Store bookings reference the same account as online scheduling tied to that login.
Hearing profiles live server side with the account. Local data is session plus test data from prior checks. Fresh login restores everything after reinstall without manual moves. Store bookings re sync with the account after sign in.
Where Audibene stores this, by platform
/data/data/com.audibene.rta
Private session and appointment cache for the shared rta package. Profiles sync from Audibene servers.
/var/mobile/Containers/Data/Application/<guid>/Documents
GUID container for the same bundle (App Store ID 1489152944). Re login restores profiles.
Frequently asked questions
Do Audibene appointments transfer phones?
Log into the same Audibene account on the new phone. Appointments sync from servers tied to that account. Local data holds session and test result cache for prior checks. No manual move is needed once the same login is used.
How do I clear Audibene cache?
Clear cache from system settings for stale data. Full storage clear logs you out and drops the appointment cache. Hearing profiles return after login without extra steps.
Notice an outdated path? Let us know.