AndroidiOS

Where Does the Flinkster App Store Data?

DB Flinkster keeps rentals in private storage on Android and iOS under one sharing package with server sync.

Last updated

Deutsche Bahn car sharing Flinkster runs one sharing package on Android with a matching iOS build. Private storage on each system holds the login session plus a small rental cache. The cache keeps recent station lists handy. It does not replace the server record.

Bookings live server side and unlock station cars through the booking itself, not through local files. The iOS bundle is unverified, so quote App Store ID 6639612291 to support when asked. A fresh login restores rentals after reinstall. Clearing local data removes the session but leaves server bookings intact.

Where Flinkster stores this, by platform

Android
/data/data/de.flinkster.sharing.app

Private session and rental cache for the verified sharing package. Rentals sync from Flinkster servers.

iOS
/var/mobile/Containers/Data/Application/<guid>/Documents

GUID container for DB Flinkster (App Store ID 6639612291). Bundle unverified; quote the numeric ID.

Frequently asked questions

Do Flinkster rentals transfer phones?

Log into the same Flinkster account on the new phone. Rentals sync from Flinkster servers, so the booking list returns after login. Local data on the old phone holds only the session and station cache. No transfer of files is needed.

How do I clear Flinkster cache?

Clear cache from system settings if station data looks stale. This keeps the login in place. A full storage clear logs you out and wipes the session and cache. Bookings return after login because they live on Flinkster servers.

Notice an outdated path? Let us know.