Where Does the Sixt App Store Data?
Sixt keeps rentals, session and station cache in private storage under a reservation package on both phones.
Last updated
Car rental Sixt runs platform specific IDs. The reservation flavor covers one platform and the isixt flavor covers the other. Private storage holds the login session plus the rental cache. Session data and cached rentals sit together there, apart from bookings that live server side.
Bookings live server side with receipts. Rentals and receipts sync from servers after login. Local data holds session and station cache only for the account. Fresh login restores everything after reinstall, so the move takes little effort.
Where Sixt stores this, by platform
/data/data/com.sixt.reservation
Private session and rental cache for the verified reservation package. Rentals sync from Sixt servers after login.
/var/mobile/Containers/Data/Application/<guid>/Documents
GUID container for the isixt bundle (App Store ID 295079411). Note the string differs from Android.
Frequently asked questions
Do Sixt rentals transfer phones?
Log into the same Sixt account on the new phone. Rentals and receipts sync from servers. Local data holds session and station cache. Bookings live server side, so fresh login restores everything after reinstall.
Why do Sixt IDs differ?
Android uses com.sixt.reservation while iOS uses com.sixt.isixt. Same vendor, different strings from app history. Confirm in system app info. The reservation and isixt flavors point to the same rental cache and session storage.
Notice an outdated path? Let us know.