Lemon law plugin privacy
The case form that dates exactly how long you kept driving the car you knew was broken
A lemon-law case evaluation can pair a VIN with a defect timeline. A form can collect the purchase date, the first-failure date, the mileage at each visit, a defect description, loan details, and the names of people who rode in the car. Repair-order PDFs, dealer invoices, and diagnostic printouts can sit in the site uploads folder. Those uploads can name the dealership and the mechanic: third parties who never consented to being evidence. That same timeline also dates how long the owner kept driving after they already knew the car was broken. VIN, purchase-date, first-failure-date, mileage, defect-description, repair-order, loan, family-occupant, dealership-name, mechanic-name, requester-name, and phone fields are configured, not documented defaults. Optional repair-order files go in the site uploads folder. A VIN is a stored identifier, not proof of a defect. A purchase date is a stored date, not proof of lemon-law eligibility. A first-failure date is a stored date, not proof the car was unsafe. A repair order is an upload, not proof of a manufacturer defect. A dealership or mechanic name on a repair order is a stored third-party name, not consent to be evidence. A loan field is a stored number, not proof of a finance contract. A family-occupant field is a stored name, not proof anyone rode in the car. A case form is not proof anyone kept driving a known-broken car. A page request is not proof anyone started a lemon-law case. The page URL can say lemon law even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and uploads, which tags load on case-evaluation pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, a lemon-law-success claim, a buyback or refund claim, a court-procedure claim, a workers-comp claim, a criminal-defense claim, an auto-detailing claim, a CDL or driving-record claim, or a GDPR or other compliance assessment.
Scan your site for third-party requestsThe scan checks browser requests on the pages it visits. It cannot inspect form entries, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.
Where lemon-law case rows, repair-order uploads, and page tags go
Case forms and uploads handled on your WordPress site
Check which VIN, purchase-date, first-failure-date, mileage, defect-description, repair-order, loan, family-occupant, dealership-name, mechanic-name, requester-name, or phone fields you enable, who can open form entries, where uploaded repair orders live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after the evaluation ends. Notification emails can also copy the same VIN, defect timeline, repair-order PDFs, loan details, family-occupant names, and dealership or mechanic names off-site. One table can name a VIN, a first-failure date, and a family occupant next to a loan field, even when no case is filed. Ask your web vendor not to collect a VIN next to a defect timeline and a family-occupant name on the first public form, not to store those repair orders next to dealership names in one open submissions list, and to purge unused case rows after the date passes. A privacy-policy page does not by itself limit who can export a case list or republish an upload. A stored case row is not proof anyone kept driving a known-broken car.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the lemon-law case-evaluation page. That page request can reach a vendor host before anyone submits. The page URL can say lemon law even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off case-intake and upload pages if you do not want that page request. A browser scan cannot inspect stored VIN rows or repair-order PDFs. A "free case review" badge is not a verified storage path.
Lemon-law case-form, upload, and marketing-tag 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 lemon-law case-management software without a WordPress.org listing is 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. That is the same pattern Contact Form 7 documents for its default file field. That cleanup does not remove copies already sent as email attachments. Which repair-order PDFs, dealer invoices, diagnostic printouts, or other case-support files you accept depends on the fields you add; they are not fixed lemon-law defaults. Filenames chosen by visitors can include a VIN, a last name, or a dealership name. A repair order is an upload, not proof of a manufacturer defect. A dealership or mechanic name on a repair order is a stored third-party name, not consent to be evidence. 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 |
| |
| Forminator Forms – Contact Form, Payment Form & Custom Form Builder Documented self-hosted form builder (plugin version 1.58.1). The listing states Forminator stores and organizes submissions so you can sort, analyze, and manage responses, and includes a free file-upload field with multi-file support. Version 1.58.1 helper-fields.php forminator_upload_root() writes under the WordPress uploads directory plus /forminator/, with per-form hashed subfolders from forminator_get_upload_path(). upload.php stores files through that path. VIN, purchase-date, first-failure-date, mileage, defect-description, loan, family-occupant, dealership-name, mechanic-name, requester-name, or phone questions are fields you add; they are not documented defaults. Repair-order PDFs, dealer invoices, and diagnostic printouts are files you accept; those file types are not documented defaults. A VIN is a stored identifier, not proof of a defect. A purchase date is a stored date, not proof of lemon-law eligibility. A first-failure date is a stored date, not proof the car was unsafe. A repair order is an upload, not proof of a manufacturer defect. A dealership or mechanic name on a repair order is a stored third-party name, not consent to be evidence. A loan field is a stored number, not proof of a finance contract. A family-occupant field is a stored name, not proof anyone rode in the car. A case form is not proof anyone kept driving a known-broken car. Notification emails can copy field values and file links off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. How long a case row sits after the evaluation ends is not a documented default of the plugin. | Case-evaluation entries stored in WordPress; file uploads in the site uploads/forminator folder | 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 VIN, first-failure date, or repair-order field was sent. A page request from this script on a lemon-law case-evaluation page is not proof anyone started a lemon-law case, and a pre-consent tag on that page can still treat lemon-law interest as an audience segment from the URL alone. The page URL can say lemon law even when no form is submitted. Consent timing has not been tested. Review which tags you enable on case-intake and document-upload pages. Keep marketing tags off those pages if you do not want that page request. | 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. VIN, purchase-date, first-failure-date, mileage, defect-description, repair-order, loan, family-occupant, dealership-name, mechanic-name, requester-name, or phone fields often depend on the fields you configure. A VIN is a stored identifier, not proof of a defect. A purchase date is a stored date, not proof of lemon-law eligibility. A first-failure date is a stored date, not proof the car was unsafe. A repair order is an upload, not proof of a manufacturer defect. A dealership or mechanic name on a repair order is a stored third-party name, not consent to be evidence. A loan field is a stored number, not proof of a finance contract. A family-occupant field is a stored name, not proof anyone rode in the car. A case form is not proof anyone kept driving a known-broken car. A marketing-tag page request is not proof anyone started a lemon-law case. The page URL can say lemon law even when no form is submitted. The VIN, the defect timeline, and the repair-order PDFs can sit after the evaluation ends. This page is about the case form that dates how long the owner kept driving after they knew the car was broken, not a workers-comp adversary file, not a sealed criminal-defense charge, not an auto-detailing household inventory, and not a CDL driving-record upload. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the case-evaluation page, and how long records and backups are kept. A "free case review" badge is not a verified storage path. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess lemon-law success, buyback, refund, court procedure, workers-comp, criminal defense, auto detailing, CDL, or driving-record claims. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on case pages, and backups.
Documentation snapshot: Oct 15, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress forms privacy
- WordPress file upload plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-lemon-law-plugin-privacy