CDL school plugin privacy
The enrollment that uploads your driving record before any employer asks
A CDL-school enrollment page can look like a booking and a contact form. The same form often asks for a license number, endorsement choices, a conviction-or-record answer, employment history, and a sponsor or employer — plus MVR and DOT-medical-card uploads — and stores those answers next to a name for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can hold the paperwork that decides a commercial driving career before any employer asks, typed once into a vendor table next to a marketing pixel. The felony-friendly promise is marketing; the conviction checkbox is a stored row. Many students are career-changers after a layoff or a sentence: the intake holds the reason for the fresh start next to the documents that could end it. An enrollment request is not proof anyone trained or was licensed. A conviction checkbox is the applicant's answer, not a court record. An uploaded MVR is a client document in a site uploads folder, not a DMV file. A DOT-medical-card upload is a client copy, not a registry entry. A page request is not proof anyone needs a second chance. The page URL can say CDL school even when no form is submitted. Ask what happens to the driving record and the conviction checkbox after enrollment — the enrollment uploads your driving record before any employer asks, and the row outlives the class. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the enrollment page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, an FMCSA or DOT-regulation claim, a licensing-eligibility claim, a background-check-law claim, an employment-law claim, a second-chance-program-outcome 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, bookings, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.
Where enrollment bookings, driving-record intakes, and page tags go
Intakes and bookings on your WordPress site
Check which license-number, endorsements, conviction-or-record, employment-history, or sponsor-or-employer fields you enable, who can open form entries and enrollment bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the enrollment uploads your driving record before any employer asks. Notification emails can also copy those fields off-site. One table can list every applicant whose conviction checkbox sat next to an MVR upload. Ask your web vendor not to keep driving records next to felony-friendly checkboxes in one open submissions list longer than operations need, and to purge intake rows when the enrollment closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored appointment is not proof of licensing. An uploaded MVR is not a DMV file.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the CDL-school enrollment page. That page request can reach a vendor host before anyone submits. The page URL can say CDL school even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off enrollment and road-test pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "second chance" badge is not a verified storage path.
Enrollment, driving-record intake, 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 CDL LMS or fleet SaaS platforms without a WordPress.org listing are outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Easy Appointments Documented self-hosted appointment plugin marketed for service businesses (plugin version 4.0.3). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. An enrollment or road-test booking is a booking you create; a service name such as CDL enrollment, road test, or skills evaluation is a label you configure. Neither is a documented default. License-number, endorsements, conviction-or-record, employment-history, or sponsor-or-employer questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not proof anyone trained or was licensed — and a CSV export of enrollment visits next to a conviction checkbox and a license number is still a re-qualification row after someone asked to drive for a living. Emails can include those custom fields and copy the appointment off-site. An optional GDPR setting can auto-remove customer data older than six months; that is not a default purge. Google Calendar, SMS, and payments are Pro. Google reCAPTCHA is optional. Public booking-form browser hosts are unverified. | CDL-school enrollment and road-test bookings stored on your WordPress site | 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. License-number, endorsements, conviction-or-record, employment-history, or sponsor-or-employer questions are fields you add; they are not documented defaults. Completing the form can store a license number next to endorsement choices, a conviction checkbox, employment history, a sponsor or employer name, and optional MVR or DOT-medical-card uploads — typed once to start a commercial driving career into the same tables as a newsletter signup. An enrollment request is not proof anyone trained or was licensed. A conviction checkbox is the applicant's answer, not a court record. An uploaded MVR is a client document in uploads/forminator, not a DMV file. A DOT-medical-card upload is a client copy, not a registry entry — and a staff login can open the uploaded driving record next to the felony-friendly checkbox the marketing page promised would not matter. Notification emails can copy field values and files off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. | Enrollment intake entries stored in WordPress; optional MVR and DOT-medical-card 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, 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, endorsements, conviction-or-record, employment-history, or sponsor-or-employer field was sent. A page request from this script is not proof anyone needs a second chance. The page URL can say CDL school even when no form is submitted. Consent timing has not been tested. Review which tags you enable on enrollment and road-test 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. License-number, endorsements, conviction-or-record, employment-history, or sponsor-or-employer fields often depend on the fields you configure. An enrollment request is not proof anyone trained or was licensed. A conviction checkbox is the applicant's answer, not a court record. An uploaded MVR is a client document in a site uploads folder, not a DMV file. A DOT-medical-card upload is a client copy, not a registry entry. A marketing-tag page request is not proof anyone needs a second chance. The page URL can say CDL school even when no form is submitted. The enrollment uploads your driving record before any employer asks — that is a storage path next to a conviction checkbox, not a feature these plugins claim. This page is about that re-qualification intake, not a consumer driving-school permit form, a DOT drug-testing appointment, a day-labor-hall sign-in, a firearms-training class roster, or a DUI-school court order. Ask your web vendor who can open entries, whether a marketing tag loads on the enrollment page, and how long records and backups are kept. A "second chance" 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 FMCSA or DOT regulation, licensing eligibility, background-check law, employment law, or second-chance program outcomes. Review stored records, bookings, connected services, exports, notification emails, marketing tags on enrollment pages, and backups.
Documentation snapshot: Oct 14, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress file upload plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-cdl-school-plugin-privacy