Vin Check
Privacy Policy
Effective and last updated: October 7, 2026
Developer and scope
Vin Check is developed by AppsDev. This policy describes the current app, which uses online vehicle-data services and stores lookup history locally. Unlike an offline reference app, VIN lookup sends information to external providers. A VIN can identify a particular vehicle and may be personal information when linked to a person.
VIN lookups and external providers
When you request decoding, your VIN is sent to the configured HTTPS decoding service. If that request fails, the app sends the VIN to the NHTSA vPIC API at vpic.nhtsa.dot.gov for basic decoding. Additional configured services can receive the VIN, make, model, and year, depending on the request. Legacy endpoints use dev.kz; additional services are currently unavailable. Providers receive normal network request information such as IP address and may log requests under their own policies. Do not enter identifiers you are not authorized to use.
Firebase and remote content
The app uses Firebase Core and Realtime Database to read service configuration, the vehicle catalog, and technical specifications. Reads may disclose network and SDK connection information to Google/Firebase. The current implementation does not write VIN history, credit balances, or device records to Firebase. It enables local database persistence and caches configuration on the device. Catalog photographs may be fetched from the content URLs supplied by the service.
Local storage and deletion
Local UserDefaults contain decoded vehicle history, the last entered VIN, cached catalog configuration, and a purchase ledger containing credit balance, unlocked VINs, and delivered transaction identifiers. You can delete saved vehicle entries from history; deleting an entry does not necessarily remove the separately stored last VIN, catalog cache, or purchase ledger. Removing the app’s local data removes local records, but iOS backups may retain copies under your backup settings. AppsDev does not provide cloud recovery or cross-device synchronization of consumable balances.
Camera, clipboard, and sharing
Camera permission is requested when you open the VIN barcode scanner. Camera frames are used on the device to recognize barcodes; the scanner does not upload or save those frames. A recognized VIN is submitted for decoding. Clipboard access happens when you explicitly use Paste, not through automatic background reading. If you share vehicle details, your selected destination receives the exported content, which may include the VIN.
Purchases
The app includes StoreKit 2 purchase handling, but products are not yet configured for release. If purchases become available, Apple processes payment and supplies verified transaction and entitlement information to the app. AppsDev does not receive your payment card details through the app. Credit and transaction records are currently stored locally. Apple’s terms and privacy policy govern App Store transactions.
Analytics, support, and security
The current app does not include advertising SDKs, Firebase Analytics, AppMetrica, third-party crash reporting, or push messaging. This does not mean external services receive no network data. Connections use HTTPS and normal certificate validation. If you email support or use the AppsDev website contact form, we receive the information you choose to send; the form uses FormSubmit for delivery. Avoid sending sensitive vehicle or ownership documents.
Changes and contact
Service configuration and release behavior may change. This policy must be updated when providers or processing change. For questions or requests concerning information sent directly to AppsDev, contact dev.play.apps@gmail.com. Requests about provider-held lookup records may also require contacting the relevant provider.