Crime scene cleanup plugin privacy

The quote form that records what happened in the house before the obituary runs

A crime-scene cleanup quote can look like a scheduling request. The same form often stores the property address, a what-happened dropdown, relationship to the deceased, date discovered, an insurance carrier, and scene photos someone uploaded so the crew would know what to bring. Those fields are configured, not documented defaults. The intake can be the only written account of the event — timestamped ahead of any public record, retained after the cleanup ends. The family thinks they are booking a service; the form is writing the house's history. The house can be clean; the database can still say what happened in it. A quote request is not proof a death occurred at the address. A what-happened dropdown is a configured field, not a default. A page request is not proof anyone requested a quote. The page URL can say crime scene cleanup even when no form is submitted. Ask what happens to that address-keyed row after the job ends — the cleanup ends, the form table may not. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and uploads, which tags load on the quote page, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, a stigmatized-property-disclosure-law claim, a death-certificate claim, a coroner-procedure claim, an insurance-coverage claim, a property-value 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 quotes, assessment bookings, and page tags go

Quotes, scene photos, and bookings on your WordPress site

Check which property-address, what-happened, relationship-to-deceased, date-discovered, insurance-carrier, or scene-photo fields you enable, who can open form entries and assessment bookings, where uploaded scene photos live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after the cleanup ends — when the house is clean but the address-keyed row may still describe what happened. Notification emails can also copy the same scene photos off-site. One table can list every address that asked for help. Ask your web vendor not to keep what-happened notes next to contact details in one open submissions list longer than operations need, and to purge quote rows when the job is over. A privacy-policy page does not by itself limit who can open an uploads folder. A stored quote is not proof a death occurred at the address. A what-happened field is a configured answer, not a death certificate.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the crime-scene cleanup quote page. That page request can reach a vendor host before anyone submits. The page URL can say crime scene cleanup 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 entries or scene photos. A "confidential remediation records" badge is not a verified storage path.

Crime-scene cleanup quote, assessment-booking, 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 remediation SaaS platforms without a WordPress.org listing are 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). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. An on-site assessment visit is a booking you create; a service name such as trauma-scene assessment or biohazard quote visit is a label you configure. Neither is a documented default. Property-address, what-happened, relationship-to-deceased, date-discovered, or insurance-carrier questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not proof a death occurred at the address — and a CSV export of assessment visits next to addresses is still an address-keyed list of the worst week. Emails can include those custom fields. 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.

Assessment-visit bookings stored 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. Property-address, what-happened, relationship-to-deceased, date-discovered, or insurance-carrier questions are fields you add; they are not documented defaults. A scene photo is a file you accept; it is not a documented default. Completing the form can record a quote request. A submitted quote is not proof a death occurred at the address. A what-happened answer is a configured field, not a death certificate. A staff login can open the address next to the what-happened dropdown and the scene photos — and that row can still exist after the house is clean. 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.

Quote entries stored in WordPress; scene-photo 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 property address, what-happened answer, or scene photo was sent. A page request from this script is not proof anyone requested a quote. The page URL can say crime scene cleanup even when no form is submitted. Consent timing has not been tested. Review which tags you enable on quote and assessment pages.

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. Property-address, what-happened, relationship-to-deceased, date-discovered, insurance-carrier, or scene-photo fields often depend on the fields you configure. A quote request is not proof a death occurred at the address. A what-happened dropdown is a configured field, not a default. A marketing-tag page request is not proof anyone requested a quote. The page URL can say crime scene cleanup even when no form is submitted. The intake can be the only written account of the event, timestamped ahead of any public record — that is a storage path next to a grief week, not a feature these plugins claim. This page is about that address-keyed row, not a biohazard product catalog, a hoarding living-conditions form, a funeral arrangement, an estate sale, or a security-guard quote. Ask your web vendor who can open entries, where uploaded scene photos live, whether a marketing tag loads on the quote page, and how long records and backups are kept after the cleanup ends. A "confidential remediation records" 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 stigmatized-property-disclosure law, death-certificate systems, coroner procedure, insurance coverage, or property value. Review stored records, bookings, connected services, exports, notification emails, marketing tags on quote pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-crime-scene-cleanup-plugin-privacy