Obituary writing plugin privacy
The announcement drafted before the death certificate
A writer can take an obituary order from a hospital waiting room. The intake can name the person who is still alive, list the survivors, leave others off that list, and attach the photo the family already chose. The entries table can hold that draft under embargo, timestamped before a death certificate exists. Decedent-name, requester-name, phone, survivors, omitted-relatives, chosen-photo, embargo-date, draft-text, hospital-ward, and relationship fields are configured, not documented defaults. Optional photos go in the site uploads folder. A draft is not proof anyone died. A photo is an upload, not a death certificate. A survivors list is stored names, not proof of kinship or estrangement. An embargo date is a stored date, not a death date. A hospital-ward label is a stored location, not a medical record. A page request is not proof anyone ordered a draft. The page URL can say obituary writing even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and uploads, which tags load on draft and order pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, a medical claim, a HIPAA claim, an occupancy claim, a funeral-arrangement claim, a monument claim, an estate-sale claim, a kinship claim, a death-certificate 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 embargoed drafts, chosen photos, and page tags go
Drafts and forms handled on your WordPress site
Check which decedent-name, requester-name, phone, survivors, omitted-relatives, chosen-photo, embargo-date, draft-text, hospital-ward, or relationship fields you enable, who can open form entries and bookings, where uploaded photos live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a draft that never published. Notification emails can also copy the same decedent names, survivor lists, and photos off-site. One table can name a living person, list who is in and who is left off, and attach the photo the family chose next to an embargo date, even when the announcement never runs. Ask your web vendor not to collect a decedent name next to a chosen photo and a survivors list on the first public form, not to store that embargoed draft next to a name in one open submissions list, and to purge unused drafts after the embargo date passes. A privacy-policy page does not by itself limit who can export a draft list or republish an upload. A stored draft is not proof anyone died.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the obituary-writing draft or order page. That page request can reach a vendor host before anyone submits. The page URL can say obituary writing even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off draft and order pages if you do not want that page request. A browser scan cannot inspect stored decedent names, survivor lists, or chosen photos. An "embargoed draft" badge is not a verified storage path.
Obituary-writing draft, photo, 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 funeral-home CRM or newspaper obituary-desk 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 |
|---|---|---|---|---|---|---|
| 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. An obituary-writing consult is a booking you create; a service name such as hospital waiting-room draft, embargoed announcement, or survivor-list intake is a label you configure. Neither is a documented default. Decedent-name, requester-name, phone, survivors, omitted-relatives, chosen-photo, embargo-date, draft-text, hospital-ward, or relationship questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked consult is not proof anyone died, and is not proof a draft published. Cancelling or missing the slot later does not erase the chosen photos, survivor lists, or decedent name already stored next to a phone, and does not unsend a confirmation email already delivered. How long that row sits after a draft that never published is not a documented default of the plugin. 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. | Draft-consult bookings, custom intake fields, and automatic confirmation emails 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-name, requester-name, phone, survivors, omitted-relatives, chosen-photo, embargo-date, draft-text, hospital-ward, or relationship questions are fields you add; they are not documented defaults. A chosen photo is a file you accept; that file type is not a documented default. A draft is not proof anyone died. A photo is an upload, not a death certificate. A survivors list is stored names, not proof of kinship or estrangement. An embargo date is a stored date, not a death date. A hospital-ward label is a stored location, not a medical record. 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 draft row sits after the announcement never published is not a documented default of the plugin. | Draft and chosen-photo 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 a decedent-name, survivors, or chosen-photo field was sent. A page request from this script is not proof anyone ordered a draft. The page URL can say obituary writing even when no form is submitted. Consent timing has not been tested. Review which tags you enable on draft and order pages. Keep marketing tags off those pages if you do not want that page request. A tagged draft page can re-confirm obituary-writing interest next to a stored decedent name and files; this row does not claim a published announcement from that request. | 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-name, requester-name, phone, survivors, omitted-relatives, chosen-photo, embargo-date, draft-text, hospital-ward, or relationship fields often depend on the fields you configure. A draft is not proof anyone died. A photo is an upload, not a death certificate. A survivors list is stored names, not proof of kinship or estrangement. An embargo date is a stored date, not a death date. A hospital-ward label is a stored location, not a medical record. A marketing-tag page request is not proof anyone ordered a draft. The page URL can say obituary writing even when no form is submitted. The chosen photo, the decedent name, and the embargo date can sit after the draft never publishes. This page is about an announcement drafted before the death certificate, not a funeral arrangements file, not a monument-engraving death date on stone, and not an estate-sale inventory of the house afterward. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the draft or order page, and how long records and backups are kept. A portfolio 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 medical status, HIPAA, occupancy, funeral arrangements, monument engraving, estate sale, kinship, or death-certificate claims. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on draft and order pages, and backups.
Documentation snapshot: Oct 15, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress forms privacy
- WordPress file upload plugin privacy
- WordPress comment plugin privacy
- All privacy guides
/wp-obituary-writing-plugin-privacy