Where Does the Rivian App Store Keys and Trip Data?
The Rivian app pairs phone as key over Bluetooth and syncs trips plus charging to the Rivian account, caching locally on the phone.
Last updated
Rivian leans on the phone harder than most car apps. Phone as key uses Bluetooth pairing bound to the handset, while trips, charging sessions, and service attach to the Rivian account.
That split decides what survives a switch. Account data returns with a sign in. The key does not, and must be paired again with the truck nearby. Local storage holds session, cache, and key material under the Rivian entry, whose exact package name varies, so match it on device.
Where Rivian stores this, by platform
/storage/emulated/0/Android/data/<Rivian package>
Session, cache, and key material. Browse Android data for the Rivian entry since the exact package varies. Never copy this folder to clone a key; pair fresh in the app instead.
On My iPhone/Rivian
Trips and charging sync through the Rivian account, but phone as key needs re pairing on every new or wiped iPhone. Keep a key card handy until the new key works.
Frequently asked questions
How do I move the Rivian app to a new phone?
Sign in with the same Rivian account, then re pair phone as key from inside the app. Trips and charging history follow the account. The Bluetooth key never transfers by folder copy; pairing is the only path.
Phone as key stopped working after a reset. How do I fix it?
Re pair it in the app with the vehicle nearby and Bluetooth on. Keys bind to the phone hardware, so wipes and new devices always need fresh pairing. Keep a key card as backup during the switch.
Notice an outdated path? Let us know.