Pet cremation plugin privacy

The pickup request filed at the worst hour, with the grief text stored next to the address

A pet-cremation order can look like an urn and a pickup time. It is also a grief intake: home address, phone, the pet's name, and a free-text memorial field where people write things they would never put in any other form. That order row logs a death in the household before neighbors or family know, and the grief text sits next to an address. An urn engraving line is a timestamped record of who is grieving and when the house is being visited for pickup. Pet-name, memorial-text, pickup-window, engraving-line, species, and weight fields are configured, not documented defaults. Optional pet photos for the urn go in the site uploads folder. A pickup booking is not proof a pet died. A memorial answer is a stored note, not a verified eulogy. A page request is not proof anyone ordered aftercare. The page URL can say pet cremation 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 account pages, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, a grief-counseling claim, a death-certificate claim, a veterinary-diagnosis 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 pickup bookings, memorial intakes, and page tags go

Pickup bookings and memorial forms handled on your WordPress site

Check which pet-name, memorial-text, pickup-window, engraving-line, species, or weight fields you enable, who can open form entries and bookings, where uploaded pet photos live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a request that never became a pickup. Notification emails can also copy the same memorial text and pet name off-site. One table can name the house, the pet, the grief note, and the pickup window next to a name, even when the van never comes. Ask your web vendor not to collect a memorial essay next to an address on the first public form, not to store engraving lines next to pickup windows in one open submissions list, and to purge unused pickup bookings after the date passes. A privacy-policy page does not by itself limit who can export a customer list. A stored booking is not proof a pet died.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the pet-cremation booking or account page. That page request can reach a vendor host before anyone submits. The page URL can say pet cremation even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and account pages if you do not want that page request. A browser scan cannot inspect stored memorial text, pet names, or pickup windows. An "aftercare customer" badge is not a verified storage path.

Pet-cremation booking, memorial-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 pet-aftercare or crematory 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 pet-cremation pickup is a booking you create; a service name such as private cremation, communal cremation, or urn engraving is a label you configure. Neither is a documented default. Pet-name, memorial-text, pickup-window, engraving-line, species, or weight questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked pickup is not proof a pet died, and a memorial answer is not a verified eulogy. Cancelling or missing the slot later does not erase the memorial text, pet name, pickup window, or engraving line already stored next to a name, and does not unsend a confirmation email already delivered. How long that row sits after a booking that never became a pickup 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.

Pickup 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. Pet-name, memorial-text, pickup-window, engraving-line, species, or weight questions are fields you add; they are not documented defaults. A pet photo for the urn is a file you accept; that file type is not a documented default. A pickup request is not proof a pet died. A memorial answer is a stored note, not a verified eulogy. An engraving line is a stored instruction, not proof an urn was etched. 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 account row sits after a request that never became a pickup is not a documented default of the plugin.

Account and memorial-intake form 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 pet-name, memorial-text, pickup-window, or engraving-line field was sent. A page request from this script is not proof anyone ordered aftercare. The page URL can say pet cremation even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and account pages. Keep marketing tags off those pages if you do not want that page request. A tagged aftercare page can re-confirm pet-cremation interest next to a stored address and memorial text; this row does not claim a pickup 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. Pet-name, memorial-text, pickup-window, engraving-line, species, or weight fields often depend on the fields you configure. A pickup booking is not proof a pet died. A memorial answer is a stored note, not a verified eulogy. A marketing-tag page request is not proof anyone ordered aftercare. The page URL can say pet cremation even when no form is submitted. The grief text and the pickup window can sit after the van never comes. This page is about a pickup request that files memorial text next to an address, not a funeral condolence book, not a veterinary vaccination reminder, and not a pet-sitting nights-away calendar. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or account page, and how long records and backups are kept. An aftercare-customer 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 grief counseling, death-certificate processes, or veterinary diagnosis. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and account 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-pet-cremation-plugin-privacy