Audit a multi-vehicle household one vehicle at a time. For each car, list the legal or primary owner, approved drivers, physical keys, digital keys, manufacturer-app users, insurance or service accounts, and any connected-home integrations. Then compare that list with the access actually shown in the vehicle and provider apps.
Build a separate record for each vehicle
Use one row per access path, not one row per person. A household member may have a key fob, an app invitation, a digital wallet key, and a saved driver profile for the same car. Record the person, access type, device or account, date granted, reason, and person authorized to revoke it. Mark lost, spare, valet, and service keys explicitly. Do not put key codes, passwords, or recovery secrets in the register.
Check ownership separately from driver access. Tesla explains that adding a driver is not the same as transferring ownership. Its support page says an added driver can use most vehicle-app features, including vehicle access, service scheduling and history, roadside assistance, and vehicle location, while some owner functions remain unavailable. The Tesla app also provides a Manage Drivers path for removing access.
Review digital keys on both phone and vehicle
Android's digital car-key guidance allows supported users to share a key with a trusted contact and, on some vehicles, configure restrictions. Google also notes that removing a shared key can take time and that some vehicles do not complete removal until another physical or digital key is used. Check the wallet, the manufacturer's app, and the vehicle's own key list; a removal request on one screen is not proof that the car has enforced it.
For a lost phone, follow the platform and vehicle maker's specific process. Google's setup guidance says a supported Android key may be suspended or erased remotely when the phone is on and connected, but vehicle behavior varies. Keep a physical key and the manufacturer's recovery instructions available before changing digital access.
Compare access with household roles
Decide what each person needs for each vehicle: routine driving, emergency use, location visibility, service scheduling, charging records, or administrative control. A person who occasionally drives a car may not need continuous location access or permission to manage other drivers. A teen or guest may need a restricted key where the vehicle supports one. Document limitations when the platform offers a broad bundle instead of fine-grained controls.
Also review accounts around the car: tolling, charging, roadside assistance, maintenance records, insurance telematics, and smart-garage links. Removing an app driver does not automatically remove a saved garage code, a physical key, or access to a separate charging account. Treat each service as its own access boundary.
Revoke, verify, and preserve recovery
Remove stale access one path at a time. Confirm the change in the owner's app and the vehicle display, then test with the removed device only when it is safe and lawful to do so. Never strand a driver or disable the only working key as an audit test. If revocation is pending, record that state and recheck after the provider's required condition is met.
Repeat the audit after a phone replacement, household move, breakup, driver change, lost key, vehicle sale, or service-provider change. Before selling or transferring a phone or vehicle, Google advises deleting associated digital car keys, and a new owner should confirm that the prior owner no longer has a key. A complete audit ends with verified current access and a clear recovery route for every vehicle.
Sources
- How to Add or Remove Drivers — Tesla
- Share a digital car key — Google
- Digital car key data sharing and safety overview — Google
- Set up or manage a digital car key — Google