Flight school plugin privacy
The enrollment that stores the documents your license is made from
Flight training is the small-business enrollment where federal process makes the school verify citizenship: TSA's Flight Training Security Program means passport scans and birth certificates land in the intake form of a two-plane operation at a county airfield. Add the FAA medical class, the student logbook, and the solo-endorsement record, and a WordPress uploads folder holds the identity documents that licenses are made from. Driving-school and CDL siblings collect licenses; this form collects the papers those licenses are built on. The school's WordPress keeps that passport-plus-birth-cert-plus-FAA-medical-plus-logbook-plus-solo-endorsement row long after training closes. Those fields are configured, not documented defaults. An enrollment booking is a service appointment, not proof anyone trained or was certified. A passport or birth-certificate upload is a client document, not a government file. An FAA medical class answer is an identifier field, not a medical finding. A solo-endorsement note is a stored training record, not a certificate. A page request is not proof anyone enrolled. The page URL can say flight school even when no form is submitted. Ask what happens to the passport scan, the birth certificate, the FAA medical class, the student logbook, and the solo endorsement after training closes — the stack that answered who someone is before they flew outlives the lesson. 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, a TSA or FAA regulation claim, a citizenship-law claim, a pilot-licensing-eligibility claim, a medical-certification claim, a flight-school-insurance claim, an instructor-background-check 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 intakes, lesson bookings, and page tags go
Intakes and bookings on your WordPress site
Check which passport-scan, birth-certificate, FAA-medical-class, student-logbook, or solo-endorsement 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 training closes — when the passport-plus-birth-cert-plus-FAA-medical-plus-logbook-plus-solo-endorsement row still holds the documents licenses are made from. Notification emails can also copy those fields off-site. One table can list every "passport scan + birth cert + FAA Class 3 + solo endorsement N172AB + logbook 42.3 hrs" stack next to a student name. Ask your web vendor not to keep passport and birth-certificate rows next to FAA medical class, logbook, and solo-endorsement notes in one open submissions list longer than operations need, and to purge those fields when training closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored booking is not proof anyone trained or was certified. A passport or birth-certificate upload is not a government file. An FAA medical class answer is not a medical finding. A solo-endorsement note is not a certificate.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the flight-school enrollment page. That page request can reach a vendor host before anyone submits. The page URL can say flight school even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off enrollment pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "flight school privacy" badge is not a verified storage path.
Flight-school-enrollment, lesson-booking, 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 flight-school LMS or aviation 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 |
|---|---|---|---|---|---|---|
| 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 lesson booking is a booking you create; a service name such as flight school enrollment, discovery flight, or solo check is a label you configure. Neither is a documented default. Passport-scan, birth-certificate, FAA-medical-class, student-logbook, or solo-endorsement questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a calendar row, not proof anyone trained or was certified — and a CSV export of "passport scan + birth cert + FAA Class 3 + solo endorsement N172AB + logbook 42.3 hrs" next to a named student is still a calendar that pairs citizenship documents with the training record those documents made possible. 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. | Flight-school enrollment and lesson 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. Passport-scan, birth-certificate, FAA-medical-class, student-logbook, or solo-endorsement fields are fields you add; they are not documented defaults. Completing the form can store a passport scan next to a birth certificate, an FAA medical class, a student logbook page, and a solo-endorsement note — typed once so a county-airfield school can satisfy TSA citizenship verification, into the same tables as a flight-school label. A passport or birth-certificate upload is a client document, not a government file. An enrollment booking is a service appointment, not proof anyone trained or was certified — and a staff login can open "passport scan + birth cert + FAA Class 3 + solo endorsement N172AB + logbook 42.3 hrs" next to every other student row long after training closes. 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. | Passport, birth-certificate, FAA-medical, logbook, and solo-endorsement answers stored in WordPress; optional identity-document 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 passport-scan, birth-certificate, FAA-medical-class, student-logbook, or solo-endorsement field was sent. A page request from this script is not proof anyone enrolled. The page URL can say flight school even when no form is submitted. Consent timing has not been tested. Review which tags you enable on flight-school enrollment 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. Passport-scan, birth-certificate, FAA-medical-class, student-logbook, or solo-endorsement fields often depend on the fields you configure. An enrollment booking is a service appointment, not proof anyone trained or was certified. A passport or birth-certificate upload is a client document, not a government file. An FAA medical class answer is an identifier field, not a medical finding. A solo-endorsement note is a stored training record, not a certificate. A marketing-tag page request is not proof anyone enrolled. The page URL can say flight school even when no form is submitted. The passport-plus-birth-cert-plus-FAA-medical-plus-logbook-plus-solo-endorsement row that holds the documents licenses are made from — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that flight-school stack, not a driving-school permit scan, a CDL-school license upload, an immigration-lawyer passport custody file, or a travel-agency passport-for-booking field. 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 "flight school privacy" or "TSA compliant" 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 TSA or FAA regulation outcomes, citizenship law, pilot licensing eligibility, medical certification outcomes, flight-school insurance, or instructor background checks. Review stored records, bookings, connected services, exports, notification emails, marketing tags on enrollment pages, and backups.
Documentation snapshot: Oct 15, 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-flight-school-plugin-privacy