Estate sale plugin privacy
The quote form that inventories a dead person's house
An estate-sale quote form can store the house address, room-by-room photos of valuables, and the dates the house sits empty before the sale. The executor typing it is often grieving and in a hurry. Those answers can sit in a local-first form plugin behind one admin login. A marketing tag on the quote page can send a page request to a vendor host before anyone submits. A page request is not proof that contents were photographed. A quote request is not an estate inventory of record or a probate filing. The page URL can say estate sale even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and files, which tags load on the quote page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal or tax advice, a probate-law claim, an estate-tax claim, a liquidation-outcome 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, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.
Where quote answers, contents photos, and page tags go
Quotes and files handled on your WordPress site
Check which address, contents-photo, sale-window, or executor fields you enable, who can open form entries, which inboxes receive copies, and how long records, emails, and backups are kept. Notification emails can also copy the same answers off-site. One entry can store a house address next to photos of jewelry, tools, or collections and the dates the house sits unattended. Ask your web vendor not to collect sale-window dates on a public quote form, not to accept room-by-room contents photos on a public form, and to purge quotes that never became a sale. A privacy-policy page does not by itself limit who can open a quote list.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the quote page. That page request can reach a vendor host before anyone submits. The page URL can say estate sale even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off quote pages if you do not want that page request. A browser scan cannot inspect stored quotes. A "confidential estate sale" badge is not a verified storage path.
Estate-sale quote, 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 estate-liquidation software without a WordPress.org listing is 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. Room-by-room photos of jewelry, tools, or collections are files you accept; they are not documented defaults. An uploaded contents photo is not an estate inventory of record. 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 |
| |
| 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. Address, contents-photo, sale-window, or executor-name fields are fields you add; they are not documented defaults. One form entry can store a house address next to room-by-room photos of valuables and the dates the house sits unattended. Completing the form can record a quote request. A quote request is not an estate inventory of record or a probate filing. A staff login can open the address, the photos, and the sale window in the same submissions list. Notification emails can copy field values off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. | Form entries stored in WordPress; file 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 address, contents-photo, or sale-window fields were sent. A page request from this script is not proof that contents were photographed. The page URL can say estate sale even when no form is submitted. Consent timing has not been tested. Review which tags you enable on quote 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. Address, contents-photo, sale-window, or executor fields often depend on the fields you configure. A quote request is not an estate inventory of record or a probate filing. An uploaded contents photo is not a finished sale. A marketing-tag page request is not proof that contents were photographed. The page URL can say estate sale even when no form is submitted. This page is about the quote form, not a moving date, a restoration claim, an auction bid, or a funeral arrangement. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the quote page, and how long records and backups are kept. A "secure" or "confidential estate sale" 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 probate law, estate tax, or liquidation outcomes. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on quote pages, and backups.
Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress funeral plugin privacy
- WordPress auction plugin privacy
- WordPress file upload plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-estate-sale-plugin-privacy