Towing plugin privacy
The impound release that staples your license to your plate
Towing companies and impound yards on WordPress can collect a release or lookup request that staples a driver's license to a license plate — plate, VIN, driver's license number, phone, and card details for release fees — through general-purpose form, upload, and marketing-tag plugins. Photos of licenses, registrations, and insurance cards land in uploads because “upload proof of ownership” is the standard release flow. A plate-plus-timestamp row is also a location record: it says where a vehicle (and usually its owner) was when it was taken. Visitors often did not choose this vendor and cannot walk away, so the form collects more ID than a bank's. A remarketing pixel on a lookup or dispatch page can fire before consent. This sample reviews three plugins' documentation. Check which identity and vehicle fields you collect, who can open submissions, where temporary uploads and tags store or send that data, and how long release rows, scans, and backups are kept after the vehicle leaves.
Documentation review only. This is not legal advice, not a towing-regulation or lien-law guide, not police-procedure guidance, and not a GDPR or other compliance assessment.
Scan your tow lookup page for third-party requestsThe scan checks browser requests on the pages it visits. It cannot inspect form entries, uploaded license or registration photos, email inboxes, staff permissions, vendor accounts, or backups.
Where license photos, plates, and lookup-page tags are stored
Files and form entries handled on your WordPress site
Check which plate, VIN, driver's license number, phone, card, 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, scans, and backups are kept after the vehicle leaves. Notification emails can also copy release answers off-site. A license number next to a plate in the contact-form database is identity stapled to a vehicle — and a plate-plus-timestamp row is also a location history — on a marketing site.
Marketing tags on the lookup or dispatch page
Some tools load a marketing pixel or tag on the same page as the lookup or release form. A page request can fire before anyone submits a license number — and can treat tow or release 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 photos.
Towing and impound 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 towing-dispatch or impound 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 driver's license photos, registration images, insurance-card scans, or other proof-of-ownership files you accept depends on the fields you add; they are not fixed towing-company defaults. Filenames chosen by visitors can include plate numbers or full legal names. 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. License plate, VIN, driver's license number, phone, card fields for release fees, or contact fields depend on the fields you add — they are not fixed towing-company defaults. A release form that stores a license number next to a plate is identity stapled to a vehicle — and a plate-plus-timestamp row is also a location record — 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 vehicle leaves is not specified as a default purge. Public form browser hosts are unverified. | Release or lookup 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 license number was sent. A page request from this script on a lookup or dispatch page is not proof that a license photo or plate was collected — and a pre-consent tag on that page can still treat tow or release 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 lookup, dispatch, 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. Plate, VIN, driver's license number, or payment fields often depend on the fields you configure. An impound lookup or release form is not a completed release, not a lien filing, and not a police report. A marketing-tag page request is not proof a license number or plate was collected. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess towing regulations, lien law, police procedure, GDPR, or other compliance status. Ask your web vendor where entries and uploads live, whether post-release rows purge, whether portal links expire, whether marketing pixels stay off lookup pages, whether license photos stay off the first contact form, whether release-fee card fields stay off the contact form, and whether “secure release” badges match the storage path you can verify. Review stored records, uploaded scans, connected services, exports, notification emails, and backups.
Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.
Related pages
Scan your tow lookup page for third-party requests/wp-towing-plugin-privacy