AndroidiOS

Where Does the Lime App Store Data?

Lime keeps rides in private local storage on Android and iOS under a limebike package ID with server sync.

Last updated

Scooter sharing Lime runs a limebike package on Android with a matching iOS build. Private storage on each system holds the login session plus a small ride cache. The cache keeps recent map tiles handy. It does not hold the booking itself.

Vehicles unlock through server bookings, not through local files. The iOS bundle is unverified, so quote App Store ID 1199780189 to support when asked. End rides before device switches to keep billing clean. Server state rules billing while the local view can still lag behind.

Where Lime stores this, by platform

Android
/data/data/com.limebike

Private session and ride cache for the verified limebike package. End open rides before switching phones.

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

GUID container for Lime (App Store ID 1199780189). Bundle unverified; quote the numeric ID.

Frequently asked questions

Do Lime rides transfer phones?

Log into the same Lime account on the new phone. Rides sync from servers, so the ride list returns after login. Local data on the old phone holds only the session and map cache. No file transfer is needed.

How do I avoid Lime double billing?

End open rides in the old app before switching phones. Server state rules billing for Lime vehicles. Confirm the vehicle locked before uninstalling. This keeps the server record clean and avoids extra charges.

Notice an outdated path? Let us know.