Car dealer plugin privacy
The credit application parked in the contact-form database
Independent and small-group car dealerships on WordPress can collect a get-pre-approved finance form that receives SSN, DOB, income, employer, and housing payment — a full credit application sitting in a form-plugin table on a marketing site — through general-purpose form, upload, and marketing-tag plugins. Trade-in and test-drive flows can add registration photos and license scans to public uploads. Retained entries and public uploads can keep that identity kit after the lead cools. Unlike a bank, the credit application lands in the same WordPress database as the contact form. This sample reviews three plugins' documentation. Check which finance fields you collect, who can open submissions, where temporary uploads and tags store or send that data, and how long intake rows, files, and backups are kept after the lead.
Documentation review only. This is not financing advice, not a credit decision guide, and not an ECOA, FCRA, GDPR, or other compliance assessment.
Scan your dealer finance page for third-party requestsThe scan checks browser requests on the pages it visits. It cannot inspect form entries, uploaded license scans or registration photos, email inboxes, staff permissions, vendor accounts, or backups.
Where credit-application answers and dealer documents are stored
Files and form entries handled on your WordPress site
Check which SSN, DOB, income, employer, housing-payment, vehicle, trade-in, license-scan, registration-photo, or contact fields you enable, who can open entries, which uploads you accept, where temporary uploads live, which inboxes receive attachments, and how long records, files, and backups are kept after the lead — including deals that never closed. Notification emails can also copy identity and finance answers off-site. A credit application in the contact-form database is the finance office on a marketing site.
Marketing tags on the finance or upload page
Some tools load a marketing pixel or tag on the same page as the get-pre-approved form. A page request can fire before anyone submits an SSN — and can treat in-market auto intent as an audience segment. Review which tags you enable, which consent filters you use, and what those platforms retain. A browser scan cannot inspect stored form entries or uploaded license scans.
Car-dealer finance-intake setups
No paid placement. Site-hosted tools appear first, followed by vendor-hosted tools. Names are alphabetical within each group.
Three plugins reviewed from public documentation. Specialty dealer-management SaaS tools without a WordPress.org listing are outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Drag and Drop Multiple File Upload for Contact Form 7 Documented Contact Form 7 upload extension (plugin version 1.4.0). The free-version listing states uploaded files move to a temporary folder under /wp-content/uploads/wp_dndcf7_uploads, attach to mail, then are removed from that temporary folder after submission — the same pattern Contact Form 7 documents for its default file field. That cleanup does not remove copies already sent as email attachments. Which license scans, registration photos, trade-in sheets, or other dealer documents you accept depends on the fields you add; they are not fixed car-dealer defaults. Filenames chosen by shoppers can include SSNs or plate numbers. Pro documents Media Library storage, custom upload folders, auto-delete timers, and remote storage options. Public form-page browser hosts are unverified. | Uploaded files attached to email; temporary copies under wp-content/uploads | Browser hosts not verified | Not assessed | Not tested |
| |
| Formidable Forms Documented self-hosted form builder (plugin version 6.35). The listing states every form submission is stored in the WordPress database, with back-end entry access, CSV export, and email notifications or autoresponders you configure. SSN, DOB, income, employer, housing-payment, vehicle, trade-in, or contact fields depend on the fields you add — they are not fixed car-dealer defaults. A get-pre-approved form that collects those answers is a credit application parked in the same contact-form database as ordinary lead capture. Optional payment, CRM, or spam-protection integrations send data only when enabled. Retention of entry rows after the lead — including deals that never closed — is not specified as a default purge. Public form browser hosts are unverified. | Finance pre-qualification form entries stored in your WordPress database | Browser hosts not verified | Not assessed | Not tested |
| |
| PixelYourSite – Your smart PIXEL (TAG) & API Manager Documented pixel and tag manager (plugin version 11.4.2.1). When a Meta Pixel ID is saved, version 11.4.2.1 dist/scripts/public.js loads https://connect.facebook.net/en_US/fbevents.js. A noscript image uses https://www.facebook.com/tr. Google Analytics 4, Google Tag Manager, OpenAI Pixel, and Head and Footer scripts load only when you enable them. Automated events include form submissions; those events do not by themselves prove that a credit application was sent. A page request from this script on a get-pre-approved page is not proof that an SSN or income answer was collected — and a pre-consent tag on that finance page can still treat in-market auto intent as an audience segment. The listing describes consent-plugin filters; that is not a legal-compliance assessment. Consent timing has not been tested. Review which tags you enable on finance, trade-in, and document-upload pages. | Marketing tags handled through Meta, Google, or other configured platforms | connect.facebook.net | Not assessed | Not tested |
|
What this table does and does not prove
This is a documentation review, not a test of your site. SSN, DOB, income, employer, housing-payment, vehicle, trade-in, license-scan, or registration-photo fields often depend on the fields you configure. A finance pre-qualification form is not financing advice and is not a credit decision. A marketing-tag page request is not proof an SSN or income answer was collected. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess ECOA, FCRA, financing, GDPR, or other compliance status. Ask your web vendor where entries and uploads live, whether credit-application rows stay off the public web, whether portal links expire, whether unconverted pre-quals purge, whether marketing pixels stay off finance pages, and whether "secure credit application" badges match the storage path you can verify. Review stored records, uploaded files, connected services, exports, notification emails, and backups.
Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.
Related pages
Scan your dealer finance page for third-party requests/wp-car-dealer-plugin-privacy