Travel agency plugin privacy
The passport scan filed next to your departure date
Travel agencies and tour operators on WordPress can collect a booking quote that pairs passport-grade identity with the exact window a household will be away — full legal names as on passports (including minors), dates of birth, passport numbers and expiry, Global Entry / Known Traveler numbers, and departure and return dates — through general-purpose form, upload, and marketing-tag plugins. Passport and visa scans land in uploads because “send us a photo of your passport” is standard onboarding. A remarketing pixel on the quote page can fire destination interest before consent. This sample reviews three plugins' documentation. Check which traveler fields you collect, who can open submissions, where temporary uploads and tags store or send that data, and how long booking rows, scans, and backups are kept after the trip.
Documentation review only. This is not legal advice, not a TSA or visa-processing guide, not airline guidance, and not a GDPR or other compliance assessment.
Scan your travel quote page for third-party requestsThe scan checks browser requests on the pages it visits. It cannot inspect form entries, uploaded passport or visa scans, email inboxes, staff permissions, vendor accounts, or backups.
Where passport scans, departure dates, and quote-page tags are stored
Files and form entries handled on your WordPress site
Check which passport, visa, date-of-birth, traveler-number, departure-date, 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 trip. Notification emails can also copy booking answers off-site. Passport data next to departure dates in the contact-form database is identity plus a home-empty window on a marketing site.
Marketing tags on the quote or upload page
Some tools load a marketing pixel or tag on the same page as the quote form. A page request can fire before anyone submits a passport number — and can treat destination interest 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 passport scans.
Travel booking-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 GDS or tour-operator 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 passport scans, visa images, travel-insurance docs, or other traveler files you accept depends on the fields you add; they are not fixed travel-agency defaults. Filenames chosen by visitors can include passport 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. Passport number, expiry, date of birth, Global Entry / Known Traveler number, departure or return date, or contact fields depend on the fields you add — they are not fixed travel-agency defaults. A quote form that stores passport-grade identity next to departure dates is the two halves of a home-empty window 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 trip is not specified as a default purge. Public form browser hosts are unverified. | Booking 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 passport number was sent. A page request from this script on a quote page is not proof that a passport scan or departure date was collected — and a pre-consent tag on that quote page can still treat destination interest 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 quote 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. Passport, visa, date-of-birth, traveler-number, or departure-date fields often depend on the fields you configure. A booking quote form is not a ticket purchase, not a visa approval, and not proof of travel. A marketing-tag page request is not proof a passport number or departure date was collected. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess airline, TSA, visa-processing, GDPR, or other compliance status. Ask your web vendor where entries and uploads live, whether post-trip booking rows purge, whether portal links expire, whether marketing pixels stay off quote pages, whether passport scans stay off the first contact form, and whether “secure booking” 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 travel quote page for third-party requests/wp-travel-agency-plugin-privacy