Used to decode and build the report
A VIN may be sent to RecallSight’s Worker and NHTSA vPIC. VIN-backed API responses use no-store caching instructions.
Privacy by design
Your VIN is for the report—not for a public profile.
RecallSight is designed so the core vehicle search and My Garage features work without an account.
VIN removed from public URLGarage stored in your browserNo account required
Saved locally on your device
The full VIN is saved only when you explicitly save a VIN-backed vehicle. The interface masks it by default.
Aggregate feature usage
Custom analytics can include year/make/model context but are designed not to send the full VIN as an event parameter.
VIN flow
What happens when you search
- 1You enter a VINThe homepage hands it to the report without intentionally leaving it in the public URL.
- 2NHTSA vPIC decodes itManufacturer-reported year/make/model and configuration fields can personalize the report.
- 3RecallSight builds public evidenceThe server-side D1 evidence index stores year/make/model context—not your full VIN.
- 4You decide whether to save itMy Garage stores the VIN locally in that browser only after an explicit save.
Public data & third parties
Government data requests
RecallSight requests relevant public information from services such as NHTSA, U.S. DOT, EPA/DOE, Transport Canada and CPSC. Those services operate under their own privacy practices.
RecallSight uses Google Analytics to understand aggregate site and feature usage. If future alerts or accounts collect contact information, this policy should be updated before those features collect it.