Home appraisal plugin privacy

The rush order that dates the divorce before the filing does

A residential real-estate appraiser can hold the earliest leak in almost every major life event that touches property: a booking or intake form where the reason-for-appraisal dropdown is a one-word biography of the household's year: divorce, estate, PMI removal, bankruptcy, pre-listing. A RUSH order timestamps the crisis before any public record exists. Uploaded interior photos can price every room of a house the owner still lives in. Access instructions (lockbox code, owner at work until 6) sit in the same entries table. Reason-for-appraisal, rush-order, access-instructions, lockbox-code, owner-at-work, property-address, owner-name, phone, email, appointment-date, and interior-photo upload fields are configured, not documented defaults. A reason-for-appraisal answer is a stored select, not proof a divorce was filed. A rush order is a stored priority label and timestamp, not proof a crisis happened. An interior-photo upload is a stored file, not a valuation. Access instructions are stored text, not proof anyone entered the home. A home-appraisal booking is not proof anyone completed an appraisal. A page request is not proof anyone booked. The page URL can say home appraisal even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open bookings, entries, and uploaded files, and how long records, interior photos, emails, and backups are kept.

Documentation review only. This is not legal advice, a divorce-outcome claim, a bankruptcy claim, an estate-settlement claim, an appraisal-valuation claim, a gold-buyer claim, a home-inspection claim, a public-adjuster claim, a probate claim, or a GDPR or other compliance assessment.

Scan your site for third-party requests

The 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 rush orders, reason labels, and interior photos go

Appraisal bookings and intake forms handled on your WordPress site

Check which reason-for-appraisal, rush-order, access-instructions, lockbox-code, owner-at-work, property-address, owner-name, phone, email, or appointment-date fields you enable, who can open form entries and bookings, which inboxes receive copies, and how long records, emails, and backups are kept after an appraisal that never happened. Notification emails can also copy the same reason-for-appraisal answers, rush-order labels, access instructions, and property addresses off-site. One table can name the owner, the property address, a divorce or bankruptcy reason, and a lockbox code next to a phone, even when no visit begins. Ask your web vendor not to collect a reason-for-appraisal answer next to a rush-order flag and access instructions on the first public form, not to store those fields next to owner names in one open bookings list, and to purge unused intake rows after the appraisal window closes. A privacy-policy page does not by itself limit who can export a booking list. A stored reason-for-appraisal answer is not proof a divorce was filed.

Interior-photo uploads on your WordPress site

Some upload tools store interior-photo originals under your WordPress uploads or wp-content path and can keep files reachable by direct URL after the visit. An interior-photo set tied to a property address can sit after an appraisal that never happened. Review who can open uploads, whether image files remain reachable without a login, and how long originals are kept. A browser scan cannot inspect stored bookings or interior-photo files that never load in the visitor browser. A "secure client upload" badge is not a verified storage path.

Home-appraisal booking, form, and file-upload 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 appraisal SaaS tools without a WordPress.org listing are outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Easy Appointments

Documented self-hosted appointment plugin marketed for service businesses (plugin version 4.0.3). The listing documents automatic email notifications: customers get instant booking confirmations; staff get notified; templates can include booking information and custom fields; customers can confirm or cancel via a link in the email. WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A home appraisal visit is a booking you create; a service name such as residential appraisal, rush appraisal, or refinance appraisal is a label you configure. Neither is a documented default. The stored service name can say rush appraisal in plain text before anyone arrives. Reason-for-appraisal, rush-order, access-instructions, lockbox-code, owner-at-work, property-address, owner-name, phone, email, or appointment-date questions are custom fields you add (textarea, select, or input); they are not documented defaults. A reason-for-appraisal answer is a stored select, not proof a divorce was filed. A rush order is a stored priority label and timestamp, not proof a crisis happened. Access instructions are stored text, not proof anyone entered the home. A booked slot is not proof anyone completed an appraisal. Cancelling or missing the slot later does not erase the reason-for-appraisal answer, rush-order label, or lockbox code already stored, and does not unsend a confirmation email already delivered. How long that pairing sits after a booking that never became an appraisal is not a documented default of the plugin. The appointments list can show who is booked this week and at which property address. 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.

Home-appraisal bookings, custom intake fields, and automatic confirmation emails on your WordPress siteBrowser hosts not verifiedNot assessedNot tested
  • None
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. Reason-for-appraisal, rush-order, access-instructions, lockbox-code, owner-at-work, property-address, owner-name, phone, or email questions are fields you add; they are not documented defaults. Optional interior-photo or document uploads are files you accept; those file types are not documented defaults. A reason-for-appraisal answer is a stored select, not proof a divorce was filed. A rush order is a stored priority label, not proof a crisis happened. An interior-photo upload is a stored file, not a valuation. Access instructions are stored text, not proof anyone entered the home. A home-appraisal form is not proof anyone completed an appraisal. Notification emails can copy field values and file links off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. How long a pairing sits after an appraisal that never happened is not a documented default of the plugin.

Appraisal intake and reason-for-appraisal entries stored in WordPress; optional uploads in the site uploads/forminator folderBrowser hosts not verifiedNot assessedNot tested
  • None
Iptanus File Upload

Documented frontend upload form (formerly WordPress File Upload). By default files land inside the wp-content directory of the site; the upload path is configurable. Uploaded files can be added to Media or attached to the current page. FTP and SFTP destinations are documented. The Professional version documents uploads to Google Drive, Dropbox, OneDrive, or Amazon S3. An interior photo, floor plan, or prior appraisal PDF is a file you accept; that file type is not a documented default. An uploaded interior photo is a stored file, not a valuation. Deleting a form entry later does not by itself prove the file was removed from the uploads path or from a cloud destination you enabled. The listing claims GDPR compliance without a tested EXIF-strip or retention length here. Review upload directory, Media attachment, and cloud destinations. Browser hosts for the visitor upload path were not verified for this snapshot. How long an interior-photo file sits after an appraisal that never happened is not a documented default of the plugin.

Interior-photo and document uploads stored under the site wp-content pathBrowser hosts not verifiedNot assessedNot tested
  • None

What this table does and does not prove

This is a documentation review, not a test of your site. Reason-for-appraisal, rush-order, access-instructions, lockbox-code, owner-at-work, property-address, owner-name, phone, email, appointment-date, or interior-photo upload fields often depend on the fields you configure. A reason-for-appraisal answer is a stored select, not proof a divorce was filed. A rush order is a stored priority label and timestamp, not proof a crisis happened. An interior-photo upload is a stored file, not a valuation. Access instructions are stored text, not proof anyone entered the home. A home-appraisal booking is not proof anyone completed an appraisal. A page request is not proof anyone booked. The page URL can say home appraisal even when no form is submitted. The rush order, the reason-for-appraisal label, and the interior photos can sit after an appraisal that never happened. This page is about the rush order that dates the divorce before the filing does, not a gold-buyer object appraisal, not a home-inspection defect walkthrough, not a public-adjuster post-loss inventory, not a probate estate intake, and not a real-estate listing inquiry. Ask your web vendor who can open entries and uploads, whether interior-photo files remain reachable by direct URL, and how long records and backups are kept. A "secure client upload" 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 legal advice, divorce outcomes, bankruptcy claims, estate settlements, or appraisal valuations. Review stored records, uploaded originals, connected services, exports, notification emails, and backups.

Documentation snapshot: Oct 19, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-home-appraisal-plugin-privacy