Can I trust Kia Access?
This app did not meet two or more trust checks, has a critical issue in one, or has a red flag.
- Avoid if
- Users who prefer vehicle data not logged externally
- What it means for you
- The build includes code to send usage and vehicle data to Firebase Analytics, Dynatrace, and LexisNexis Risk Solutions. The crash reports the code builds for Firebase Crashlytics include vehicle identifiers such as VIN and license plate numbers alongside the full vehicle record. The build includes code to send navigation activity to Google Maps and HERE Maps. SiriusXM integration handles entertainment connectivity.
- Main concern
- Hardcoded Kia production API keys enable unauthorized vehicle command access
- The developer's description
- Kia Access is Kia America's official app. Access vehicle information and services including owner's manual, payment information, maintenance reminders, and connected features like remote lock/unlock, climate control, navigation, and battery status.
- Third-party services
- 14
- Findings rated low or higher
- 13
Open on Google PlayOpens the app's listing on Google Play in a new tab.
Full findings
Open this scan in your dashboardThe account that ran this scan sees every finding and the Rescan button there.
Trust checks
Secure by Design
One criterion not metSecurity gaps detected
Why this result
This check looks for security issues at high severity or above in the code of this build, and at least one was recorded. Issues of this kind include a credential or token another app on the device can reach, sensitive data stored without protection, and network paths that expose information in transit.
Backend credentials are embedded in the app's code, some locally stored data uses a weak encryption configuration, some network connections allow unencrypted traffic, and a debug tool in the production release can disable encryption verification.
Data Minimization
One criterion not metTracking lacks clear disclosure
Why this result
This build contains analytics or attribution code written to send data to companies other than the developer. No consent step was found before that code runs, and the app's disclosures do not describe the collection in full. Tracking by itself is ordinary; what this check reports is the combination of collection, recipient and absent disclosure.
Usage and diagnostic data collection begins automatically at the first app launch, before any privacy notice is displayed or consent is requested.
Manifest Mismatch
One criterion not metDisclosure incomplete or contradicted
Why this result
The check compares the app's privacy disclosures against what the code does, and at least one claim did not match in this build. Mismatches of this kind include a data category collected but not disclosed, a recipient the disclosure omits, and an identifier attached to data the disclosure describes as anonymous.
This build contains code for this item; what that code does at run time was not observed.
User Control
Items recorded, result pending reviewHard to leave
Why this result
The check looks for a way to export the data an account has accumulated and a way to delete the account itself. At least one of the two was not found in this build. Leaving therefore means either abandoning the data or contacting the developer to ask for it.
Driving history and vehicle records are stored on the developer's servers, and no account deletion or data export option was confirmed within the app.
Truly Local
One criterion not metContains code to send personal data off the device
Why this result
This app presents itself as working offline or on the device alone, and this build contains code written to send personal data to servers. The check covers analytics, crash reporting, advertising code and any first-party endpoint the code addresses personal data to. Code of this kind is common; what this check reports is the distance between that code and how the app describes itself.
This build contains code for this item; what that code does at run time was not observed.
Strengths
- Seven SHA-256 certificate pins on the vehicle command API block interception of lock, unlock, and remote start commands even against rogue Certificate Authorities
- ADB backup is disabled, preventing app data extraction via USB from a connected computer
- VIN barcode scanning is processed entirely on the device using Google ML Kit with no data sent to third parties
- No broad-reach advertising SDK ecosystem is present — Adjust, Braze, Amplitude, Kochava, and similar data-broker-linked SDKs are absent
- Vehicle geolocation capture requires explicit opt-in consent with clear disclosure before any data collection begins
- Google Tink cryptography library is in use, providing established cryptographic primitives rather than custom implementations
What the app contains
14 services
Third-party services the scan names in the build:
- Firebase Analytics
- Firebase Crashlytics (crash reporting; crash logs include vehicle identifiers V…
- Firebase Cloud Messaging
- Firebase Performance
- Firebase Remote Config
- Firebase App Check
- Google Maps SDK
- HERE Maps SDK
- Dynatrace APM
- Google Digital Car Key (DCK)
- Google Wear OS
- Google Play Integrity
- LexisNexis Risk Solutions
- SiriusXM
Changes since the previous scan
- Version 7.29.0 (versionCode 10700), score 88.
- Score 78 before, 88 after.
- Score change since version 7.29.0 (versionCode 10700): no change.
- Since the previous scan: 12 findings added, 10 removed.
- Version 7.29.0 (versionCode 10700), score 78.
- Score 81 before, 78 after.
- Version 7.29.0 (versionCode 10700), score 81.
- Score 78 before, 81 after.
- Version 7.29.0 (versionCode 10700), score 78.
- Score 70 before, 78 after.
- Version 7.29.0 (versionCode 10700), score 70.
- Score 77 before, 70 after.
- Version 7.29.0 (versionCode 10700), score 77.
- Score 85 before, 77 after.
- Version 7.29.0 (versionCode 10700), score 85.
- Score 71 before, 85 after.
- Version 7.29.0 (versionCode: 10700) before, 7.29.0 (versionCode 10700) after.
- Version 7.29.0 (versionCode: 10700), score 71.
- First public scan of this app.
Method and limits
Static analysis: the decompiled code, manifest and resources of this build, read file by file. Network traffic at run time is established by a capture of the running app.
- Files decompiled
- 2,055
- Scan date
- 29 July 2026
Corrections
No correction is published for this app.
Developer response
No response is published for this app.
Report an error Opens an email to [email protected] that names this app and this scan.