TRUST
Trust & Security
The safest data is the data a site never collects. A check asks for a VIN; a purchase adds an email and a payment made on our processor's form. This page covers what we hold, how it is protected, where the vehicle data comes from and the controls you have.
Last updated October 29, 2026 · Questions: contact@vindecode.net
The short answer
- Do you store my card number?
- No. Card details are entered on Stripe's secure form (PCI DSS Level 1) and never reach our servers. We hold the payment confirmation and the last four digits.
- Is the connection encrypted?
- Yes. Every page and every request uses HTTPS, and the site tells browsers to refuse plain HTTP for two years (HSTS).
- How do I report a security issue?
- Email contact@vindecode.net with "Security" in the subject line. We acknowledge every report.
What we collect, and why
| What | Why |
|---|---|
| VIN or license plate | To build the report and to detect abuse |
| Email address | To deliver the report and the receipt |
| Payment confirmation | To match a payment to a report and handle refunds |
| No name, address or phone | Not needed to run a check or buy a report |
| No card number | Handled entirely by Stripe |
How that information is protected
- Data minimization. We collect what the service needs and nothing more.
- Encryption in transit. HTTPS everywhere, HSTS, and security headers that stop the site being framed or sniffed.
- Payments. Stripe, certified PCI DSS Level 1, handles every card; our servers never see a card number. Visa, Mastercard, American Express, Discover, Apple Pay, Google Pay and Link are accepted.
- Infrastructure. The site runs on Vercel and stores order records in Supabase, which encrypts data at rest.
- Access control. Access to stored data is limited to what operating the service requires, behind individual accounts with two-factor authentication.
- Retention. Data is kept for as long as you need access to what you purchased, and as long as tax and accounting law requires. After a deletion request, purchase records are kept with the personal details removed.
- Logging for abuse, not profiling. Lookups are logged to rate-limit scrapers, never to build a profile of you.
Where the vehicle data comes from
Title, brand and odometer records come from state motor vehicle agencies through NMVTIS, supplied by ClearVin LLC, an approved NMVTIS data provider whose service we resell. Safety recalls come from NHTSA. Factory build, specifications and photos are decoded from the VIN against manufacturer data through Auto.dev; European vehicles are covered through Vincario. Accident, salvage, auction and sale records come from auction operators, salvage yards, insurers and marketplaces that report them, with the NICB theft check alongside. Every record in a report names the source that supplied it, and we re-present records unaltered. See the NMVTIS disclaimer.
The controls you have
- Access: email us to ask what we hold about you.
- Deletion: the same address removes your email and lookup history, except order records we must keep by law.
- Unsubscribe: one click in any service email.
- Do Not Sell or Share: a dedicated page, and Global Privacy Control honored automatically.
Reporting a security issue
If you find a vulnerability, email contact@vindecode.net with “Security” in the subject, the URL or component, steps to reproduce and your contact details. We acknowledge within one business day, keep you informed, and credit you if you wish. Please give us reasonable time to fix an issue before publishing it, and do not access other people's data while testing.
Where this information comes from
- PCI Security Standards Council — the card-data standard our payment processor operates under
- FTC: protecting personal information — the data-minimization principles this page follows
- NMVTIS consumer portal (U.S. DOJ) — the federal title system behind the title records