Probate attorney plugin privacy
The intake that inventories the estate while the house is still empty
A probate consult can look like a booking and a contact form. The same intake often asks who died, what they owned, who the heirs are, which of them dispute the will, and whether the house is empty — and stores those answers next to a decedent name for the life of the form table. Those fields are configured, not documented defaults. The asset list keyed to the house that just emptied is still just a form row until a court filing makes any of it public; the catalog exists while the fight narrative is still private. A consult request is not proof anyone died or that a will exists. A dispute field is one relative's framing, not a finding — heirs named in it are third parties who never consented. An uploaded will is a client document, not a filed instrument. A page request is not proof a family is in probate. The page URL can say probate attorney even when no form is submitted. Ask what happens to the asset list and the heir roster after the consult — the intake inventories the estate weeks earlier than probate. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the intake page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a probate-law claim, a will-validity claim, an inheritance-tax claim, a court-procedure claim, an unclaimed-property 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 probate consults, estate intakes, and page tags go
Intakes and bookings on your WordPress site
Check which decedent, asset-inventory, heir-roster, dispute-narrative, or document-upload fields you enable, who can open form entries and consult bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a matter closes — when the row still maps an emptied house to a family fight. Notification emails can also copy those fields off-site. One table can list every household that typed an estate map. Ask your web vendor not to keep will files next to heir names in one open submissions list longer than operations need, and to purge intake rows when the consult is closed. A privacy-policy page does not by itself limit who can open a submissions list. A stored consult is not proof anyone died. An uploaded will is not a filed instrument.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the probate-attorney intake page. That page request can reach a vendor host before anyone submits. The page URL can say probate attorney even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off intake and booking pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "confidential estate consultation" badge is not a verified storage path.
Probate consult, estate-intake, 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 or legal SaaS platforms 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. A probate consult or estate-intake booking is a booking you create; a service name such as probate consult or will-review meeting is a label you configure. Neither is a documented default. Decedent, asset-inventory, heir-roster, or dispute-narrative questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not a court filing — and a CSV export of consults next to heir names is still a name-keyed estate map captured while the house is empty. 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. | Probate consult 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. Decedent, asset-inventory, heir-roster, dispute-narrative, or document-upload questions are fields you add; they are not documented defaults. Completing the form can inventory the estate while the house is still empty — weeks before probate makes any of it public record. A submitted consult is not proof anyone died or that a will exists. A dispute field is one relative's framing, not a finding — heirs named in it are third parties who never consented. An uploaded will is a client document, not a filed instrument — and an asset list next to a dispute narrative can sit in the same row as the emptied address. A staff login can open the will file next to the heir roster. 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. | Estate-intake entries stored in WordPress; optional will and death-certificate 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 decedent, asset-inventory, heir-roster, or dispute field was sent. A page request from this script is not proof a family is in probate. The page URL can say probate attorney even when no form is submitted. Consent timing has not been tested. Review which tags you enable on intake and booking 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. Decedent, asset-inventory, heir-roster, dispute-narrative, or document-upload fields often depend on the fields you configure. A consult request is not proof anyone died or that a will exists. A dispute field is one relative's framing, not a finding — heirs named in it are third parties who never consented. An uploaded will is a client document, not a filed instrument. A marketing-tag page request is not proof a family is in probate. The page URL can say probate attorney even when no form is submitted. The intake inventories the estate while the house is still empty — that is a storage path next to a name, not a feature these plugins claim. This page is about that estate-map intake, not an estate-sale listing, a cemetery-plot pre-need inquiry, a funeral arrangement form, a guardianship petition, or a security-guard site survey. Ask your web vendor who can open entries, whether a marketing tag loads on the intake page, and how long records and backups are kept. A "confidential estate consultation" 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, will validity, inheritance tax, court procedure, or unclaimed-property rules. Review stored records, bookings, connected services, exports, notification emails, marketing tags on intake pages, and backups.
Documentation snapshot: Oct 14, 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-probate-attorney-plugin-privacy