Where Does the Jameda App Store Data?
Jameda keeps appointments and doctor data in private storage on Android and iOS under one short app ID.
Last updated
Doctor portal Jameda runs one short package on Android with a matching iOS build. Private storage holds login session plus appointment cache. The terse ID is easy to mistype, so copy it whole from system app info.
Bookings live server side with confirmations as backup. iOS bundle unverified, so quote App Store ID 1635293480 to support. Fresh login restores appointments after reinstall. Doctor ratings recompute server side regardless of local files. Session holds login plus appointment cache after login.
Where Jameda stores this, by platform
/data/data/de.jameda
Private session and appointment cache for the verified Jameda package. Bookings sync from Jameda servers.
/var/mobile/Containers/Data/Application/<guid>/Documents
GUID container for Jameda (App Store ID 1635293480). Bundle unverified; quote the numeric ID.
Frequently asked questions
Do Jameda appointments transfer phones?
Log into the same Jameda account on the new phone. Appointments sync from servers. Local data holds session and doctor photo cache. History returns after login without extra steps.
How do I clear Jameda cache?
Clear cache from system settings for stale doctor photos. Full storage clear logs you out and drops the appointment cache. Bookings return after login without extra steps.
Notice an outdated path? Let us know.