Driving-school learner-file privacy
The permit number and pickup address in a booking row
Driving-school sites on WordPress can use booking or enrollment plugins for lesson requests, learner profiles, and pickup scheduling. Those records can include a learner name, permit or license number, date of birth (often a minor), home pickup address, lesson notes, and test results you configure. This sample reviews three plugins' documentation. Check which fields you collect, who can open records, where vendor hosts store enrollment or payment data, and how long learner or booking rows and backups are kept.
Documentation review only. This is not legal advice and is not a DMV, GDPR, or other compliance assessment.
Scan your site for third-party requestsThe scan checks browser requests on the pages it visits. It cannot inspect learner profiles, booking records, staff permissions, vendor accounts, or backups.
Where driving-school learner files are stored
Records stored on your WordPress site
Check which learner or booking fields you enable, who can open entries, and how long records and backups are kept. Lesson confirmation and reminder emails can also copy the same details — or reveal a driving-school relationship — off-site.
Enrollment or payments handled by a vendor
Some tools send enrollment leads or payment data into a driving-school platform, Stripe, or another vendor when you enable those connectors. Review access and retention there. A browser scan cannot inspect those stored submissions.
Driving-school lesson-booking 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 driving-school 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 |
|---|---|---|---|---|---|---|
| Booking Calendar Documented general-purpose WordPress booking plugin (version 11.9.1). The privacy notice states booking details are stored in the WordPress database and are not sent to the vendor's servers by default; optional integrations may send data to external services you configure. Appointment-style flows collect customer contact details with configurable form fields — permit or license numbers, dates of birth, home pickup addresses, lesson notes, or test results depend on the fields you add; they are not fixed driving-school defaults. Confirmation emails to administrators and visitors can copy booking details off-site. Retention of booking rows is not specified as a default purge. Public booking-form browser hosts are unverified. | Lesson bookings and form answers stored in WordPress | Browser hosts not verified | Not assessed | Not tested |
| |
| LucrativeIT Driving School Management System Documented driving-school booking and instructor-scheduling plugin (version 1.1.0). Students book lessons against live instructor availability; bookings list student, service, date and time, instructor, location, and payment status. Locations store address, city, state, postcode, and phone for training centres or pickup points. A customisable booking form supports text, textarea, email, phone, number, date, dropdown, radio, and checkbox fields — permit or license numbers, dates of birth, home addresses, and lesson notes depend on the fields you configure; they are not fixed identity-document defaults. Optional customer login stores account bookings on the site. External services: Stripe Checkout (and optional WooCommerce or SMTP) only when enabled; card details stay on Stripe's hosted page and are not stored on the site. Deleting the plugin removes its tables and settings. Retention of booking or customer rows after a lesson ends is not specified as a default purge. Public booking-form browser hosts are unverified. | Driving-lesson bookings and customer records stored in WordPress | Browser hosts not verified | Not assessed | Not tested |
| |
| eDrive Site Documented WordPress embed for the eDrive driving-school management platform (plugin version 1.0.0). Offers, theory groups, and school details are pulled from eDrive; the enrollment form ([edrive_form]) collects name, phone, email, offer, group, and message with a mandatory data-processing consent checkbox. Every request is sent from the WordPress server to https://partners.edrive.md with the school's API key; enrollment leads land in the eDrive Leads section — not as ordinary WordPress form-entry tables. The API key never reaches the browser. Permit or license numbers, dates of birth, pickup addresses, and test results are not listed as fixed enrollment fields; any such detail would depend on what the visitor types in the message field. This row describes the documented storage path only and does not assess legal or regulatory compliance status. Review vendor account access and retention separately. Browser hosts for the embed were not verified for this snapshot (partner API calls are server-side). | Enrollment leads forwarded to the eDrive vendor platform | Browser hosts not verified | Not assessed | Not tested |
|
What this table does and does not prove
This is a documentation review, not a test of your site. Permit, date-of-birth, pickup-address, or lesson-note fields often depend on what you configure. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess legal compliance status. Review stored learner records, connected services, exports, notification emails, and backups.
Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress daycare plugin privacy
- WordPress school plugin privacy
- WordPress tutoring plugin privacy
- All privacy guides
/wp-driving-school-plugin-privacy