Trust
Editorial policy
This editorial policy explains how Vehicle Plainly researches vehicle topics, writes with source limits, handles corrections, and keeps commercial relationships separate from educational claims.
Editorial mission
Vehicle Plainly publishes cautious, useful guides that improve used-car research literacy. Accuracy, reader safety, and source limits matter more than aggressive claims.
Vehicle Plainly is an independent informational publisher. We explain VIN lookup, vehicle history, title brands, recalls, and used-car research with limits-first language. We are not a government agency, DMV, vehicle history report provider, insurer, lender, dealer, or Consumer Reporting Agency.
Operator and editorial contact
VehiclePlainly is operated by LEGITIME DOMAINS d.o.o., Ulica Stjepana Gradića 1, 10010 Zagreb, Croatia.
Editorial corrections, source questions, and disclosure issues can be sent to contact@vehicleplainly.com.
Topics covered
Editorial coverage focuses on practical used-car research topics:
- VIN research, VIN checks, VIN decoders, and identifier mismatches
- Vehicle history reports, accident and damage context, service records, and report limits
- Title brands, title checks, liens, odometer issues, and seller documents
- Recalls, open recall research, inspection questions, pricing context, and buyer checklists
- Privacy boundaries around license plate research and owner-identification requests
Source hierarchy
When making factual claims, we follow this order:
- Official government or agency sources where relevant, including NHTSA tools and recall materials
- NMVTIS educational and approved-provider context where relevant
- FTC consumer guidance and other verified consumer-protection sources where relevant
- Verified educational guidance tied to allowed claims in the site source registry
- General limits language when a specific claim is not source-backed
- Commercial provider mentions only with independence and without rankings unless methodology is published
Verified source registry
Production guides should rely on verified source entries and keep claims within the scope those sources actually support.
Unverified, unclear, or high-risk sources are not used for public factual claims until separately reviewed.
Government and official sources
Examples include NHTSA VIN decoder and recall lookup tools, NMVTIS educational pages about report indicators, and FTC used-car buying guidance.
We describe what these sources say they provide. We do not imply government endorsement of Vehicle Plainly.
Commercial data providers
Vehicle history reports may include NMVTIS information when obtained through approved providers. We may explain that context without recommending a specific vendor.
Partner links or forms may appear on some pages. They must be disclosed in context and must not change factual claims.
Why we write with limits
Vehicle data is incomplete by nature. Limits-first writing prevents readers from treating a lookup as proof of a clean history, safe condition, or owner identity.
Claim discipline rules
Authors and editors should avoid unsupported certainty.
- Prefer may show, can help explain, and records can be incomplete
- Do not use guarantee, prove, full event-by-event history claims, or every record
- Do not publish owner-identification or private registration access
- Do not claim Vehicle Plainly accesses NMVTIS or DMV directly
- Do not claim a clean title, accident-free history, lien-free status, recall-free status, safe-to-buy conclusion, exact value, or no-inspection-needed result
- Do not provide legal, insurance, lending, tax, appraisal, DMV-specific, or mechanical diagnosis
Safety and privacy boundaries
We do not publish people-search-style content, license plate owner-identification content, or private DMV record access guides.
High-risk topics remain in hold until source packs and safety review support publication.
Content production
Guides may use assisted writing workflows for structure, outline, and consistency, but publication requires editorial review.
Sources must not be fabricated. Unsupported claims are softened, sourced, or removed before publication.
Publication readiness
Some pages may be reviewed privately before public promotion. A page should not be presented to readers as ready until its source limits, safety language, related links, and disclosures have been checked.
Editorial copy updates do not by themselves change technical publication controls.
Human and automated QA
Automated checks look for unsupported phrases, missing safety boundaries, broken related links, and source-limit drift.
QA findings are fixed with focused edits when the base guide is already sound.
Internal linking policy
Guides link to related pages in the same cluster and to trust pages where boundaries need reinforcement.
We do not link to owner-identification pages, unpublished high-risk pages, or comparison/review pages without a published methodology.
Corrections policy
Report corrections to contact@vehicleplainly.com with the page URL, the specific claim or passage, the issue you found, and any source that supports the correction.
Source-limit and safety corrections receive priority, especially if a page could imply owner lookup, official database access, complete history, clean-title certainty, or professional advice.
Typographic fixes, clarity edits, source updates, and substantive claim corrections may be handled on different timelines. We do not promise to accept every requested change.
Update policy
Guides should be reviewed when important source context, vehicle research practices, or safety boundaries change.
Substantive source or claim changes trigger a review pass and may update the visible update information for the page.
Affiliate and commercial independence
Editorial content is independent from commercial relationships. Partner links and forms require disclosure and must not imply official endorsement, owner lookup, DMV access, complete-history certainty, or provider ranking without a published methodology.
When sources are missing
If a topic lacks verified sources, it stays unpublished rather than publishing unsupported claims.
We soften or remove claims rather than invent facts.
Frequently asked questions
- Does Vehicle Plainly use AI to write guides?
- Guides may use assisted writing or structure workflows, but publication requires editorial review, source checks, and automated verification. Unsupported claims are removed, softened, or sourced before publication.
- Can I request a new topic?
- You may send suggestions through contact. We prioritize topics with verified sources and clear reader utility within our risk taxonomy.
- How do you handle conflicting sources?
- We describe the conflict, cite the verified source scope, and avoid false certainty. Readers are directed to official channels for binding decisions.
