Is my VIN shared with ClearVIN?
Yes: the VIN goes to ClearVIN for the history preview the check page requests automatically, and for a purchased report. The identity decode uses other sources.
Check the review date and linked sources for context. Live availability, prices and record coverage can vary by VIN, source, jurisdiction and time.
Yes, for the history side. The privacy policy states that when you request a ClearVIN preview or purchase a ClearVIN vehicle history report, the submitted VIN is sent to ClearVIN so it can locate available vehicle information and generate the report. The free identity decode is a different request, answered by the vehicle-identity sources with NHTSA's vPIC among them — but the check page asks for the ClearVIN preview automatically once that decode returns, so a free check does send the VIN to ClearVIN while the preview is active.
- The check page requests the ClearVIN history preview automatically once the decode returns, so a free check does send the VIN to ClearVIN while that preview is active.
- The free 17-character identity decode is answered by the identity providers, including NHTSA vPIC.
- Your VIN is stored encrypted on our side, and the order screen after payment shows only the last six characters — the free check result and the order review page still show all 17.
Which request goes where
Two different endpoints sit behind the free check page. The identity decode asks our vehicle-identity providers — the response names NHTSA vPIC as a source — and returns year, make, model and factory attributes. The history preview the check page requests automatically calls ClearVIN with the VIN as a query parameter, which is why the privacy policy names that exact moment: requesting a preview or buying a report sends the submitted VIN to ClearVIN.
The policy also describes what may be kept afterwards: the ClearVIN report identifier, fulfillment status, the original report file, integrity information and report-access activity, retained for secure delivery, customer support, billing disputes, fraud prevention and contractual recordkeeping.
What is not sent, and what we keep
Full payment-card details are not part of this. The policy says payment details are handled by the payment provider and that full card numbers do not need to reach us, and the ClearVIN section repeats that card details stay with the payment provider. More broadly, the policy commits to sharing the minimum necessary information with payment, authentication, hosting, database, email, analytics, fraud-prevention and vehicle-data providers, which may process it in another country under their contractual and legal safeguards.
On our side, the VIN is stored encrypted and the order API returns only a masked form — six bullets plus the last six characters — so your full VIN is not printed back on the order screen.
What this does not cover
- Once the VIN reaches ClearVIN, ClearVIN's own terms and retention govern it; our policy does not state their retention period.
- Providers may process information in another country under their applicable contractual and legal safeguards.
- The policy describes the categories retained, not a per-record deletion schedule.
Sources reviewed
Open the underlying public source and verify that its scope matches the question you are asking.
Frequently asked questions
Does the free VIN decode send my VIN to ClearVIN?
Yes, while the preview is active. The identity decode endpoint goes to the vehicle-identity providers, with NHTSA vPIC named as a source in the response — but the check page requests the ClearVIN history preview for the same VIN as soon as the decode returns, so running a free check does send the VIN to ClearVIN. Buying a report sends it too.
Does ClearVIN receive my name or card number?
The policy says payment details are handled by the payment provider and full card details remain there. The ClearVIN section describes the submitted VIN being sent so the provider can locate vehicle information and generate the report.
Does the report tell ClearVIN who is searching the car?
The published policy does not state that a searcher identity is sent, so we do not claim it either way. What it does state is that the submitted VIN is sent so the provider can locate available vehicle information.