Home-inspection plugin privacy
Where are inspection addresses and defect photos stored?
Booking forms can collect a property address, inspection date, and buyer name before anyone walks the house. File fields can store interior photos or inspection PDFs in the site uploads folder. Marketing tags on those pages can also send a page request to a vendor host. This sample reviews three plugins' documentation. Check which fields you collect, who can open records, where uploaded files land, whether a report link uses an access token, which tags load on the booking page, and how long entries, files, and backups are kept.
Documentation review only. This is not legal advice, a security assessment, an inspection-standards review, 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 booking entries, uploaded files, report links, email inboxes, staff permissions, vendor accounts, or backups.
Where booking answers, files, and page tags go
Answers and files handled on your WordPress site
Check which address, date, or file fields you enable, who can open entries, where uploaded files live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept. Notification emails can also copy the same answers off-site. A report link with an access token can show the same defect list to anyone who has the URL. Ask your web vendor not to leave inspection PDFs at a public uploads URL, to expire report links, and to purge booking entries after closing.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the booking page. That page request can reach a vendor host before anyone submits. Review which tags you enable, account access, and retention there. A browser scan cannot inspect stored form entries. A "client portal" label is not a verified storage path.
Home-inspection booking, file-upload, 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 inspection CRMs 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). Version 1.4.0 drag-n-drop-upload-cf7.php defines wpcf7_dnd_dir as wp_dndcf7_uploads. The listing states the free version moves files to wp-content/uploads/wp_dndcf7_uploads, attaches them to mail, then removes them from that temporary folder about one hour after submission. That cleanup does not remove copies already sent as email attachments. Inspection PDFs, interior photos, or floor plans are files you accept; they are not documented defaults. Pro documents saving to the Media Library, changing the upload directory, auto-delete timers, and remote storage to OneDrive, Google Drive, Amazon S3, Dropbox, or FTP. Public upload-page browser hosts are unverified. | Visitor files stored under wp-content/uploads/wp_dndcf7_uploads | Browser hosts not verified | Not assessed | Not tested |
| |
| XCodesol Home Inspection Manager Documented self-hosted inspection-management plugin (plugin version 1.0.0). Version 1.0.0 BookingService.php create_booking stores the visitor first name, last name, email, phone, and optional client address in xchim_clients, then writes street, city, state, zip, and property type to xchim_properties, and the inspection date and time slot to xchim_inspections. InspectionService.php assigns an access_token when a booking is created. Version 1.0.0 PhotoService.php uses wp_handle_upload and wp_insert_attachment for finding photos, so image files land in the default site uploads directory and the Media Library. Frontend.php handle_report_view serves print-ready HTML when xchim_report or a token query is present; a non-empty token authorizes the view without a login. Defect-list, lock, alarm, or vacancy notes are inspector findings, not documented booking-form defaults. Stripe and optional OpenAI or Gemini calls run only when you add keys. Public booking-page browser hosts are unverified. | Bookings stored in plugin tables; photos stored as WordPress attachments | 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 property address or defect list was sent. A page request from this script is not proof that a booking answer was collected. Consent timing has not been tested. Review which tags you enable on booking and report-delivery 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. Property addresses, inspection dates, interior photos, or defect notes often depend on the fields you configure. A booking request is not a finished inspection report. A marketing-tag page request is not proof that an address or defect list was collected. Ask your web vendor who can open entries, where uploaded files live, whether a report link expires, whether a marketing tag loads on the booking page, and how long records and backups are kept. A portal label is not a verified storage path. Camera metadata and unlisted media URLs are described only when a plugin documents them. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess inspection-standards or other legal status. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking pages, and backups.
Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress file-upload plugin privacy
- WordPress real-estate plugin privacy
- WordPress booking plugin privacy
- All privacy guides
/wp-home-inspection-plugin-privacy