Monument engraving plugin privacy

The proof PDF with a living name and an open death date

A pre-need engraving order can name a living person. A form can collect the name that will go on the stone, a birth year, an open death date waiting for its second number, the portrait chosen for laser etching, and the plot coordinates where the stone will stand. The proof PDF the family approved can sit in the site uploads folder. That order row can sit in a form plugin entries table any staffer can open. Living-name, birth-year, open-death-date, proof-pdf, portrait, plot-coordinates, requester-name, and phone fields are configured, not documented defaults. Optional proof PDFs and portraits go in the site uploads folder. A proof PDF is an upload, not a death certificate. A living name on a proof is a stored name, not proof anyone died. An open death date is a stored blank, not a death date. A birth year is a stored year, not proof of age. A portrait is an upload, not a biometric identity. Plot coordinates are a stored location, not proof of a burial right. A pre-need booking is not proof anyone died. A page request is not proof anyone ordered engraving. The page URL can say monument engraving 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 booking and order pages, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, a cemetery-plot claim, a funeral-measurement claim, an estate-sale claim, a genealogy claim, a death-certificate claim, a burial-right 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 monument-engraving orders, proof PDFs, and page tags go

Engraving orders and forms handled on your WordPress site

Check which living-name, birth-year, open-death-date, proof-pdf, portrait, plot-coordinates, requester-name, or phone fields you enable, who can open form entries and bookings, where uploaded proof PDFs and portraits live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a proof that never became a finished stone. Notification emails can also copy the same living names, birth years, open death dates, proof PDFs, portraits, plot coordinates, and requester names off-site. One table can name a living person, a birth year, and an open death date next to a phone, even when the stone is never cut. Ask your web vendor not to collect a living name next to an open death date and a proof PDF on the first public form, not to store those portraits next to plot coordinates in one open submissions list, and to purge unused proofs after the date passes. A privacy-policy page does not by itself limit who can export an order list or republish an upload. A stored order is not proof anyone died.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the monument-engraving booking or order page. That page request can reach a vendor host before anyone submits. The page URL can say monument engraving even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and order pages if you do not want that page request. A browser scan cannot inspect stored living names, proof PDFs, or portraits. A "pre-need specialist" badge is not a verified storage path.

Monument-engraving booking, order, 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 monument-engraving or cemetery software without a WordPress.org listing is 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 monument-engraving order is a booking you create; a service name such as monument engraving, headstone lettering, pre-need proof, or laser portrait is a label you configure. Neither is a documented default. Living-name, birth-year, open-death-date, proof-pdf, portrait, plot-coordinates, requester-name, or phone questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked order is not proof anyone died, and is not proof a stone was finished. Cancelling or missing the slot later does not erase the living name, birth year, open death date, proof PDF, portrait, or plot coordinates already stored next to a requester name, and does not unsend a confirmation email already delivered. How long that row sits after a booking that never became a finished stone 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.

Monument-engraving 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. Living-name, birth-year, open-death-date, proof-pdf, portrait, plot-coordinates, requester-name, or phone questions are fields you add; they are not documented defaults. A proof PDF or portrait is a file you accept; those file types are not documented defaults. A proof PDF is an upload, not a death certificate. A living name on a proof is a stored name, not proof anyone died. An open death date is a stored blank, not a death date. A birth year is a stored year, not proof of age. A portrait is an upload, not a biometric identity. Plot coordinates are a stored location, not proof of a burial right. A pre-need booking is not proof anyone died. 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 an order sits after a proof that never became a finished stone is not a documented default of the plugin.

Order and proof-PDF entries stored in WordPress; file uploads in the site uploads/forminator folderBrowser hosts not verifiedNot assessedNot tested
  • None
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 living-name, open-death-date, or proof-pdf field was sent. A page request from this script is not proof anyone ordered engraving. The page URL can say monument engraving even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and order pages. Keep marketing tags off those pages if you do not want that page request. A tagged order page can re-confirm monument-engraving interest next to a stored name and files; this row does not claim a finished stone from that request.

Marketing tags handled through Meta, Google, or other configured platformsconnect.facebook.netNot assessedNot tested
  • None

What this table does and does not prove

This is a documentation review, not a test of your site. Living-name, birth-year, open-death-date, proof-pdf, portrait, plot-coordinates, requester-name, or phone fields often depend on the fields you configure. A proof PDF is an upload, not a death certificate. A living name on a proof is a stored name, not proof anyone died. An open death date is a stored blank, not a death date. A birth year is a stored year, not proof of age. A portrait is an upload, not a biometric identity. Plot coordinates are a stored location, not proof of a burial right. A pre-need booking is not proof anyone died. A marketing-tag page request is not proof anyone ordered engraving. The page URL can say monument engraving even when no form is submitted. The living name, the open death date, and the proof PDF can sit after the proof never becomes a finished stone. This page is about the proof PDF with a living name and an open death date, not a cemetery-plot pre-need lead row, not a tailor funeral measurement, not an estate-sale emptied-house inventory, and not a genealogy-research family secret. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking 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 cemetery-plot, funeral-measurement, estate-sale, genealogy, death-certificate, or burial-right claims. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and order pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-monument-engraving-plugin-privacy