Where Does the TheFork App Store Data?
TheFork keeps bookings and restaurant data in private storage under French lafourchette IDs on both phones.
Last updated
Restaurant portal TheFork runs lafourchette platform IDs with per OS prefixes. Private storage holds login session plus booking cache. The French vendor string hides the brand, so device searches for fork miss the folder entirely.
Reservations live server side with confirmation emails as backup. Local data is session plus images. Fresh login restores bookings after reinstall regardless of platform. Yums loyalty points recompute server side and survive any local wipe. Cache holds temporary copies. Server copies stay authoritative. Session data remains private.
Where TheFork stores this, by platform
/data/data/com.lafourchette.lafourchette
Private session and booking cache for the verified lafourchette package. Bookings sync from TheFork servers.
/var/mobile/Containers/Data/Application/<guid>/Documents
GUID container for the c4mprod twin bundle (App Store ID 424850908). Note the prefix differs from Android.
Frequently asked questions
Do TheFork bookings transfer phones?
Log into the same TheFork account on the new phone. Bookings and Yums sync from servers. Local data holds session and restaurant photo cache. Stored files return after login. System settings clear the cache.
Why do TheFork IDs differ?
Android uses com.lafourchette.lafourchette while iOS uses com.c4mprod.lafourchette. Same French platform, different prefix per OS. Confirm in system app info.
Notice an outdated path? Let us know.